Chapter 13 – Customizing the Search Result and Search Center

MS Sharepoint 2010 Admin’s Companion eBook (P. 615)

Out of the box, Sharepoint 2010 suports anti-phrasing – the parts of a query that do not contribute to its meaning. Such as “How do I find”. Traditionallty this is done by using [noise words] or [stop words].

Contextual promotions – provide search results to the web user based on the user’s search action, location, or other relavant information.
(1) location awareness: user’s location: USA? Europe or other palces?
(2) device awareness: user on a mobile phone? Laptop? PC
(3) referrer awareness: how did user get to this site? Via a search engine like Bing? A social media site?
(4) Click pattern: Analyze from web log how user generally navigate the web site
(5) Time of day:
(6) Personalize content

The managed properties currently being used by search can be retrieved with the cmdlet Get-SPEnterpriseSearchMetaDataManagedProperty

Contextual feature only works for FAST Search.

Using Managed keywords —

Managed keywords are the basis for best bets, visual best bets and promitions.

When using enterprise keywords, a user who is updating content in Sharepoint can choose from either Enterprise Search terms or managed terms.

Difference between Enterprise keywords and managed terms? Enterprise terms allows multiple values.

To enable a document library to use Managed Keywords, go to:
Library’s Library Settings Page Enterprise Metadata and Keywords Settings

Later when you update a document’s property, you will be able to enter keywords for this document.

Site Actions Site Settings Search Keywords

Click on Add a Keyword, to add a keyword. Once you created a keywords, you can set up best bets and visual best bets.

Using Language Detection – Sharepoint 2010 automatically detects and understands 81 different languages.
Customizing the User Interface —
Sharepoint offers three search center site templates,
Enterprise Search Center – requires Publishing Infrastructure feature.
Basic Search Center – offer three basic search pages.
Fast Search Center – for FAST Only.

Creating New Search Pages —

Create an enterprise search center

To create a new Search Page – On the Search Center Site, Site Actions More Options Page Publishing Page

From what I can see, creating a Search Center actually creates on page – the page where you can do a search. There are no other pages that come with it.

On the next screen, enter title, description, URL and select a template:

To add a “Tab” to a search page, click Edit Page, and you will see this:

You can Add a new tab or edit existing tab. Once done, publish it, you can see the tab on a search page:

I believe “Tab” is a shortcut to a customized search result page – in which you can pre-deinfed the search parameters so when user clicks on it, they can see the desired results.

Customizing Search Pages —

The Web Parts on a Results Page communicate with a Shared Query manager identified in the Web parts as the Cross Web part Query ID.

Query Page – The welcome page of all Search Center site is a basic query page named default.aspx.

In Edit web Part, configure the textbox’s label, default text and custom search scope (contract)

Configure the scope drop down menu.

In Misc. sectio, these two checkbox overwrite the Scope Dropdown

Advanced Search Page —

Customizing the Results Presentation —
To Display results page in edit mode: In Search Center site,
Site Actions
View All Site Contents Pages Results.aspx, and change to Edit Mode, you wills ee a page with many web part zones:

On this page:
Refinement Panel – (“Faceted Search Results”, also called “Refiners”)
When user executes a search, the refinement only provide the relevant search categories for the first 50 items in the result list.

In the Refinement section, updtae this XML file to change the refinement options:

Search Core Results —

Both Sharepoint Search and Sharepoint FAST Search use federated search web parts to display search results – Provides a method for retrieving search results from any OpenSearch 1.1
compliant search engine including Sharepoint farms.

Core results —

Cross-Web Part Query ID options are user Query, Query 2 – 5. This ID is used by result Web Parts to identify the query manager that they share. Web Parts with User Query option selected share the query sent to the results page. Query 2-5 are for fixed query.

Sharepoint only index the first 16MB of a file, so if two file has the same content in the first 16MB, then they’re considered the same, even the file name is different. In this case, to remove duplicate, check this box:

Customizing Search Result Metadata —

To change or remove the managed properties retrieved by Core Result Web Part, us the following steps

Improving Search Quality – Page 656

Linguistics – use language structure and information so user can more easily find relevant data through search queries. Allows for grammatical forms and synonyms
to be added to the index.
Tokenization – word breaking.

Sharepoint 2010 supports 3 spelling searches —
(1) Simple spell check, which checks against language-specific dictionaries
(2) Phonetic spell check for phonetic similarities
(3) Advanced spell check against a custom list of words or phrases

Excluding Words from Spell Check — solution
(1) add the term or phrase to the dictionary
(2) exclude the term from the SharePoint spell checker. (Only FAST)

Lemmatization – process of mapping a word down to its base form or form variation, to improve the search.
e.g., keyboarding or keyboards
à keyboard

Lemmatization cab be added to the search feature by one of the following 3 methods:
(1) Index expansion – as content is indexed, the lemma value is stored in the index. Provide a quick search results, but neds large index and large disk space.
(2) Query expansion – the query is lemmatized. Takes longer, but need less space.
(3) Reduction – Stored the lemma value in index; query is alo lemmatized.

**** The preferred: lemmatization during the indexing process using index expansion or reduction.

Sharepoint use Index Expansion
– including nouns, verbs, adjectives.

Entity Extraction —

Several custom extractors
are provided out of the box to extract specific data such as person names, company names, locations, or paragraphs or sentences.

Entity extraction automatically extracts defined metadata to create useful information
based on unstructured data. Available in Sharepoint Search and FAST Search. (But only FAST supports management via Central Admin)

Creating Search Rules – P.661

Exclude content via varying levels within a Sharepoint library or list. Columns can be excluded; columns can be excluded based on user’s security.
Admin crawl rules that limit Sharepoint Crawlers from accessing specific links. You can use a wildcard
or regular expression. To configure rule, go to Manage Service Application.

Rank Profile —
supports two levels of rank profile customization:
(1) with user interface
(2) by using the search queries

Static rank – a number assigned to an item at indexing time.
Dynamic rank – how well the search query matches an index item.

Boost:
Anchor text boost – the weight an indexed item imposes over others
Queries boost: (click-through) the more clicks, the higher the rank (a 30-day window” is applied.)
Freshness boost: how recent is the document created?
Managed property boost: set boost levels for managed properties or groups of managed properties.
Proximity boost: how closely related to the search query is the document? (URL proximity)
Context boost: document text or terms match the search criteria?
Quality boost: depending on a managed property value such as user rating; also refer to user social tagging.

XRANK – (????)

dynamic filtering can occur during query execution using the XRANK operator, which is part of FAST Query Language (FQL)

XRANK: Assign higher ranking to a specific match.

01/19/2011, 10:48PM

Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: