My slide deck from my presentation "Overview of Search in SharePoint Server 2013" the 2013 Australian SharePoint Conference - April 11 2013, Sydney

1. Sezai
Komur
NEC

2.  SharePoint Server MVP
 SharePoint Solutions Architect – NEC Australia
 Perth SharePoint User Group
 Email
 sharepointsezai@gmail.com
 sezai.komur@nec.com.au
 Twitter
 @sezai
 LinkedIn
 http://www.linkedin.com/in/sezaikomur

3.  History of SharePoint Search
 Architecture of Search in SharePoint 2013
 Search Centre
 Result Sources
 Result Types
 Display Templates
 Query Rules
 Content Enrichment
 Recommendations
 Recap

4.  There has been Search in SharePoint since
SharePoint 2001 and all versions since.
 FAST Search and Transfer Acquisition in
2008.
 Two Search Product Options for SharePoint
2010
 SharePoint Server 2010 Search
 FAST Search Server 2010 for SharePoint
 OneSearch Product Option for SharePoint
2013!

10. 1. Connect to and crawl content
2. Process the content
3. Store the content in an index
4. Execute search queries against
the index
5. Retrieve Results
6. Display the results to the user

11. Crawled Properties
 Individual
data properties
detected during crawls
Managed Properties
 Another „layer‟ of properties that
map to crawled properties
 Used in search queries

12. SharePoint 2013 Search Centre

21.  Replacement for 2010 Scopes + Federated
Locations
 Apply a query transform to return a corpus
subset
 Can be created in Service Application, Site
Collection and Site levels
 Used when defining a new Search „Vertical‟
 Create a new Search Results page and
applying the Result Source to it to create a
search experience

22.  Each Search Result Item is rendered
differently
 Each Item Uses a different Display
Template
 No more XSLT, use HTML and JavaScript

23. Result Sources and Result Types

31.  Replaces 2010 Search Keywords and Best
Bets
 Used to understand user intent and
deliver a targeted user experience
 Query Conditions  Query Actions
 Query Publishing

34. Query Rules
Result Blocks

41.  SharePoint‟s Site Collection Boundary
Problem
 Uses Search as a data source to display
content

42. Content Search Web Part
Display Templates

48.  Used for Entity Extraction
 Replacement to the FAST Search Document
Processing Pipeline / Processing Pipeline
Extensibility
 For each item that is crawled:
 - The file / properties can be passed to a
web service.
 - The web service contains custom code
which can create new managed properties
that are stored in the index.
 Powerful for extensibility

49.  Youcan run code against crawled data and
pass data to other systems to:
 - CRM/ERP and other Line-of-business
systems
 - Geocoding
 - OCR
 - Audio and Video Transcription
 - „Deep‟ Search of raw data

50.  Analytics based recommendations engine
 Similar to –
 Amazon “people who purchased this also
purchased”
 LinkedIn “people who viewed this profile
also viewed”

52.  One NEW Search Engine based on FAST
& SharePoint Search
 Search requires more servers
 Search Centre is overhauled and improved
 Significant UI enhancements – previews
 Query Builder in many places

53.  Result Sources – Replaces scopes &
federated locations
 Result Types – Configure different Display
Templates for individual results
 Display Templates – Define how an item
is rendered with HTML and JS

54.  Query Rules – Replaces keywords and best
bets
 Intent based search experience.
 When conditions of a query rule trigger are
met:
 - Add promoted results
 - Add result blocks
 - Change Result Rank

55.  Result
Sources, Result Types, Query
Rules & Search Schema can be managed
at many levels
 Search Service Application
 Site Collection
 Site

56.  Content Search Web Part – Cross Site
Collection Aggregation!!!
 Content Enrichment – Can be used for
property extraction - powerful extensibility
 Recommendations – Recommends based
on analysis of user behaviour

59. Thank you to our sponsors