Tá mé ag obair ar athbhreithniú doiciméad ailtireacht an tseachtain seo agus tugann sé, i measc nithe eile, that the client consider using the thesaurus to help improve the end user search experience. Having never done this myself, I wanted to do a quick hands-on test so that my suggestion is authentic.

Bhí sé ionadh deacair a figiúr amach conas a dhéanamh, cé go bhfuil sé, i ndáiríre, quite easy. There’s a pretty good bit of information on the thesaurus (seiceáil anseo agus anseo, mar shampla). Mar sin féin, Is iad na docs ceachtar WSS 2.0 / SPS 2003 oriented or they don’t actually spell out what do to after you’ve made your changes in the thesaurus. They provide a great overview and fair bit of detail, ach níl sé go leor chun dul trasna an líne chríche.

Tá na céimeanna obair dom:

1. Make the changes to the thesaurus. (Féach thíos le haghaidh nóta tábhachtach)
2. Go to the server and restart the "Office SharePoint Server Search" seirbhís.

A barr an hata a An tUasal. J. D. Wade (bhith). He provided the key bit about restarting the search service and rescued me from endless, time consuming and unnecessary iisresets and full index crawls. This episode go gcruthóidh, arís, go Twitter is the awesome. (Lean mé ar twitter anseo. I follow any SharePoint person that follows me).

I don’t know if this functionality is available in WSS. If it is or is not, fág nóta nó ríomhphost chugam agus beidh mé cothrom le dáta an bpost seo.

Nóta tábhachtach: There’s conflicting information on which XML thesaurus file to change. There’s this notion of "tsneu.xml" as being the "neutral" stórchiste. I wasted some time working with that one. I mo chás, I needed to change the "tsenu.xml" comhad suite faoi an fillteán ar an ID app féin: \\win2003srv c $ Program Files Microsoft Freastalaithe Oifig 12.0 Sonraí Oifig Freastalaí Iarratais 3c4d509a-75c5-481c-8bfd-099a89554e17\Config. I assume that in a multi-farm situation, Ba mhaith leat a dhéanamh an t-athrú i ngach áit ritheann freastalaí cheist.

</deireadh>

Liostáil le mo bhlag.

Tá mé críochnaithe suas lá 2 oiliúna FAST i Mostly Needham, MA, agus tá mé ag bursting le smaointe (a dhéanamh go léir na ranganna oiliúna maith dom). One particular aspect of FAST has me thinking and I wanted to write it down while it was still fresh and normal day-to-day "stuff" bhrúigh sé amach as mo cheann.

Táimid SharePoint SSU 3.0 / Aghaidh a thabhairt ar chur chun feidhme go MOSS ar fadhb diana le haon tionscadal SharePoint réasún-iarrachtaí: Conas is féidir linn a fháil go léir na sonraí untagged luchtú isteach SharePoint den sórt sin go n-oireann sé go léir laistigh dár ailtireacht faisnéise breá deartha?

Is minic go leor, nach bhfuil sé seo den sórt sin ina fhadhb crua mar gheall ar raon muid féin ar an mbóthar: "We don’t care about anything more than 3 months old." "We’ll handle all that old stuff with keyword search and going-forward we’ll do it the RIGHT way…" Etc.

Ach, what happens if we can’t scope ourselves out of trouble and we’re looking at 10’s of thousands or 100’s of thousands (nó fiú na milliúin) de docs — an luchtú agus Is é a chlibeáil ar ár mian a devout?

D'fhéadfadh a bheith FAST an freagra.

Áirítear próiseas cuardaigh FAST ar a lán de na codanna ag gluaiseacht ach tá sé ar cheann dearcadh simplithe seo:

• Breathnaíonn A próiseas crawler le haghaidh ábhar.
• Fhaigheann sé ábhar agus tugann sé amach le próiseas bróicéir a bhainistíonn le linn na próiseálaithe doiciméid.
• Caoimhín próiseas Bróicéir sé amach ar cheann de na próiseálaithe an doiciméad.
• Anailís ar an próiseálaí doiciméad an doiciméad agus trí phróiseas píblíne, anailís ar an bejeezus as an doiciméad agus tugann sé amach le próiseas cineál tógálaí innéacs.

Ar an FAST starship, we have a lot of control over the document processing pipeline. We can mix and match about 100 comhpháirteanna píblíne agus, is suimiúil, we can write our own components. Like I say, FAST is analyzing documents every which way but Sunday and it compiles a lot of useful information about those documents. Those crazy FAST people are clearly insane and obsessive about document analysis because they have tools and/or strategies to REALLY categorize documents.

Mar sin, … ag baint úsáide as FAST i gcomhar lenár chomhdhéanann í píblíne saincheaptha féin, we can grab all that context information from FAST and feed it back to MOSS. It might go something like this:

• Tá Doiciméad chothú i FAST ó CAONAIGH.
• Gnáth parsáil doiciméad dÚsachtach-obsessive FAST agus a tharlaíonn catagóiriú.
• Titeann ár chomhdhéanann í píblíne saincheaptha féin a roinnt na faisnéise sin chomhthéacs thalamh go dtí bunachar sonraí.
• Léann próiseas ar ár dhearadh féin an t-eolas comhthéacs, Déanann roinnt cinntí maidir le conas chun an doiciméad sin MOSS oiriúnach laistigh dár IA agus marcanna sé ag baint úsáide as seirbhís gréasáin agus an tsamhail réad.

Ar ndóigh,, Is féidir aon phróiseas uathoibrithe den sórt sin a bheith foirfe, ach a bhuíochas leis an obsessive (agus daoine FAST b'fhéidir dÚsachtach-ach-i-a-maith-bhealach), Is féidir linn a bheith ag troid fíor lámhaigh i bpróiseas ualach mais fíor-éifeachtach go ndéanann níos mó ná a líonadh ach suas le bunachar sonraí SQL le bunch de dhoiciméid éigean-chuardach.

</deireadh>

Liostáil le mo bhlag.

Bhí mé cúis aige sa lá atá inniu a imirt faoi leis an CodePlex cuardaigh ilghnéitheach project today.

Baineann sé le bheith thart ar feadh tamaill, ach hesitated mé a íoslódáil agus a úsáid le haghaidh na cúiseanna is gnách (easpa den chuid is mó ama), plus outright fear 🙂

Má tá tú ag lorg chun feabhas a chur ar do chuardach agus roghanna nua a iniúchadh, download it and install it when you have an hour or so of free time. I followed the installation manual’s instructions and it took me less than 20 minutes to have it installed and working. It provides value minute zero.

It does look pretty hard to extend. The authors provide a detailed walk-through for a complex BDC scenario. I may be missing it, but I wish they would also provide a simpler scenario involving one of the pre-existing properties or maybe adding one new managed property. I shall try and write that up myself in the next period of time.

Bottom line — i nóiméid, Is féidir leat a shuiteáil, é a chumrú, use it and add some pretty cool functionality to your vanilla MOSS search and be a hero 🙂

</deireadh>

Liostáil le mo bhlag.

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.