spca2013 - dude, where’s my search scopes
TRANSCRIPT
Martin Hatch
Dude, Where’s my Search Scopes?SharePoint 2013 Search
@MartinHatch
http://martinhatch.com
This Slide Deck
http://sdrv.ms/1cAoaFy
• New Capabilities
• What’s new:• For IT Pros
• For Devs
• For Site Owners
• Result Sources
• Query Rules
• Result Types
• Display Templates
Agenda
• SharePoint 2013 “Server” now includes “FAST” search by default
• If you have Office Web Apps then you get document thumbnails in your search results
• Custom rules to impact on query ranking• Auto-population of document metadata (title / description)
• SharePoint Analytics is now part of Search• Views (Lifetime)• Views (Past 7 Days)
• Federated Search results (from other SharePoint farms) can now be embedded directly in core search results
New Capabilities from 50,000 feet
• Search in 2013 has a new topology which can ONLY be modified using PowerShell
• Index Partition
• Query Component
• Crawl Component
• Content Processing
• Analytics Processing
• Admin Component
• Search is much more intensive than it used to be! Expect to require a lot of tin!
• Continuous Crawls allow for vastly faster identification of new content
Changes for IT Pros
Potentially suitable for Web Servers for low-latency results(if you have decent hardware on your front-ends)
VERY resource intensiveWill definitely want (multiple) dedicated servers
• Incremental Crawl every 15 min .. takes 35 min to complete
Continuous or Incremental Crawls?
0 15 30 45
When the crawl starts it will effectively query a “snapshot” of the data, so only changes known NOW will be crawled
When the crawl finishes it will start again at xx:45 as per the “every 15 minutes” schedule
Content created at xx:01 is not indexed until xx:45 BEST CASE scenario! (it may take longer for the crawl to complete)
• Continuous Crawls every 15 min .. takes 35 min to complete
Continuous or Incremental Crawls?
Thread 1
0 15 30 45
Thread 3
This time, new crawl threads are spawned every 15 minutes .. REGARDLESS of how long each crawl takes to complete
In the scenario above we are doing 3 crawls simultaneously
Content created at xx:01 is indexed at xx:15Due to the crawls executing more frequently, it is likely that they will complete much quicker
Thread 2
Thread 1
• Search Settings can now be defined at the Site Collection and Site level .. Beware the site owner!
• Search dictionaries are now Managed Metadata Taxonomies
• List Owners can now reset the search index, which triggers on the next crawl
• Great if owners know their content well
• If you have large libraries this can cause a performance problem
Delegated Search Configuration
• Search Results and the Refinement Panel are now rendered using JavaScript Display Templates (and we can build our own)
• New Query Language Syntax for Search• URL Query String values
• Page field values
• User Profile Properties (based on the current user)
• Content Search Web Part also uses JavaScript Display Templates and provides search-based aggregations (as a replacement for the Content Query Web Part) *Enterprise SKU required
Changes for Devs
• Content Sources still work the same way
• Crawl schedules still work the same (although we now have the new “Continuous Crawl” model)
• Crawled Properties and Managed Properties still largely the same, now collectively called “Search Schema”
Some things don’t change
Result Sources .. the new “Scope”
• Levels: Service App | Site Collection | Site
• Replacement for Search Scopes, which are now deprecated
• Use Query Builder to define. Vastly more flexible than the old approach!
• You get a 16 of them out of the box including: Documents, Pages, Conversations, Wiki, Pictures ..
• Search Scopes are still “functional” but cannot be edited
More than just a search scope
• The new query syntax allows for considerable flexibility in the way Result Sources can be built
• There are some interesting “dynamic” result sources you get OOTB:
• Items related to the current user
• Items matching a tag
• Items matching a content type
• Items with the same keyword as this item
• Popular
• Recently Changed Items
• Levels: Service App | Site Collection | Site
• Allow you to change the output when a user has searched for something specific
• You can add a “Promoted Result” (URLs or Banner images)
• Add a “Result Block” (add in extra search results)
• Modify the rankings of the matching items
• These can be configured to only appear during a date range
Query Rules
DEMOResult Sources and Query Rules
..............................
• Levels: Site Collection | Site
• Identifies specific types of content in Search Results so it can be granted a custom look and feel
• Result Types can be selected based on:• The Result Source it is in
• The type of content (file / image / list item)
• Any other Search Managed Property (e.g. ContentTypeId)
• When creating your Result Type, select from the JavaScript Display Templates installed in the Master Page Gallery
Result Types
• These are HTML / JS files installed in the Master Page Gallery
• When you copy over your HTML file SharePoint will generate the JS file automatically (using an Item Event Receiver)
• You can optionally just deploy the JS file (if you don’t want the template to be edited, i.e. in SharePoint Designer)
Result Type Display Templates
DEMOResult Types and Display Templates
..............................
• Search Settings in each site allows you to configure the drop-down
• In the Search Center this also controls the tabs
• If you don’t specify anything then you get the default items:• Everything
• People
• Conversations
• This Site
Search tabs & drop-downs
• A lot of the same .. And a lot of changes
• Search looks and feels extremely familiar, but it really is very different
• New capabilities .. for everyone
• Much easier to customise .. and vastly more flexible
• New architecture .. learn to love PowerShell!
• New hardware requirements .. and new topologies
Wrap Up
European Office 365 Connect : January
Martin Hatch
@MartinHatch
http://martinhatch.com
Thank You
This Slide Deck
http://sdrv.ms/1cAoaFy