Migrating Content by Search from 2010 into 2013

IW411

Paul Hunt

Paul Hunt, MCITP, MCPD Trinity Expert Systems Ltd www.tesl.com paul.hunt@eurodatasystems.com Twitter:@cimares www.myfatblog.co.uk I do woodturning for a hobby!

Session Agenda

Cross-Site Collection roll-ups in SP2010 using Search Core Results

Migrating the solution from SP2010 to SP2013

Rebuilding from scratch in SP2013 using Search Results/Content by Search

LegalCorp.ComIntroducing our fictional client

LegalCorp.Com is a fictional example of a Global Multi National legal firm.

•Practices in 3 main global regions•Americas•EMEA•AsiaPac

•Each region represents key legal entities with their own reporting structures and requirements.

Global Challenges

The nature of the company meant that the client wanted to use a site collection for each region, with a global site at the top of the Navigation.

Global Challenges

This presented several challenges.

Consistent navigation.

Content Type syndication.

Client preference to avoid custom code.

Roll up of content from each of the regions.

What does the client want to achieve?To roll up news articles from each of the regions as well as from the Global site collection.

•The top four stories should be displayed in order of creation.•A region icon should be displayed to show where the story is from.•The story title should be displayed along with a summary of the article.

CQWP Limitations

CQWP is the usual tool of choice for the roll up of information.

Quick and easy to configure.

Fairly simple to customize with xslt.

Good for time critical information.

CQWP doesn’t work across site collections.

CQWP doesn’t provide paging ootb.

CQWP is limited to 1000 lists.

CQWP increases the demand on the web servers.

Enter our Hero!

Search

A Search alternative?

The search service application has been designed from the ground up to be scalable in enterprise situations.

Search results can be provided from multiple site collections.

Search results can be styled easily using xslt.

Complex search queries can be executed.

Our Kryptonite?

Result data is only as fresh as the crawls.

[Me] and [Today] tokens are not available. (SP2010)

Search needs more preparation.

In addition to Content Types and Site Columns Search needs:-

Search scopes Managed properties Regular crawls

Building our Solution in

SharePoint 2010

Building our Solution

Site Columns Content Type Page Layout Managed Properties Scope Search Core Results

Web Part XSLT

Site Columns

Region Sector Primary Sector Article Summary

Content Type

Name: Legal Corp News Article Page.

Inherits from Article Page (OOTB).

Adds our new site columns.

Content Type - Deployment

Manual Configuration

Content Type Hub Powershell Solution Package

New Page Layout(s) Copied from Article

Page Adds our new site

columns into the edit experience.

Managed Properties

Before you go any further. Create some content. Tag it properly Full Crawl.

Managed Properties

Crawled properties are extracted from the index.

Managed Properties

These can then be mapped to Managed properties and used in our web part.

Scope

Used to limit our results to just our web application.

Search Core Results Web part

Runs our fixed query and shows the results.

XSLT

Used to control the rendering output of our results.

XSLT

XSLT – Deployment Options

In the Search Core Results Web Part Properties

In a Site Collection style library

On the file system in /_layouts

In a federated location in the service app.

XSLT – Deployment Options

In the Search Core Results Web Part Properties

XSLT – Deployment Options

In a Site Collection Style Library Or on the file system

Use the XSL Link in the web part

properties tab to link to the file using a

relative path

XSLT – Deployment Options

In a federated location in the Search service application.

XSLT – Deployment Options

In a federated location in the Search service application.

XSLT – Deployment Options

In a federated location in the Search service application.

Search Core Results Web Part

Configure the managed properties to display in results.

Search Core Results Web Part

Configure Fixed Query

Building in 2010 – Key Points

Consider the impact to the search architecture and monitor the farm.

Remember to create, tag content and crawl it to make properties available.

Consider deployment options if migration to 2013 is likely.

PUTTING IT TOGETHER IN SHAREPOINT 2010

Demonstrating content roll-up using SharePoint 2010 search.

Migrating our Solution from

SharePoint 2010 to

SharePoint 2013

Migration Options

There is no supported in-place upgrade option.

Web applications are upgraded through the content database attach method.

The search service application can be upgraded through a similar method. Managed Properties Scopes Federated Locations

