sharepoint 2013 search whats new


Enterprise Search - Crawl and Content ConfigurationAccording to Microsoft


About Moi

Fernando R MeloA+, MCSE, MCITPSr. SharePoint Architect at SharePoint Innovations

SharePointing since 2005

BLOG- Sharepointdojo.wordpress.com


About SharePoint Innovations

SharePoint innovations is a Microsoft Gold Partner, specializing in: SharePoint Training SharePoint Architecture SharePoint Custom Development

www.sharepointinnovations.comTwitter - @sharepointappLike us on Facebook!

http://www.sharepointinnovations.com/


Crawling the Content• The crawl role is responsible for crawling

content sources. It delivers crawled items – both the actual content as well as their associated metadata – to the content processing component• Invokes connectors or protocol handlers to

content sources to retrieve data• Does not do any document parsing (Content

Processing Component does that)• Information about content sources, schedules,

etc. are synchronized to the registry on crawl role servers from the search admin database

• The Crawl Database is used by the crawl component to store information about crawled items and to track crawl history• Holds information such as the last crawl time, the

last crawl ID and the type of update during the last craw.


Crawl and Content Configuration

Connectors Crawling and Content Sources Result Sources Improvements in Document Parsing Entity Extraction Schema Management


Connectors The following connectors will be available out of the box in

SharePoint: SharePoint HTTP File Share BDC – also includes these other connectors that are built on BDC

framework: Exchange Public Folders Lotus Notes Documentum Connector Taxonomy Connector

Requires the Term Store to be provisioned for crawling, so requires SharePoint Server

Requires Secure Store only if you want to create an end-to-end BDC experience, including per-user authentication, so requires SharePoint Server

People Profile Connector Requires the profile store to be deployed and populated, so requires

SharePoint Server


Reach out and search someone


Crawling and Content Sources

There are improvements to the crawling feature itself: For HTTP sites, crawler supports a new type of

authentication - anonymous Crawling also supports certain out of the box

web part content that is rendered asynchronously on the client

The crawler gets a “classic” type rendering of pages with the new asynchronous web parts on them in order to index them

NEW!


Ninja’s are crawling my site.


Crawling “Continuously” “Continuous crawling” is a new feature to crawling in

SharePoint 2013 – it only applies to SharePoint sources When you crawl continuously every 15 minutes (by

default) the crawler gets changes from SharePoint sites and pushes them to the content processing component You can change the interval using Set-

SPEnterpriseSearchCrawlContentSource Because of changes in how the index is created and

stored, a document can appear in the index within seconds of going through the content processing component – you no longer have to wait for long index merges until it shows in results

It also means you can get latest changes even while a full crawl is starting, so you can see results before full crawl completes

NOVO


Crawl baby Crawl


Result Sources – FKA Scopes and Federated Search Scopes and Federated Search in SharePoint 2010 are now known

as “Result Sources” in SharePoint 2013 Results Sources also support a “Remote SharePoint Index”

This is for scenarios where you have multiple SharePoint farms but don’t want to create a central farm that crawls them all

It also simplifies the problem of passing credentials for the current user around (i.e. Kerberos, etc.). It does this with: An OAuth trust between search applications Passing the current user’s claims to the remote farm when making the search

request It requires a trust between the farms, the same as you establish

when consuming service applications between farms

Noveau


Improvements in Result Sources Some of the key functional improvements in Result

Sources over Federated Search include: Site and site collection admins can manage and

configure result sources for their site collection It will reduce requests for SSA admins to centrally create and

manage federated sources Empowers lower-level admins to create and manage federated

sources to meet their specific requirements. Exchange is now a data source for a result source You can apply query transformations to a result source

For example, adding criteria to it that will be appended to each query, e.g. author=“Our CEO”, etc.

atarashi


Content Sources and Result Sources

demo


Improvements in Document Parsing

SharePoint 2013 introduces new parsing features Automatic file format detection: no longer relies on

file extension Deep link extraction for Word and PowerPoint

formats Visual metadata extraction: titles, authors and dates High-performance format handlers for HTML, DOCX,

PPTX, TXT, Image, XML and PDF formats New Montage, Visio and OneNote filters The IFilter API continues to be supported as a

means of extending the supported set of file formats

neu


Entity Extraction for Companies Custom refiners were introduced into SharePoint with

FAST Search 2010. The term lists used in custom refiners were maintained on the file system via XML files and admin database

