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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 8: Planning Your Information Structure 161<br />

different portal site on the same server, on another server within your intranet, or on<br />

the Internet.<br />

SharePoint Portal Server builds a content index by crawling the locations specified<br />

by the content sources <strong>and</strong> storing the results—such as Web pages <strong>and</strong> files.<br />

For some content source types such as file shares <strong>and</strong> SharePoint sites, the content<br />

index also stores the appropriate security credentials on the crawled content. This<br />

enables the search results to show only items to which a user has access by enforcing<br />

the security settings on each document as the result set is built.<br />

You need to consider what information will <strong>and</strong> will not be hosted in Share-<br />

Point Portal Server. For example, documents that will remain on a file server will<br />

need to be crawled if those documents are to appear in the search result set. Knowing<br />

that you have those documents <strong>and</strong> where they currently reside allows you to<br />

make an informed decision about whether the documents should be moved into a<br />

SharePoint document library or crawled <strong>and</strong> left in their current location.<br />

Generally speaking, older documents that will not change need not be placed<br />

in a SharePoint document library if the only method needed to find those documents<br />

is the Search method. However, if users will need to browse the taxonomy<br />

hierarchy to find older documents, you’ll need to move the documents into a Share-<br />

Point document library or at least link to them using a links list.<br />

Content Indexes<br />

A content index is a flat text file that holds the data from crawled content in a content<br />

source. Updating a content index requires crawling the locations specified by the<br />

content sources <strong>and</strong> storing the results on the job server. Propagating a content index<br />

consists of copying the index from the index server to the search servers. A portal site<br />

search returns results from the content indexes stored on the search servers.<br />

Every portal site includes content indexes that allow users to search for documents<br />

inside or outside the portal site. After content is included in an index, the content<br />

appears in search results on that portal site.<br />

Source Groups<br />

Source groups, topics, <strong>and</strong> areas are the elements of search scopes. Search scopes<br />

allow you to define the breadth <strong>and</strong> depth of searches within portal sites <strong>and</strong> across<br />

portal sites. These assignable components can create very flexible searches.<br />

A source group is a list consisting of one or more content sources. Source<br />

groups are one of the elements used to define search scopes. Source groups are created<br />

<strong>and</strong> managed at the shared services level (if you are using shared services) <strong>and</strong><br />

can be assigned in any combination to a portal site search scope. These characteristics<br />

allow you to easily define search scopes across portal site boundaries. For example,<br />

if you want your marketing portal site users to be able to search content on the<br />

sales portal site, you can create a search scope consisting of a source group that<br />

encompasses all sales portal site data <strong>and</strong> a source group that encompasses all marketing<br />

portal site data.

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

Saved successfully!

Ooh no, something went wrong!