Monthly Archives: Urtarrilaren 2008

Blog Stats

I thought some people might be interested in my blog’s statistics. You can use mine as a benchmark to compare your own.

I’m running my blog on windows live spaces. They collect stats for me and I don’t know any way to control that. It’s good as far as it goes, but it’s fairly limited in that I can’t do much actual analysis with it. I’d love, adibidez, to be able to generate a listing of my most frequently hit posts but I can’t do that without a prohibitive manual process. If someone knows better, mesedez esan dit.

Live espazio egoera kontatu zidan: egunean hits guztira, total hits for the week and total hits since day zero. It also tells me what people did to get to my blog (e.g. google, MSDN foro lotura, etc).

Nolabait, a "hit" begien bistakoa da. Zaren esaldi hau irakurtzen oraintxe, ia zalantzarik duzun hit bakar gisa erregistratu.

RSS is a little confusing. On one hand, I see individual RSS hits all day long. Baina, I also see RSS "sweeps". A sweep is when I see 20 edo 30 RSS hits all within a one or two second window. I assume these are automated things like google checking in on my site, agian beste pertsona horrek nabigatzaile … not sure. They are definitely some kind of automated process. I cannot tell, Hala ere,, how many of my total hits are automated and how many have an actual human on the other side. I would guess at least 100 eguneko hits automatikoak dira.

Zenbakiak buruzko!

Nire lehenengo blog-sarrera idatzi nuen uztailaren 27an, 2007.

Idatzi dut, gutxi gorabehera, 60 blog-sarrerak eta orduz geroztik, baino gehiago 50 horietatik zuzenean SharePoint erlazionatzeko.

Segimendua egiteko, nire sarrera kalkulu batean, egunero, irailaren amaieran hasi nintzen.

Hileroko Hasiera:

Lehen aste: Guztira Hits
Urriaren 1,234
Azaroaren 2,162
Abenduaren 3,071
Urtarrilaren 2008 4,253

Hilabetea Guztira

Hilabetea Guztira Hits
Urriaren 6,620
Azaroaren 11,110
Abenduaren 13,138

High Water Markak

Mota Guztira Hits
Best Day 958
Best Astea 4,253
Geroztik Day Zero Hits Guztira 42,438

Dut, beste batzuek interesa’ stats. If you care to share yours in the comments, mesedez egin!

</amaiera>

Technorati Tags:

Igande goizean Funny: “Yeah, yeah, yeah. Blah, blah, blah.”

Sei urte, nire lau urteko semea eta biok goiko bat ikusi Discovery Channel "shark attacks" bereziak (seguru asko, hau da,). He was very young at the point and I was always worried what he might see on a show like this and how he might take it. I didn’t want him to develop, adibidez, edozein bereziak beldurrak ura edo blab zerbait egokitzat bere lagunak eta, seguru asko, bere haurra lagun sarea sor behera etorri.

Discovery handles these kinds of subjects very well. It’s not about creating a zerbaiten beldur, but rather to show how unusual it is for sharks to attack humans.

Beraz,, we’re watching it and there is this one particularly scary attack involving a small girl. As Discovery is building the drama of the attack, nire semea (nor izan da beti, hala ere, oso jumpy), is getting very excited. I make some noises about how unusual it is for sharks to attack people, and how bad the poor girl must feel. I’m trying to explain that people recover from these events and become stronger for it. Hala eta guztiz ere, I had misinterpreted his excitement. He was not worried about the girl at all. Horren ordez, txaloak, berriz, bere esku, esaten dit, "The sharks love it! It’s terrific. It’s wonderful. Its a DREAM COME TRUE!"

Hau izan zen pentsatu nuen barregarri, but also very disturbing. Alde batetik,, Pozik nengoen, — nahiz eta apur bat harro — indartsu enpatikoa sentimenduak izan zituen, cross-species though they may be. As humans, we need to develop our "empathic muscles" beraz, hitz egin edo, azkenean, ikusiko duzu atsegin Guy honetan 🙂 On the other hand, he was feeling cross-species empathy toward a species who was exhibiting behavior inimical to his own. I was really struggling with this when the narrator used the word "paradigm". My son picked up on that and asked me what that meant.

Hori ez da beti erraza, esaterako, hitz bat, lau urteko deskribatzeko, but I gave it a try. When I think of the word "paradigm", Thomas Kuhn is never far from my thoughts. Irakurri dut Iraultzen Zientifikoen Egitura atzera Lafayette eta, onerako zein txarrerako, the word "paradigm" is pregnant with extra meaning for me. (Sort of like the word "contact" entzun ondoren bat Movie Telefonoa ahots Esadazu non ikusi izan dut duten filma [Liburua izan zen, hobeto pentsatu dut]; Neu naiz beti esan, "CONTACT!" whenever I see or hear someone say "contact").

