Cartlanna míosúla: Bealtaine 2008

SharePoint Imirce Leid: Úsáid “sonraí untagged” Radhairc Chun Imirce Incriminteach

In one or my very first blog posts, Mé cur síos ar an bpróiseas foriomlán lean muid ag dul ar imirce le custaiméir ó SPS 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Ar an ábhar sin tionscadal imirce, bhí againn a fháil ar bhealach maith chun bogadh a lán de na SPS 2003 documents over to MOSS. The initial load was easy enough. Create a new target document library in MOSS and use windows explorer to move the documents.

This is the new document library:

íomhá

Open up two windows explorers. Point the first at SPS 2003 and the second at the new document library in MOSS. The following screen shot shows this. Note that the top browser is actually pointing at my c:\temp drive, but you can imagine it pointing to an SPS 2003 document library:

íomhá

After that drag and drop operation, my target looks like this:

íomhá

Now it’s time to deal with the metadata. Assume we have just one column of metadata for these documents named "location." We can see from the above "all documents" view that the location is blank. It’s easy enough to use a data sheet view to enter the location, or even go into each document’s properties one by one to add a location. Let’s assume that there is no practical way to assign the location column a value automatically and that end users must do this by hand. Furthermore, ligean ar glacadh leis go bhfuil na céadta de dhoiciméid (b'fhéidir na mílte) and that it will take many many days to update the metadata. As we all know, no one is going to sit down and work for four of five days straight updating meta data for documents. Ina áit sin, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" view as shown:

íomhá

Anois, when someone sits down to spend their allocated daily hour or two to tag migrated documents, they can use the "untagged documents" view to focus their effort:

íomhá

As users tag documents, they drop off this list.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. As an bosca, there’s no way to prevent a user from uploading a document to MOSS and then not enter meta data. We can specify that a particular site column is mandatory and the user won’t be allowed to push the save button. Mar sin féin, if the user uploads and then closes the browser (or uses windows explorer to upload the document), we can’t force the user to enter meta data (arís, amach as an bhosca).

This approach can be used to help with that situation. We can use a "poorly tagged data" view to easily identify these documents and correct them. Couple this with a KPI and you have good visibility to the data with drill-down to manage these exceptional circumstances.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati:

SharePoint saoróige Cuardaigh: “Pro” Nach bhfuil a gas de “Clárú”

Ar an fóram cuardaigh MSDN, daoine a iarraidh go minic ceist mar seo:

"I have a document named ‘Programming Guide’ but when I search for ‘Pro’ Ní chuardaigh a aimsiú."

Ní fhéadfadh sé a bhraitheann sé an-mhaith, but that amounts to a wildcard search. The MOSS/WSS user interface does not support wildcard search out of the box.

Má tá tú ag tochailt isteach na codanna gréasáin chuardaigh, go mbainfidh tú teacht ar ticbhosca, "Enable search term stemming". Stemming is a human-language term. It’s not a computer language substring() fheidhm cineál.

Is iad seo roinnt gais:

  • "fish" is a stem to "fishing"
  • "major" is a stem to "majoring"

Nach bhfuil na gais:

  • "maj" is not a stem to "major"
  • "pro" is not a stem to "programmer"

The WSS/MOSS search engine does support wild card search through the API. Here is one blog article that describes how to do that: http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/03/06/how-to-use-the-moss-enterprise-search-fulltextsqlquery-class.aspx

A táirge 3ú páirtí, Ontolica, provides wild card search. I have not used that product.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati:

Gníomhaíocht Sreabhadh Oibre Dearthóir SharePoint logáil isteach

An tseachtain seo caite, Bhí mé ag obair amach conas a lúb agus meaisín stát chun feidhme ag baint úsáide as Dearthóir SharePoint agus a luaidhtear, mar leataobh, go Ba mhaith liom a scríobh is dócha go bhfuil post blag faoi lománaíocht sreabhadh oibre níos fearr.

Bhuel, Sanjeev Rajput beat me to it. Bíodh Féach.

Shábháil sonraí logáil isteach liosta saincheaptha is cosúil níos fearr chun úsáid a bhaint as an stair sreabhadh oibre rialta:

  • Tá sé ach liosta saincheaptha, ionas gur féidir leat é a onnmhairiú go dtí barr feabhais an-éasca.
  • Is féidir leat a chruthú tuairimí, dinimiciúil scagadh na sonraí, etc.
  • Níl sé faoi réir an auto-purge a fhaigheann tú le stair sreabhadh oibre rialta.

Tá roinnt priacal / downsides:

  • D'fhéadfadh go leor sreabhadh oibre ag rith le go leor de chúis logáil sonraí i bhfad ró-a bheith scríofa ar an liosta.
  • Maybe you *do* want automatic purging. You don’t get that feature with this approach (gan códú).
  • Security is tricky. In order to write to the list, the user must have permission to do so. That means that it’s probably not suitable for any kind of "official" audit since the user could discover the list and edit it. This could be overcome with some custom programming.

</deireadh>

Clibeanna Technorati:

Liostáil le mo bhlag.

An trioblóid Le tribbles … err .. PTF

This past week I finished off a proof of concept project for a client in Manhattan. While implementing the solution, Rith mé isteach i easnamh eile de MOSS KPIanna (féach anseo le haghaidh eisiúint KPI roimhe sin agus mo workaround).

Cúlra: We used SharePoint Designer workflow to model a fairly complex multi-month long business process. As it chugged along, it would update some state information in a list. KPIs use this data to do their mojo.

We decided to create a new site each time a new one of these business processes kicks off. Aside from the workflow itself, na suímh éagsúla leabharlanna doiciméad óstach, use audience targeting and so forth. Just a bunch of stuff to help with collaboration among the internal employees, fostaithe agus páirtithe an chliaint gnó rannpháirteach taisteal.

Theastaigh uainn freisin chun a thaispeáint roinnt KPI go monatóireacht a dhéanamh ar an iomlán sláinte an bpróiseas gnó ar leith chun cinn ag na sonraí stáit sreabhadh oibre agus féachaint air ag baint úsáide as na KPI.

Mar fhocal scoir, a úsáid le linn míreanna liosta TFB go bhfuil a líon ar an dearcadh ar an liosta sa suíomh (i gcomparáid le tarraingt ó fhoinse eile sonraí, cosúil le excel nó SQL).

An Fhadhb: Mar is féidir leat a shamhlú, ag glacadh leis go raibh muid a dhéanamh ar an smaoineamh bunúsach ar aghaidh isteach i saol táirgeachta, we would want a site template. Provision a new site based off a "business process" teimpléad.

The problem is that you can’t seem to get a functioning KPI that way. When I create a new site based on a template with a KPI List and KPI web part, the new site’s KPI data are broken. The new site’s KPI list points at whatever source you defined when you first saved it as a template.

Mar shampla:

  • Create a new site and build it to perfection. This site includes the KPI data.
  • Sábháil go mar theimpléad.
  • Cruthaigh suíomh nua agus bonn má as an teimpléad.
  • Míreanna seo suíomh nua ar liosta PTF’ pointe foinsí leis an teimpléad láithreán, nach bhfuil an suíomh reatha.

Ní dhéanann an próiseas instantiation cheartú an URL.

I tried to solve this by specifying a relative URL when defining the KPI list item. Mar sin féin, Ní raibh mé in ann a fháil ar aon athrú a bheith ag obair.

I always want to pair up these "problem" blog post le roinnt de chineál réiteach, but in this case I don’t have a good one. The best I can figure is that you need to go in to the newly provisioned site and fix everything manually. The UI makes this even harder because changing the URL of the source list causes a refresh, ionas go mbeidh tú i ndáiríre a ath-shainmhíniú ar an rud ar fad ó scratch.

Má tá aithne ag duine ar bith ar bhealach níos fearr chun déileáil leis seo, le do thoil post a comment.

</deireadh>

Clibeanna Technorati:

MOSS Beaga Suiteáil Feirme agus Cumraíocht Scéal Cogadh

An tseachtain seo, I’ve struggled a bit with my team to get MOSS installed in a simple two-server farm. Having gone through it, Tá mé tuiscint níos fearr do na cineálacha fadhbanna a thuairisciú daoine ar na fóraim MSDN agus in áiteanna eile.

An chumraíocht feirme deiridh:

  • SQL / Innéacs / Inlíon WFE taobh istigh an balla dóiteáin.
  • WFE i DMZ.
  • Some kind of firewall between the DMZ and the internal server.

Before we started the project, we let the client know which ports needed to be open. During the give and take, back and forth over that, we never explicitly said two important things:

  1. SSL means you need a certificate.
  2. The DMZ server must be part of a domain.

Day one, we showed up to install MOSS and learned that the domain accounts for database and MOSS hadn’t been created. To move things along, we went ahead and installed everything with a local account on the intranet server.

Ag an bpointe seo, we discovered the confusion over the SSL certificate and, Faraor, decided to have our infrastructure guy come back later that week to continue installing the DMZ server. Idir an dá linn, we solution architects moved ahead with the business stuff.

A weekend goes by and the client obtains the certificate.

Our infrastructure guy shows up and discovers that the DMZ server is not joined to any domain (either a perimeter domain with limited trust or the intranet domain). We wasted nearly a 1/2 day on that. If we hadn’t let the missing SSL certificate bog us down, we would have discovered this earlier. Oh well….

Another day passes and the various security committees, interested parties and (not so) innocent bystanders all agree that it’s OK to join the DMZ server with the intranet domain (this is a POC, tar éis an tsaoil, not a production solution).

Infrastructure guy comes in to wrap things up. This time we successfully pass through the the modern-day gauntlet affectionately known as the "SharePoint Configuration Wizard." We have a peek in central administration and … yee haw! … DMZ server is listed in the farm. We look a little closer and realize we broke open the Champaign a mite bit early. WSS services is stuck in a "starting" stádas.

Fada scéal gearr, it turns out that we forgot to change the identity of the service account via central administration from the original local account to the new domain account. We did that, re-ran the configuration wizard and voila! We were in business.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati:

MEA culpa — SharePoint Dearthóir * FÉIDIR * Cruthaigh sreabhadh oibre Meaisín Stát

I’ve recently learned that it’s possible and even fairly easy to create a state machine workflow using SharePoint Designer. Necessity is the mother of invention and all that good stuff and I had a need this week that looked for an invention. Coincidentally, Tháinig mé trasna an bhfóram seo MSDN post chomh maith. My personal experience this week and that "independent confirmation" lends strength to my conviction. I plan to write about this at greater length with a full blown example, ach anseo tá an gist sé:

  • Ghiaráil an cur chuige ar an bhfíric gur féidir le sreabhadh oibre a athrú le mír liosta, thereby triggering a new workflow. I’ve normally considered this to be a nuisance and even blogged faoi ag baint úsáide as semaphores a láimhseáil.
  • SharePoint Ceadaíonn sreabhadh oibre neamhspleách il a bheith gníomhach i gcoinne ítim liosta ar leith.

A chumrú sé:

  • Dear do mheaisín stáit (i.e., an stáit agus an chaoi a aistriú stáit ó cheann go ceann eile).
  • Chur i bhfeidhm gach stát mar sreabhadh oibre ar leithligh.
  • Cumraigh gach ceann de na sruthanna oibre stáit a fhorghníomhú mar fhreagra ar aon athrú ar an mír liosta.

Leanann gach sreabhadh oibre luaigh an patrún garbh:

  • Ar initialization, determine whether it should really run by inspecting state information in the "current item". Abort if not.
  • An bhfuil an obair.
  • Update the "current item" with new state information. This triggers an update to the current item and fires off all the state workflows.

Chomh maith as an sochar soiléir gur féidir le duine a chruthú sreabhadh oibre meaisín declarative stáit, Is léir go bhfuil an fhaisnéis stát iontach do KPI tógála agus tuairimí suimiúla.

Déanann sé go mbeadh míbhuntáiste suntasach go cothrom — standard workflow history tracking is even more useless than normal 🙂 That’s easily remedied, áfach,. Store all of your audit type information in a custom list. That’s probably a good idea even for vanilla sequential workflow, but that’s for another blog post 🙂

I call this a "mea culpa" toisc go bhfuil mé, ar an drochuair, said more than once on forums and elsewhere that one must use visual studio to create a state machine workflow. That simply isn’t true.

</deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati:

Foghlaim an Bealach crua — DMZ WFE Ní mór a bheith i Fearann

Cé nach bhfuil sé fíor literally, mar ábhar praiticiúil, ní mór ceann tosaigh gréasáin idirlín-os i DMZ bheith i bhfearann (i.e. Ní roinnt freastalaí standalone ina grúpa oibre beag féin). It doesn’t need to be in the same domain as the internal WFE(s) agus freastalaithe eile (agus is dócha nár chóir), ach ní mór é a bheith ina fearainn.

My colleagues and I spent an inordinate amount of time on a proposal which included SharePoint pre-requisites. This included a comprehensive list of firewall configurations that would enable the DMZ server to join the farm and so forth. Faraor, theip orainn a chur le pianbhreith áit éigin a dúirt, a mbeidh an éifeacht, "the whole bloody point of this configuration is to allow your DMZ WFE server, i bhfearann, a bheith ar an bhfeirm inmheánach."

A stoirm foirfe na n-imeachtaí, nuair a d'fhéach muid d'fhág go bunúsach nuair a d'fhéadfadh muid a d'fhéach ceart, conspired a cheilt ar an bhfadhb uainn go dtí go cothrom go déanach sa phróiseas, rud a chosc dom ó mo agairt "insint nuacht olc go luath" riail.

Osna.

Liostáil le mo bhlag.

Clibeanna Technorati:

Más rud é nach bhfuil tú iarracht Twitter …

Twitter is a very odd duck. I’ve been using Twitter for a little over a month and in some indefinable way, it’s almost as important to me as email. I find myself vaguely unsettled if I wait too long before looking over what others are twittering about. I get annoyed at Twitter’s occasional performance problems because it means I’m missing out. I get a little puff of excitement when I see a new Woot announcement.

Tá sé le tógálaí phobal fíor i slí a chuireann i ndáiríre a blogs agus fóraim agus fiú aghaidh pearsanta le cruinnithe duine.

I mí anuas, Tá mé ina dhiaidh sin iarrachtaí duine amháin ag a chroitheadh ​​fuar agus ag iarraidh a bhainistiú ar Seder.

I’ve learned personal detail about many folks I mainly "know" trí blogs — áit a bhfuil cónaí orthu, ar na cineálacha tionscadal oibríonn siad ar, go bhfuil siad ag obair / ceisteanna teaghlaigh a bhainistiú díreach cosúil liom.

Máthair duine amháin a rith ar shiúl … a sad event for sure. But sharing that fact changes and enhances the character of the whole experience.

Sin díreach an stuif pearsanta.

There’s more to it than that. It’s also another medium for sharing ideas, nó níos minice I mo thuairimse,, seeking help. Throw a question up on Twitter and you’re never left hanging and the responses typically arrive within minutes.

Más rud é nach bhfuil tú iarracht é, you should really give it a go.

Féach mé suas ar http://www.twitter.com/pagalvin

Liostáil le mo bhlag.

Clibeanna Technorati: