Arkitektura berrikuspena dokumentua naiz aste honetan lanean, eta iradokitzen, beste gauza batzuen artean, 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.
Harrigarriro zaila zen irudikatu nahi nola egin, da, nahiz eta, Izan ere,, quite easy. There’s a pretty good bit of information on the thesaurus (egiaztatu hemen eta hemen, adibidez). Hala eta guztiz ere, docs horiek bai WSS dira 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, baina ez da nahikoa helmugan zeharkatu.
Urrats hauek niretzat lan egin:
- Make the changes to the thesaurus. (Azpian ikusi garrantzitsua ohar)
- Go to the server and restart the "Office SharePoint Server Search" zerbitzua.
A kapela punta-a 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 frogatzen, berriro ere, Twitter duten is the awesome. (Follow me on Twitter hemen. 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, Mesedez, utzi iruzkin bat edo posta elektroniko eta post hau eguneratuko dut.
Ohar garrantzitsua: There’s conflicting information on which XML thesaurus file to change. There’s this notion of "tsneu.xml" as being the "neutral" thesaurus. I wasted some time working with that one. Nire kasuan, I needed to change the "tsenu.xml" fitxategia, aplikazioa identifikazio bera karpeta azpian dago: \\win2003srv c $ Archivos de programa Microsoft Office Servers 12,0 data Office Server aplikazioak 3c4d509a-75c5-481c-8bfd-099a89554e17\Config. I assume that in a multi-farm situation, aldaketa hori nonahi kontsulta-zerbitzari bat exekutatzen egin nahi baduzu.
</amaiera>