Hala ere, Berarekin Kuhnian definizioa azaldu ari naiz, that it’s "a historical movement of thought" and that it’s a "way of thinking with a number of built-in assumptions that are hard to escape for people living at that time." Jakina, ezin duzu hitz egin bezala, lau urte bat, so I’m trying to successively define it to smaller pieces and feeling rather proud of myself as I do so. (Dut Bagenekien unibertsitateko kanpoko norbait izan dela irakurri dut Kuhn zaintzeko litzateke!).

I’m just warming to the task when he interrupts me. Waving his hand nire zuzendaritzapean, oro har, eta inoiz ez bere begiak hartuz, beste marrazo atentatuaren off, dio besterik ez zuen, "Yeah, yeah, yeah. Blah, blah, blah.".

So much for that 🙂

Une horretan, Ihes egitea erabaki nuen, rhetorically hitz egin, eseri, eta gozatu marrazo eraso gizakiak behaketa nire semea.

</amaiera>

Technorati Tags:

Aldatu Ikusi Erabiltzaile ID oinarrituta InfoPath formularioa batean

Bat garatu genuen InfoPath inprimaki bat hainbat aldiz berriak alokatzeko bati laguntzeko / on-boarding process. When the company hires a new person, Informatika Saila eta beste taldeek behar ekintza (sortu nominak, gaitu dagokion aplikazio sarbidea, kokatzeko mahai bat, etc). We use on form but a different view of the form for each of those functions.

Enpresa honetan, Enpresa-prozesuan parte hartzen duten pertsona gehienak dira IT-savvy, beraz, forma sartu dira, their default view is a "menu" view with buttons that direct them to their specific function. Hala eta guztiz ere, we needed to simplify things for the new hire’s direct manager. This person should not see any of the IT related stuff. Izan ere,, bakar forma ikuspegi ikusi behar zuen, eta ez da, nahiz eta beste aukera bat aldiz ikusi behar.

Gure kasuan,, zuzeneko kudeatzailearen kontu hori zuzenean jarriz inprimaki lotuta harremanetan hautatzailea (which I am always wanting to call a "people picker" arrazoiren batengatik).

Urratsak honako hauek dira::

1. Diseinu moduan, joan Tresnak -> Inprimaki Aukerak -> Ireki eta gorde.

2. Select "rules".

3. Create a new rule whose action is "switch to view" eta zeinen baldintza userName baliatzen() funtzioa.

userName() returns the "simple" user name without the domain. If I log into SharePoint with credentials "domain\pagalvin", userName() returns "pagalvin".

The contact selector provides three bits of information for a contact. The "AccountID" portion is most useful for this scenario. The only thing that makes this even a little bit of challenge is that the contact selector (Nire ingurunean Hala ere,) itzultzen domeinua eta erabiltzaile-ID, as in "domain\pagalvin". This prevents us from doing a straight-forward equality condition since AccountID ("domain\pagalvin") ez dira inoiz berdinak userName() ("pagalvin").

We can get around this using the "contains" operadore: AccountID dauka userName().

Da gero eta pre-PEND userName aurrean domeinu hard-kodetuak bat hartu ahal izango dugu() funtzionatzeko gure berdintasuna egiaztatu eta desagerrarazi faltsu positiboak arriskua dauka operadorearen iritsi.

We would have REALLY like to automatically switch view for other users based on their AD security group membership. Adibidez, when a member of the "IT Analytics" talde inprimaki sartzen, automatically switch to the IT Analytics view. We didn’t have time to implement it, but my first thought is to create a web service that would have a method like "IsMemberOfActiveDirectorySecurityGroup", pasatzen da, erabiltzaile izena() and return back true or false. Does anyone have any other, gehiago clever ideia? Is there any SharePoint function we can leverage from InfoPath to make that determination?

</amaiera>

Technorati Tags:

Ustekabean Código gehitzea InfoPath inprimakia; Nahita kendu

Noiz botoiak formulario bat ari da lanean, we often add rules. You access the rules editor from the properties of the button.

Noiz inguratuz klik azkar, it’s easy to accidentally click on "Edit Form Code" instead of "Rules …".

Lehenengo aldiz egin nuen hau, I canceled out of the code editor. Hala eta guztiz ere, denean, forma argitaratzeko pixka bat beranduago saiatu naiz, it required that I publish as an "Administrator-approved form template (aurreratuak)". I didn’t actually do any programming and I absolutely didn’t want to go through an unnecessary approval process. I was in a bit of panic at the time due to time constraints. To get past it, I simply restored a previous backup and continued. I had recently seen some blog posts about people going into the form’s XML to tweak things and I was afraid I would have to do something similar.

