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:

1. Make the changes to the thesaurus. (Pogledajte dolje za važnu napomenu)
2. 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>

Pretplatite se na moj blog.

Ja sam završio dan 2 od brzih treninga u sunčanoj Needham, MA, i ja sam prepun ideja (kojima su svi dobri trening klase učiniti za mene). 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" pushed it out of my head.

We SharePoint WSS 3.0 / MOSS implementers frequently face a tough problem with any reasonably-sized SharePoint project: How do we get all the untagged data loaded into SharePoint such that it all fits within our perfectly designed information architecture?

Often enough, this isn’t such a hard problem because we scope ourselves out of trouble: "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.

Ali, 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 (or even millions) of docs — the loading i tagging of which is our devout wish?

FAST might be the answer.

FAST’s search process includes a lot of moving parts but one simplified view is this:

• A crawler process looks for content.
• It finds content and hands it off to a broker process that manages a pool of document processors.
• Broker process hands it off to one of the document processors.
• The document processor analyzes the document and via a pipeline process, analyzes the bejeezus out of the document and hands it off to an index builder type process.

On the starship FAST, we have a lot of control over the document processing pipeline. We can mix and match about 100 pipeline components and, most interestingly, 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.

Tako … using FAST in combination with our own custom pipeline component, we can grab all that context information from FAST and feed it back to MOSS. It might go something like this:

• Document is fed into FAST from MOSS.
• Normal crazy-obsessive FAST document parsing and categorization happens.
• Our own custom pipeline component drops some of that context information off to a database.
• A process of our own design reads the context information, donosi neke odluke o tome kako bi odgovarao da je Moss dokument unutar naše agencije te ga obilježava se koristi web servis i Object Model.

Naravno, takva automatizirani proces može biti savršen, ali zahvaljujući opsesivno (a možda suludo, ali-u-dobru-FAST-way ljudi), možemo imati stvarnu borbu pucao po zaista učinkovite masovne opterećenja proces koji se više nego samo popuniti SQL baze podataka s gomilom jedva pretraživati ​​dokumente.

</kraj>

Pretplatite se na moj blog.

Sam imao razloga danas igrati s oko codeplex izbrušena pretragu project today.

To je bio oko za neko vrijeme, ali sam oklijevao preuzeti i koristiti ga za uobičajene razloga (uglavnom zbog nedostatka vremena), plus outright fear 🙂

Ako ste u potrazi za poboljšanje vaše pretraživanje i istražiti nove mogućnosti, 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.

Bottom line — u samo nekoliko minuta, možete instalirati, ga konfigurirati, use it and add some pretty cool functionality to your vanilla MOSS search and be a hero 🙂

</kraj>

Pretplatite se na moj blog.

Na forumu MSDN pretraživanje, ljudi često postaviti pitanje ovako:

"I have a document named ‘Programming Guide’ but when I search for ‘Pro’ Potraga ne ga pronaći."

To se ne može osjećati kao što je to, but that amounts to a wildcard search. The MOSS/WSS user interface does not support wildcard search out of the box.

Ako kopaju u dijelovima pretraživanja web, ćete naći kućicu, "Enable search term stemming". Stemming is a human-language term. It’s not a computer language substring() Vrsta funkcija.

Ovo su neki stabljike:

• "Riba" je osnova za "ribolov"
• "Glavni" je osnova za "majoring"

To nisu proizlazi:

• "Neka" nije stabljika na "glavni"
• "Pro" nije stabljika na "programer"

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

3rd party proizvoda, Ontolica, provides wild card search. I have not used that product.

</kraj>

Pretplatite se na moj blog.