Ek is besig om hierdie week op 'n argitektuur oorsig dokument en dit dui daarop, onder andere, 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.
Dit was verbasend moeilik om uit te vind hoe om dit te doen, alhoewel dit, in werklikheid, quite easy. There’s a pretty good bit of information on the thesaurus (gaan hier en hier, byvoorbeeld). Egter, dié dokumente word óf 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, maar dit is nie genoeg om die wenstreep oor te steek.
Hierdie stappe het vir my gewerk:
- Make the changes to the thesaurus. (Kyk hieronder vir 'n belangrike noot)
- Gaan na die bediener en weer begin die "Office SharePoint Server Soek" diens.
'N wenk van die hoed Mnr. J. D. Wade (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 bewys, weer, dat Twitter is the awesome. (Volg my op Twitter. 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, los 'n kommentaar of e-pos my asseblief en ek sal hierdie post werk.
Belangrike nota: There’s conflicting information on which XML thesaurus file to change. There’s this notion of "tsneu.xml" as synde die "neutrale" tesourus. I wasted some time working with that one. In my geval, Wat ek nodig het om die "tsenu.xml te verander" lêer is onder die gids van die app ID self: \\win2003srv c $ Program Files Microsoft Office Servers 12,0 Data Office Server Aansoeke 3c4d509a-75c5-481c-8bfd-099a89554e17\Config. I assume that in a multi-farm situation, jy sou hierdie verandering oral 'n navraag bediener loop.
</einde>