Gaur egun, I did it again. Oraingo honetan, Pixka bat denbora gehiago izan nuen nire eskuak eta aurkitu ahal izango duzu erraz desegin honetan.

Hona joan:

Tresnak -> Inprimaki Aukerak -> Programazioa: "Remove Code"

Ez du lortu hori baino askoz errazagoa.

</amaiera>

Technorati Tags: ,

Gutxieneko segurtasuna InfoPath Inprimakiak behar diren

I needed to meet a security requirement for an InfoPath form today. In this business situation, a relatively small number of individuals are allowed to create a new InfoPath form and a much wider audience are allowed to edit it. (Hau da, berri-kontratatu on-barnetegi inprimaki Giza Baliabideetako ek erabiltzen duen workflow bat jarri du abian).

Helburu hori bete ahal izateko, Sortu sortu dut bi baimen mailak ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, eguneratu" user and a separate "update only" Erabiltzaileak. The mechanics all worked, but it turned out to be a little more involving than I expected. (Sentitzen duzu, pixka bat bada, dar-dar SharePoint baimenak, begiratu blog post honetan). The required security configuration for the permission level was not the obvious set of granular permissions. To create an update-only permission level for an InfoPath form, Honako hau egin nuen:

  1. Berri bat sortzeko baimenik maila.
  2. Garbitu kanpoan aukera guztiak.
  3. Selected only the following from "List permissions":
    • Elementuak editatu
    • Ikusi elementu
    • Ikusi aplikazio orrialdeak

Aukera horiek hautatzean, erabiltzaileak inprimaki bat eguneratzeko, baina ez da sortu.

The trick was to enable the "View Application Pages". There isn’t any verbage on the permission level that indicates that’s required for update-only InfoPath forms, baina bihurtzen da.

Create-and-Update was even stranger. I followed the same steps, 1 bidez 3 Goiko. I had to specifically add a "Site Permission" aukera: "Use client integration features". Berriz, deskribapena dago, ez du dirudi InfoPath inprimaki bat egon behar da, behar bezala, baina ez da.

</amaiera>

Duten “-En artean,” Feeling; SharePoint Consulting buruzko oharrak

Tamalez, phase one of my last project has come to a close and the client has opted to move ahead by themselves on phase two. We did our job too well, as usual 🙂 I’m now between projects, langile bezala, nire burua aholkulariak denbora berezi bat (as opposed to independents who must normally live in perpetual fear of in-between time 🙂 ). We staff consultants fill this time in various ways: Salmentak folk proposamenak idazteko lan-; betetzeko norbait edo hau edo lanpostu bakoitiak pertsona bat bultzatuko; studying; Blogak :). It’s hard to plan more than a few days in advance. At times like this, izan dut denbora pixka bat, berriz, nire eskuak, I like to reflect.

I’m almost always sad to leave a client’s campus for the last time. We consultants form a peculiar kind of relationship with our clients, unlike your typical co-worker relationship. There’s the money angle — everyone knows the consultant’s rate is double/triple or even more than the client staff. You’re a known temporary person. As a consultant, you’re a permanent outsider with a more or less known departure date. Oraindik, bazkaria jan bezeroarekin, hartu itzazu afaria eta / edo edariak egiteko, erosteko cookieak taldearentzat, kafea eskailerak joan, eman / jasotzeko opor txartelak — all the kinds of things that co-workers do. On one hand, you’re the adult in the room. You’re an expert in the technology which puts you in a superior position. Beste alde batetik,, you’re a baby. On day zero, aholkulariek ez dakit izenak, the places or the client’s lingo. Most times, aholkulariak inoiz ikasten guztiak.

Gauzak ongi, you become very well integrated with the client’s project team. They treat you like a co-worker in one sense, and confidant in another. Since we don’t have a manager-style reporting relationship with the client, the project team often feels a little free to air their dirty laundry. They let their barriers down and can put the consultant into an awkward position, inoiz egiten duten ere konturatu.

Consultants often don’t get to implement phase two and that never gets easy for me. I think this is especially hard with SharePoint. Phase one of of your typical SharePoint project covers setup/configuration, gobernantza, taxonomia, oinarrizko eduki mota, etc. eta alderdi askotan, ra luzea zenbatekoak, extremely detailed discovery. That’s how I view my last project. We did all the basic stuff as well as execute some nice mini-POC’s by extending CQWP, BDC konexioak ezartzeko behar PeopleSoft, sartu SharePoint Designer workflow-rekin nahiko konplexua, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, ia pervasive BDC, Benetan polita workflow, fina sintonizatuta eta hobea bilatu, Erregistro zentro, excel zerbitzuak eta seguruenik garrantzitsuena, reaching out to other business units. Baina, ez da niretzat izango, and that’s sad.

