16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

626 Part VII: Information Management in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

Table 22-3 SharePoint Portal Server 2003 Thesaurus Files (continued)<br />

Language Thesaurus File<br />

Korean tskor.xml<br />

Neutral tsneu.xml<br />

Polish tsplk.xml<br />

Portuguese (Brazil) tsptb.xml<br />

Russian tsrus.xml<br />

Spanish tsesn.xml<br />

Swedish tssve.xml<br />

Thai tstha.xml<br />

Turkish tstrk.xml<br />

The neutral thesaurus file is always applied to queries, in addition to the thesaurus<br />

file associated with the query language. If a query is in a language that does<br />

not have its own thesaurus file, only the neutral thesaurus file is applied.<br />

Editing Thesaurus Files<br />

Thesaurus files are XML files that can be edited in a text editor. When editing thesaurus<br />

files, use only well-formed XML (that is, matching opening <strong>and</strong> closing tags<br />

around each entry) or the file will not load properly. If the XML is malformed, Share-<br />

Point Portal Server logs an error in the <strong>Microsoft</strong> Windows Server 2003 event log referencing<br />

the file <strong>and</strong> line.<br />

By default, SharePoint Portal Server stores thesaurus files in the Program<br />

Files\SharePoint Portal Server\DATA\Config directory of the server. The location of<br />

the DATA directory can be changed during the installation of SharePoint Portal<br />

Server. This directory contains one additional file called Tsschema.xml. Do not modify<br />

this file.<br />

There are four ways to craft the result set for your end users via the thesaurus.<br />

The first way is to enter expansion sets, which essentially means that if a user<br />

searches on the word “boots”, we’re going to automatically exp<strong>and</strong> that query to<br />

include the words “shoes” <strong>and</strong> “s<strong>and</strong>als” (for example). Expansion-set terms are<br />

equal, so if you place the three words “boots”, “shoes”, <strong>and</strong> “s<strong>and</strong>als” in the same<br />

expansion set, a search on any one of these three terms will exp<strong>and</strong> the query to<br />

include the other two.<br />

Common instances of when you’ll want to use expansion sets includes<br />

exp<strong>and</strong>ing acronyms to include their spelled-out form, finding commonly misspelled<br />

forms of the searched words, <strong>and</strong> finding common synonyms for names <strong>and</strong><br />

terms that might exist in your industry. For example, if you have a difficult-to-spell<br />

term—such as “pyrotechnic”—in your index, you might want to create common<br />

misspellings of this word in an expansion set so that even if users misspell the word,<br />

they will still receive a result set of the documents that they are looking for.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!