In SharePoint 2013 the experience is simplified by moving much of this management into the term store

You can manage entity extraction like any other term set (with a few exceptions); however you cannot add additional term sets for extraction:

New 2


Schema Management In SharePoint 2013 we’re able to give site collection

admins much more flexibility to work with managed properties

The farm search admin can define managed properties when the schema needs to be extended

Site collection admins have similar but limited power though, because they make some changes of the schema model per site collection Site collection admins can pick up new crawled properties for

custom metadata in their sites and create managed properties from them

Creating new crawled and managed properties still requires a full crawl

If the site collection administrator decides not to do schema management that site collection uses the one from central admin

neya


Search for the little people too…


Demo Creating Managed Property Its not for apartments anymore


Search Query Configuration Ranking Query Spell Correction Query Rules


Ranking Ranking model describes which criteria are included in

sorting, how much they contribute to the rank score and how they relate to one another

Custom ranking models are managed through PowerShell and the public OM using XML files as it was in SharePoint 2010

Ranking model for a specific query can be selected at query time by setting the RankingModelId of the query; otherwise default is used NOTE: This property is currently not available in the OOB search

results web part


Working with Ranking Models A search service administrator can do the following basic

operations on the rank models: List ranking models Specify a default ranking model Change an existing custom ranking model Delete an existing custom ranking model Create a new ranking model (either based on an existing one or

from scratch) Import and export a ranking model to XML Specify how much weight the various properties should have in

the model These operations are all administered through

PowerShell There may be a CodePlex GUI-based solution after RTM


Query Spelling Correction Customizations to Query Spelling Correction is now

managed in the term store – both inclusions and exclusions

We also still have a dynamic dictionary that is created based on content in the index, or you can switch to the static OOB dictionary

Here’s an example:

Provides customizable “did you mean” functionality:


Query Rules Query Rules are a new feature in SharePoint 2013 that

help act upon the “intent” of a query Query Rules are composed of three top level elements:

Query Conditions (i.e. matching rules) Query Actions (i.e. what do you do when you find a match) Publishing Options (i.e. when should this rule be active)

Rules are created at the site collection level, but you will probably also be able to create them at the SSA level through PowerShell (TBD by RTM)

Several Query Rules are provided out of the box and can be found in the Site Settings for each site collection

Interestingly new


Query Rules Implementation Query Rules allow you to have search requests from a

user trigger multiple queries and multiple result sets. This differs from SharePoint 2010 where there were only simple

queries – one query has one set of results. All matching Query Rules can generate results; the query

orchestration engine retrieves all the different sets of search results and organizes them for rendering to the user

The results themselves are then rendered using a new feature called Query Results display templates, which is discussed later


Query Rules - Conditions Conditions allow you to define the circumstances under which your

query rule will apply You can choose to match on these use cases:

Query contains a specific word or words Query contains a word in a specific dictionary Query contains an action word that matches a specific phrase or term set Query is common in a different source (like Videos Result Source) Results include a common result type (like file type) Advanced rule – match across a set of terms, dictionary, regular expression,

etc. You can also match if a query is against a specific Result Source or

category (like a Topic Page category) Each Query Rule can have multiple conditions


Query Rule Actions There are three types of actions:

Assign a “promoted result” to the query Promoted result is similar to Best Bets with SharePoint 2010 or Visual Best

Bets with FAST Search 2010, but much more flexible Create and display a Result Block

Result blocks specify an additional query to run and how to display results The feature includes a full query designer so you can build and test queries

before finalizing them You can include the results above those returned by core results, or

interleaved by ranking You can also choose custom display templates instead of the default for

the result Change the query that returns the core results

Change the original query by changing the query terms, adding additional terms, apply an XRANK formula to the query, etc.

You can add multiple best bets or results blocks for each query rule


Query Rules Publishing Options Publishing options for a Query Rule determine when it

will be used It works just like rules for publishing a page in a

publishing site template You decide whether the rule is active You decide when to start and when to finish using the rule, or

don’t set dates at all and it’s always used You can configure a review date, which is basically an email

reminder for you to look at the rule again Publishing a rule is particularly useful in commerce

scenarios. For example, queries that should return items you want to percolate to the top and sell during a particular period of time


Query Rules

demo


Would you like to ask a question?

Remember, beta is not just a fish.


© 2011-2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows 7 and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted

to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

sharepoint 2013 search whats new

Technology

demo2012 microsoft

2012 microsoft

published

content based

rights reserved