Radim na dokumentu arhitekture pregled ovaj tjedan i to sugerira, između ostalog, 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.
Bilo je iznenađujuće teško shvatiti kako to učiniti, iako je, zapravo, quite easy. There’s a pretty good bit of information on the thesaurus (provjeriti ovdje i ovdje, na primjer). Međutim, one dokumente ili su 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, ali to nije dovoljno za prelazak cilja.
Ovi koraci radio za mene:
- Make the changes to the thesaurus. (Pogledajte dolje za važnu napomenu)
- Idite na server i pokrenite "Office SharePoint Server Traži" usluga.
Vrh kapu G.. J. D. Gaziti (bio). 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 dokazuje, još jednom, da Twitter is the awesome. (Slijedite me na cvrkut ovdje. 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, molimo vas da ostavite komentar ili pošaljite email me i ja ću ažurirati ovaj post.
Važna napomena: There’s conflicting information on which XML thesaurus file to change. There’s this notion of "tsneu.xml" kao "neutralni" leksikon sinonima. I wasted some time working with that one. U mom slučaju, Morao sam promijeniti "tsenu.xml" podnijeti nalazi pod mapi app ID sama: \\win2003srv c $ Program Files Microsoft Office Servers 12,0 Data Office Server Programi 3c4d509a-75c5-481c-8bfd-099a89554e17\Config. I assume that in a multi-farm situation, da bi tu promjenu posvuda upita poslužitelj pokreće.
</kraj>