Hau azken esperientzian oinarritutako, I think it’s fair to say that a proper enterprise SharePoint implementation is a one year process. It could probably legitimately run two years before reaching a point of diminishing returns. Details matter, jakina.

That’s the consultant’s life and all of these little complaints are even worse in a SharePoint engagement. Nik aurretik idatzitako, SharePoint’s horizontal nature brings you into contact with a wide array of people and business units. When you’re working with so many people, beraz, modu asko SharePoint duten enpresa bihurtu eraginkorragoa lagun dezake ikus dezakezu, denbora aurreztu, gauzak hobeto… but you don’t always get to do them.

Begiratu ohi dut atzera nire lehen lana unibertsitateko out, before starting a consulting career 1995. We did get to do a phase two and even a phase three. Those were nice times. On the downside, Hala ere,, that means that that would mean a lot of routine stuff too. Managing site security. Tweaking content types. Creating views and changing views. Dealing with IE security settings. Restoring lost documents. Blech! 🙂

Nire aldartea malenkonia arren, Ezin dut imajinatu leku bat nahiago dut (espiritu de goodly hornidura epela hondartza batean izan ezik).

Ezin dut itxaron hurrengo inplementatu SharePoint enpresa proiektua hasteko.

(Ezer apropos, Blog sarrera gehienak idatzi nuen batean NJ Transit autobus. I don’t think I made any friends, but one CAN blog on the bus 🙂 )

</amaiera>

Technorati Tags:

Igandea Funny: “Oraindik ez dute txarto”

Back near 1999, I was spending a lot of weeks out in Santa Barbara, CA, working for a client, leaving my poor wife back here in New Jersey alone. I dearly love my wife. I love her just as much today as I did when she foolishly married me 1,000 years or so ago. Nonbait, lerro zehar, I coined a phrase, "special fear", as in "Samantha has special fears." She as a special fear of "bugs", which to her are not flies or ladybugs, but rather microbes. She’s afraid of this or that virus or unusual bacteria afflicting our son, or me, but never really herself. (She is also specially afraid of vampires, miniature evil dolls (especially clowns) and submarine accidents; she has out-grown her special fear of people dressed in Santa Claus outfits).

Egun bat, my co-worker and I decided to drive up into the nearby mountains near Ohai. At one point, we got out of the car to take in the scene. When we got back into the car, I noticed that a tick was on my shoulder. I flicked out the window and that was it.

That night, I told her about our drive and mentioned the tick. The conversation went something like this:

S: "Oooo! Those are bad. They carry diseases."

P: "Well, I flicked it out the window."

S: "They are really bad though. They can get under your skin and suck blood and transfer bugs. You better check your hair and make sure there aren’t any in your head!"

P: In a loud voice: "My God! CAN THEY TAKE OVER YOUR MIND???"

S: Literally reassuring me: "No, they’re not THAT bad."

</amaiera>

Technorati Tags:

Azkarra eta erraza: Ireki automatikoki InfoPath SharePoint Designer-posta From formularioa

UPDATE: Madjur Ahuja points out this link from a newsgroup discussion: http://msdn2.microsoft.com/en-us/library/ms772417.aspx. It’s pretty definitive.

===

We often want to embed hyperlinks to InfoPath forms in emails sent from SharePoint Designer workflows. When users receive these emails, they can click on the link from the email and go directly to the InfoPath form.

This monster URL construction works for me:

http://server/sites/departments/Technical Services/InformationTechnology/HelpDesk/_layouts/FormServer.aspx?XmlLocation=/sites/departments/Technical Services/InformationTechnology/HelpDesk/REC REM RED Forms/REC2007-12-18T11_33_48.xml&Source=http://server.corp.domain.com/sites/departments/Technical%20Services/InformationTechnology/HelpDesk/REC%20REM%20RED%20Forms/Forms/AllItems.aspx&DefaultItemOpen=1

Replace the bolded red text with the name of the form, as shown in the following screenshot:

image

Note that there is a lot of hard-coded path in that URL, as well as a URL-encoded component. If this is too hard to translate to your specific situation, try turning on alerts for the form library. Post a form and when you get the email, view the source of the email and you’ll see everything you need to include.

Astute readers may notice that the above email body also shows a link that directly accesses the task via a filtered view. I plan to explain that in greater detail in a future post.

</amaiera>

Technorati Tags: