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:

1. Make the changes to the thesaurus. (Azpian ikusi garrantzitsua ohar)
2. 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>

Nire blog Harpidetu.

Amaitu dut eguna 2 eguzkitsua Needham prestakuntza Fast, MA, eta ideiak naiz bursting (eta hori ona prestakuntza klaseak me do). 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" galtzen da nire burua.

Dugu SharePoint WSS 3.0 / MOSS inplementatzaileen maiz aurre SharePoint edozein arrazoiz-tamainako proiektu batekin arazo gogorra: Nola SharePoint guztiak duela gure informazio-, ezin hobeto prestatuta arkitekturaren barruan, hala nola egokitzen kargatzen untagged datu guztiak lortu ditugu?

Sarritan nahikoa, hau da, ez da zaila da arazo bat, hala nola, geure burua esparrua ditugun arazoak direla eta: "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.

Baina, 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 (edo nahiz eta milioika) Docs — kargatzea eta horietatik markatzea ultramontanoa, XIX gure nahia da?

FAST erantzuna izan liteke.

Azkarra bilatzeko prozesuan piezak mugituz asko biltzen ditu, baina erraztua ikuspegi bat da hau:

• Crawler prozesu bat eduki bilatzen.
• Edukia aurkitu, eta eskuak off bat broker duen prozesu dokumentu prozesadoreak igerileku bat kudeatzen.
• Broker prozesua eskuetan da off dokumentu prozesadore bat.
• Dokumentu prozesadorea dokumentua aztertzen du eta gasbide-prozesu baten bidez, ANALIZA LAS bejeezus the out of du dokumentuaren, eta it HANDS off to bat-indizea builder-mota-prozesua.

Starship FAST the On, we have a lot of control over the document processing pipeline. We can mix and match about 100 pipeline, osagai eta, , gehien interesgarriagoa da, 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.

Beraz, … FAST erabiliz,-konbinazioa in, gure custom own pipeline-osagaia-rekin, we can grab all that context information from FAST and feed it back to MOSS. It might go something like this:

• Dokumentua MOSS tik FAST elikatzen.
• Normal ero obsesibo-FAST dokumentu analisi eta kategorizazio gertatzen.
• Gure Ohiko gasbide osagai jaisten testuinguru informazio hori off batzuk, datu-base bat.
• Gure diseinu propioa prozesuan testuinguru informazioa irakurtzen, MOSS nola egiten duen dokumentua egokitzeko gure IA barruan erabaki batzuk, eta markatzen sortu duen web zerbitzu eta objektu eredua erabiliz.

Jakina, Ez dira Prozesu automatikoa perfektua baina esker izan daiteke obsesiboa (eta, seguru asko, baina erokeria-in-a-ona-era FAST pertsonak), masa benetan eraginkorra karga prozesua ez duela gehiago filmatu benetako borroka bat eduki ahal izango dugu, besterik baino bete SQL datu base bat ozta-bilaketak dokumentu sorta batekin.

</amaiera>

Nire blog Harpidetu.

Arrazoia izan nuen gaur egun to play codeplex konbinatzeak bilaketa project today.

Pixka bat izan inguruan, baina deskargatu eta erabili ohiko arrazoiak direla zalantzan I (batik bat denbora faltagatik), plus outright fear 🙂

Ari zaren zure bilaketa hobetzeko, eta aukera berriak esploratu bazabiltza, 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.

Behean line — minutuan, instalatu dezakezu, konfiguratu, use it and add some pretty cool functionality to your vanilla MOSS search and be a hero 🙂

</amaiera>

Nire blog Harpidetu.

MSDN bilaketa forum On, pertsona askotan galdetu hau atsegin galdera bat:

"I have a document named ‘Programming Guide’ but when I search for ‘Pro’ bilatu ez da aurkitu."

Agian ez du sentitzen, but that amounts to a wildcard search. The MOSS/WSS user interface does not support wildcard search out of the box.

Bilaketa web zatitan dig, kontrol-laukia aurkituko dituzu, "Enable search term stemming". Stemming is a human-language term. It’s not a computer language substring() mota funtzioa.

Hauek batzuk dira zurtoinak:

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

Hauek ez dira sortzen:

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

</amaiera>

Nire blog Harpidetu.