Overview of Search in SharePoint Server 2013 - Australian SharePoint Conference - April 11 2013, Sydney

10,196 views

Published on

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

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
10,196
On SlideShare
0
From Embeds
0
Number of Embeds
6,298
Actions
Shares
0
Downloads
122
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • First world problems
  • {searchTerms} site:http://portal.sezai.com/sites/projects/*
  • Fix up this demo to one with:SearchtermactionProject POContenttype:”purchase order”
  • Overview of Search in SharePoint Server 2013 - Australian SharePoint Conference - April 11 2013, Sydney

    1. 1. SezaiKomur NEC
    2. 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. 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. 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!
    5. 5. 1. Connect to and crawl content2. Process the content3. Store the content in an index4. Execute search queries againstthe index5. Retrieve Results6. Display the results to the user
    6. 6. Crawled Properties  Individual data properties detected during crawlsManaged Properties  Another „layer‟ of properties that map to crawled properties  Used in search queries
    7. 7. SharePoint 2013 Search Centre
    8. 8.  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
    9. 9.  Each Search Result Item is rendered differently Each Item Uses a different Display Template No more XSLT, use HTML and JavaScript
    10. 10. Result Sources and Result Types
    11. 11.  Replaces 2010 Search Keywords and Best Bets Used to understand user intent and deliver a targeted user experience Query Conditions  Query Actions Query Publishing
    12. 12. Query RulesResult Blocks
    13. 13.  SharePoint‟s Site Collection Boundary Problem Uses Search as a data source to display content
    14. 14. Content Search Web Part Display Templates
    15. 15.  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
    16. 16.  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
    17. 17.  Analytics based recommendations engine Similar to – Amazon “people who purchased this also purchased” LinkedIn “people who viewed this profile also viewed”
    18. 18.  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
    19. 19.  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
    20. 20.  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
    21. 21.  Result Sources, Result Types, Query Rules & Search Schema can be managed at many levels  Search Service Application  Site Collection  Site
    22. 22.  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
    23. 23. Thank you to our sponsors

    ×