We cover Search driven architecture in SharePoint and Content Search Web Parts. We also discuss some differences between online and on premise.

1. Search Driven Architecture
in
SharePoint
Jim Lennox and Mark Passando
Contact:
Jim.Lennox@acm.org info@markpassando.com
https://www.linkedin.com/in/markpassando
jim@lennoxdev.com
https://www.linkedin.com/in/jim-lennox-15ab1442

2. Shoulders of Giants!
• Bella Engen
• Elio Struyf
• Benjamin Niaulin
• Marc Anderson
• Andrew Connell
• Bob German

3. The Search Problem…
Where are my keys?…

4. The Search Solution
Ah! Always the last place I look…

5. But at times…
It still feels like this…

6. We want our customers…
to just do this…

7. Definitions!
I have seen various definitions:
• Using Search as a data access technology
• Using Search as the interface and presentation
• Extending the current search center
• Adding dynamic URL’s that have search queries imbedded in them

8. Benefit of Search Driven Architecture
• Less risky, no code deployment .vs. configurations
• We troubleshoot results rather than code
• Much faster than development cycles and code
• More over, we separate the content architects and
developers from the SharePoint architects and
developers
• No need to give everyone access to the content site
collection

9. Online versus On Premise
• Product Catalog is distributed
• Can create Managed Properties in a limited way
• Only Text and Yes/No
• Not Refinable or Sortable
• Lists are not automatically re-indexed
• Crawls and indexing at the mercy of Microsoft’s schedule

10. Pattern Reference (MVC)
Model
View
Controller

11. Cross Site Publishing Detailed
Publishing Site
Collection
Javacript plugins
Control Template Item Template
Consuming
Site Collection

12. Cross Site Publishing
Four simple steps:
1. Create content in libraries and lists in a site collection where cross-site publishing is enabled.
Enable these libraries and lists as catalogs.
2. Crawl the content in your catalog-enabled libraries and lists. This will add the catalog content to
the search index.
3. Add one or more Search Web Parts to the site collections where you want to display your
catalog content.
4. When users view a page, the Search Web Parts issue queries to the search index. Query results
are returned from the search index, and shown in the Search Web Parts.

13. Site Collection Settings

14. Term Store

15. News List

16. Catalog Settings

17. Blog Comments List

18. Blog Comments Catalog Settings

20. Pub Demo Manage Catalog Connections

22. Content Search Web Parts

23. Content Search Web Part

24. Content Search Web Part

25. Build the Query

26. Final Query

27. Display Template Hierarchy
<!–#
AddPostRenderCallback(ctx, function()
{
//code to execute
});
_#–>
There is another way to achieve this by using:
ctx.OnPostRender = function() {
};

28. Managed Properties

29. Managed Properties (Search Schema)

30. Managed property Mapping Rules
'Link URL'{Link URL}:'Path'
• first token represents the label of the property displayed in the toolpart under
property mappings
• second token represents the display name of the variable reference to the actual
managed metadata property. This variable will be used in the display template to
access the value.
• last token is the actual name of the managed metadata that is used in display
template. This is not the display name of the column but the name of the
managed metadata property mapped to the crawled property in search schema.

31. Property Mapping in Web Part

32. Getting your Managed Properties

33. Referencing Managed Properties
_#= ctx.CurrentItem.<Current item property name> =#
Var currentItemIndex = ctx.CurrentItemIdx;
Var authorVal = $getItemValue(ctx, "Author");
ctx.ClientControl.get_nextUniqueId();
ctx.CurrentItem.ListItemID
ctx.CurrentItem.SPSiteUrl
Ctx.CurrentGroup.RowCount

34. A Few References…
• Bella Engen
• Elio Struyf
• Benjamin Niaulin
• Marc Anderson
• Useful Javascript Utilities