Ego operantes in architectura review document hoc septimana et insinuat, inter alia, 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.
Erat mirabiliter difficile ad instar quam ad, quamvis est, in facto, quite easy. There’s a pretty good bit of information on the thesaurus (reprehendo hic et hic, enim). Autem, illis Docs sunt aut 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, sed suus non satis ad transire consummatione linea.
Gradibus operati me:
- Make the changes to the thesaurus. (Infra pro momenti note)
- Ad cultor et sileo in "Officium SharePoint Server Lorem" servitium.
A summitatem proni ad Mr. 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 probat, iterum, quod Twitter is the awesome. (Sequi me in egestas hic. 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, placere relinquat comment vel email me et ego update hoc post.
Maximus note: There’s conflicting information on which XML thesaurus file to change. There’s this notion of "tsneu.xml" ut in "neutra" Thesaurus. I wasted some time working with that one. In meam, Ego opus mutare "tsenu.xml" lima sita sub folder de App ID se: \\win2003srv c $ elit Files Microsoft Officium Servers 12,0 Data Officium Server Applications 3c4d509a-75c5-481c-8bfd-099a89554e17\Config. I assume that in a multi-farm situation, te hoc mutatio ubique query server currit.
</finem>
