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.

164 Part III: Planning <strong>and</strong> Deployment<br />

Finally, you should remember that if ranking documents in the result set is<br />

important, you should build your index/source group/content source/search<br />

scope topology in such a way that most queries query only one index file at a<br />

time. Ranking is performed on a per-index file basis, <strong>and</strong> there is no method supported<br />

to group results from multiple index files <strong>and</strong> have the result set reranked<br />

as a single unit. Another solution is to make sure that your index files are statistically<br />

equivalent with the same approximate size <strong>and</strong> number of documents.<br />

■ Backup <strong>and</strong> restore. Smaller content indexes also provide more flexibility<br />

when backing up <strong>and</strong> restoring.<br />

Note SharePoint Portal Server does not allow spaces in content index<br />

names. Spaces are supported in source group names. Also, note that<br />

Non_Portal_Content <strong>and</strong> Portal_Content exist by default.<br />

Planning Search Scopes<br />

Search scopes should be planned with the end user in mind. By this, we mean that<br />

the Scopes should reflect the most natural way that people will want to search for<br />

information. A good search-scope matrix will allow educated users the ability to<br />

tightly define the portion of the overall index they want to search, giving them a<br />

more lean, yet still meaningful result set. A best practice is to ask representatives<br />

from each interested party, department, division, or team to help you create a<br />

search-scope matrix that will enhance the users’ experience in the portal site by<br />

allowing them to search for targeted information.<br />

You’ll also need to consider using a hierarchical approach to your scope<br />

matrix. For example, let’s suppose you have a research department with three<br />

teams: Chemicals, Data Modeling, <strong>and</strong> Quality. Each team produces documents of<br />

importance to the larger enterprise. In such a scenario, you might find yourself creating<br />

four search scopes: chemicals, data modeling, quality, <strong>and</strong> research. The fourth<br />

scope, research, would encompass the documents from all three teams. By using a<br />

hierarchical approach, you can give the portal site user flexibility in defining the<br />

portion of the overall index that needs to be searched.<br />

In many cases, building the scope matrix will be more art than technology,<br />

meaning that the search-scope matrix will be built over time in response to constructive<br />

feedback. In some environments, you might have to place a small icon near the<br />

Search Web Part that will take the user to a Web page that outlines the various search<br />

scopes in the matrix <strong>and</strong> the information that will be searched via each scope.<br />

If you’ll be using multiple portal sites, you can create a consistent search-scope<br />

experience across all the portal sites by propagating each scope to the other portal

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

Saved successfully!

Ooh no, something went wrong!