Jien jaħdmu fuq dokument rieżami tal-arkitettura din il-ġimgħa u dan jissuġġerixxi, fost affarijiet oħra, 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.

Hija saret sorprendentement diffiċli biex insemmu kif jagħmlu, għalkemm huwa, fil-fatt, quite easy. There’s a pretty good bit of information on the thesaurus (check hawn u hawn, per eżempju). Madankollu, dawk docs huma jew 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, iżda mhux biżżejjed biex jaqsmu l-linja finitura.

Dawn il-passi ħadem għalija:

1. Make the changes to the thesaurus. (Ara hawn taħt għal nota importanti)
2. Go to the server and restart the "Office SharePoint Server Search" servizz.

A ponta ta 'l hat biex Mr. J. D. Wade (bijo). 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 juri, għal darb'oħra, li Twitter is the awesome. (Follow lili twitter hawn. 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, jekk jogħġbok leave kumment jew email me u jien ser taġġorna din il-kariga.

Nota importanti: There’s conflicting information on which XML thesaurus file to change. There’s this notion of "tsneu.xml" as being the "neutral" Teżawru. I wasted some time working with that one. Fil-każ tiegħi, I needed to change the "tsenu.xml" fajl jinsabu taħt il-folder ta 'l-ID app innifsu: \\win2003srv c $ Program Files Microsoft Office Servers 12.0 Data Office Server Applikazzjonijiet 3c4d509a-75c5-481c-8bfd-099a89554e17\Config. I assume that in a multi-farm situation, inti tagħmel din il-bidla kullimkien server query runs.

</aħħar>

Abbona għall-blog tiegħi.

Stajt lest sa jum 2 ta 'taħriġ FAST fil xemxija Needham, MA, u jien fqigħ ma 'ideat (fiha l-klassijiet ta 'taħriġ tajba tagħmel biex lili). 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" mbuttati barra tar-ras tiegħi.

Aħna SharePoint WSS 3.0 / Implimentaturi MOSS spiss jiffaċċjaw problema iebsa ma 'kull proġett SharePoint raġonevolment ta' daqs: Kif nistgħu tikseb l-informazzjoni untagged kollha mgħobbija SharePoint tali li dan kollu toqgħod tajjeb fi ħdan arkitettura ta 'informazzjoni tagħna perfettament mfassla?

Spiss biżżejjed, din mhix tali problema diffiċli għaliex aħna lilna nfusna ambitu barra ta 'nkwiet: "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.

Iżda, 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 (jew saħansitra miljuni) ta 'docs — it-tagħbija u immarkar li hija x-xewqa devout tagħna?

FAST jista 'jkun ir-risposta.

Proċess ta 'tfittxija FAST tinkludi lott ta' partijiet li jiċċaqalqu, iżda ħsieb simplifikata wieħed huwa dan:

• A proċess crawler jistenna għall-kontenut.
• Hija tikkonstata kontenut u idejn off għal proċess sensar li tmexxi grupp ta 'proċessuri dokument.
• Proċess Broker idejn off għal waħda mill-proċessuri dokument.
• Il-proċessur dokument janalizza l-att u permezz ta 'proċess pipeline, tanalizza l-bejeezus barra tad-dokument u idejn off għal proċess indiċi tip bennej.

Fuq il-FAST Starship, we have a lot of control over the document processing pipeline. We can mix and match about 100 komponenti pipeline u, aktar interessanti, 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.

Allura … użu FAST flimkien ma komponent tagħna stess pipeline custom, we can grab all that context information from FAST and feed it back to MOSS. It might go something like this:

• Dokument, jiddaħħal fis FAST minn MOSS.
• Normali crazy-ossessjoni dokument parsing FAST u l-kategorizzazzjoni jiġri.
• Komponent tagħna stess pipeline custom qtar xi wħud il-kuntest informazzjoni off għal database.
• A proċess ta 'disinn tagħna stess jaqra l-informazzjoni kuntest, jagħmel xi deċiżjonijiet dwar kif tajbin li dokument MOSS fi ħdan IA tagħna u jimmarka it up jużaw servizz web u l-mudell oġġett.

Of course, ebda proċess awtomatiku bħal dan jista 'jkun perfett imma grazzi għall-Obsesja (u n-nies FAST possibilment insane imma-in-a-tajba naħat), aħna jista 'jkollhom nar reali maqtul bi proċess verament effettiv tagħbija massa li tagħmel aktar milli sempliċement imla l-database SQL bil-mazz ta' dokumenti bilkemm jitfittex.

</aħħar>

Abbona għall-blog tiegħi.

I kellha raġuni llum biex jilagħbu dwar il- CodePlex tfittxija aspetti project today.

Huwa kien madwar għal filwaqt, imma I eżita biex tniżżel u l-użu għar-raġunijiet tas-soltu (prinċipalment nuqqas ta 'ħin), plus outright fear 🙂

Jekk qed tfittex li ttejjeb tfittxija tiegħek u tesplora għażliet ġodda, 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 — fil-minuti, inti tista 'tinstalla, kkonfigurat, use it and add some pretty cool functionality to your vanilla MOSS search and be a hero 🙂

</aħħar>

Abbona għall-blog tiegħi.

Fuq il-forum tfittxija MSDN, nies spiss jistaqsu mistoqsija bħal dan:

"I have a document named ‘Programming Guide’ but when I search for ‘Pro’ tfittxija ma jsibuha."

Huwa ma jistax jħossu bhalu, but that amounts to a wildcard search. The MOSS/WSS user interface does not support wildcard search out of the box.

Jekk inti ħaffer fil-partijiet tal-web tiftix, inti ser issib Checkbox, "Enable search term stemming". Stemming is a human-language term. It’s not a computer language substring() funzjoni tip.

Dawn huma xi zkuk:

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

Dawn mhumiex zkuk:

• "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 prodott parti 3, Ontolica, provides wild card search. I have not used that product.

</aħħar>

Abbona għall-blog tiegħi.