Migration Process

Build new SP2013 farm Restore Search Admin DB (optional) Create Search Service Application Create new Web Application Restore Content Databases Attach content database to web

application Fix issues!

Migration Process

Migration Process

Migration Process

Our site columns are already configured as part of the content database migration, but not the managed properties.

Migration Process

SharePoint 2013 now automatically adds Managed Properties for Site Columns discovered during crawls.

A suffix is added based on the field type.

Migration Process

To pick up the new properties, we first amend the columns in our Core Results web part

And then the XSLT in the style library.

Migration Process

Migration Process

Migration Process

With a SharePoint 2013 master page

Migration Process

With a custom Master Page & Css

Migration – Key Points

Upgraded Scopes & Federated XSLT can’t be edited post migration.

Managed property names will change unless re-mapped.

Weigh up the benefits of building it from scratch in 2013 for the improved search options.

Building our solution from

scratch in SharePoint 2013

Flexing the new muscles of SharePoint Search Automatic Managed

Properties Result Sources Display Templates New Search Web

Parts Search Results Content by Search

(Enterprise CAL only) Continuous Crawl

Building our solution

Site Columns and Content Types

Page Layouts Managed Properties Result Sources Display Templates Image Renditions …..

Building our solution

…Web Parts Server Standard Cals

Search Results WP– More configuration required.– Duplicate trimming requires

the .webpart file to be amended.

Server Enterprise Cals Content by Search WP

– Easier to configure– Duplicate trimming off by default– Pre-configured variants

Site Columns & Content Types

Site Columns Content Types &

Deployment Page Layouts

Nothings Changed!

Managed properties

Automatically mapped from Site Columns Requires content to

be tagged and crawled before it happens!

Result Sources

Combines 2010 federated search and scopes + extras

Defined at Service App, Site collection or Web level.

Uses the Query Builder to define the search.

Display Templates

Controls the rendering of a search result item

No more XSLT! Html and JavaScript

based Design manager

creates raw JS file from the Html

Display Templates

Each template includes a header block with key properties.

These map to the Design Manager properties

Display Templates – Tag Rules Understand the tag rules! JavaScript goes inside

<!--#_ _#-->

Display Templates – Tag Rules Calls to JavaScript variables

within Html go inside _#= =#_

Display Templates – .JS File Generated automatically every

time the .Html is saved.

Display Templates – .JS File Troubleshooting is easy with

the IE Developer toolbar!

Image Renditions Sizing images made simple

Requires Publishing Features Requires Blob Caching

Ensures appropriate files sizes

Image Renditions

Image Renditions Can be used in several ways

Picked from the SharePoint Image Dialog

Or specified in the URL– By ID - ?RenditionID=5– By Size using Height And/Or Width

Web Parts – Search Results

Server Standard Cals Uses the Query

builder or another webpart for results.

Web Parts – Search Results Select result source in query builder and refine as needed.

Web Parts – Search Results And then choose a display template to

control the output rendering.

Web Parts – Content By Search Server Enterprise Cals Also uses query builder or another web part for results

More options for styling with Control and Item templates

Heavily used in catalog sites

Web Parts – Query Priority Both Standard and Enterprise results web parts can be given a query priority for

times when search is busy.

Building in 2013 – Key Points

Familiarise yourself with all of the capabilities of 2013 search before deciding on which design route to take.

Think beyond the singular! Dust off those HTML and

JavaScript skills.

PUTTING IT TOGETHER IN SHAREPOINT 2013

Demonstrating content roll-up using SharePoint 2013 search.

Related Sessions IT102 – SharePoint Search

All Up – Neil Hodgkinson IT114 – Upgrading,

Deploying and Scaling out SharePoint search – Neil Hodgkinson

P&M306 – Using Javascript templates to customize the SharePoint UI – Chris O’Brien

P&M308 – Soup to nuts – How to build a metadata & search driven Intranet – Chris Johnson

IW507 & IW508 – Making the most of Content Aggregation in SharePoint Pts 1&2 – Christina Wheeler

DEV209 – Developers approach to search applications – Matthew McDermott

Questions?

Thank you for attending!

See you at the conference party tonight!