Your SlideShare is downloading. ×
SP24 online conference April 17, 2014 > Real-live experience using cross-site content publishing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

SP24 online conference April 17, 2014 > Real-live experience using cross-site content publishing

272
views

Published on

Though at first it seems the easiest sites to build, challenges and questions appear: what if I want to build an Knowledge base, or a policies and procedures site, or global news/events or , integrate …

Though at first it seems the easiest sites to build, challenges and questions appear: what if I want to build an Knowledge base, or a policies and procedures site, or global news/events or , integrate or link TermSets in managed navigation, what about friendly-urls, how to define contextual filters, adaptive interfaces & user segmentation, inherited content types, configure content sources or display templates, what about multi-language, and more? To get answers to this and many more questions - join for the session exposing a real-life project built around these new features.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
272
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Relevancyis a personal concept - «whatis relevant to one, is not to another».“Findability” has become a very trendy term, sort-of the holy grail.But is it really findability relevant today? What are really people expecting an intranet/extranet or public-facing web sites? Most intranets have a hard-time in providing a logical path to browse throughorganically grown information and looking for an effective way of exposing deeply nested content that is not otherwise visible from the typical top-down navigational mechanisms. Today we are talking about people using a variety of devices, with different shapes and capabilities accessing
  • SharePoint 2013 has a range of search capabilities that allow for customization and personalization of results and new ways to leverage content models and metadata. By combining various content model, metadata and taxonomic structures to these mechanisms, the possibilities are virtually unlimited.Search results can be furtherrefined, re-ranked and presented through a tremendous variety of mechanisms and approaches.The foundation is still, drum roll please, good taxonomy, metadata and information architecture.  Search results are relevant when they meet the user’s needs.  We can meet those needs when we understand the user, task, context and needed content. One cannot overemphasize these messages
  • Situation – in the context of this project our mission was to provide some kind of mechanism to enable rollup of content available across multiple site collections – in most cases, each handling own security, structure and content publishing processes. Immediately we thought about Search – which proven not to be a bad choice, but by itself it was not enough, mainly because structure already in place was not ready to support content aggregation scenarios.Content Types ( and/or Site Columns) used were not consistent across the board – which also meant that search results, refiners we’re mostly unpredictable leading to more confusion than clarity. In order to tackle this we had to map and transform the content into Commonly agreed “structures” by using Solution packages to deploy same content types across the board.Unified Taxonomy – helped us reused information to the maximum for classification of content. At the same time, we’ve been able to identify most appropriate Navigation Term-Sets, define Refiners appropriate to each type of Catalog Item
  • The Knowledge Center is the information sharing hub which collects and exposes data from multiple data sources. A special “attribute” enables further segregation of content into multiple sub-sites (Code Productivity, Collaboration Solutions, Project Management, etc.). We’ve got a custom master page adapted to the purpose of the site (fancy page-stack effect). Page layout has been adapted for Category pages to show: - In the center a rollup of multiple types of content types (News, Tips, Articles) using a tabbed user interface – customized version of the CSWP - Custom refiners using adapted Display Templates
  • Cross-Site Publishing is very simple publishing is a feature driven method that lets you create and maintain content in one or more authoring site collections or web application and publish or display this content in one or more publishing site collections by using content Search Web Parts.Cross-site publishing uses search technology to retrieve content.On a site collection where the Cross-Site Collection Publishing feature is enabled, libraries and lists have to be enabled as catalogs before the content can be reused in other site collections.The content of the library or list catalogs must be crawled and added to the search index.The content can then be displayed in a publishing site collection by using one or more Search Web Parts.When we are changing the content in an authoring site collection, those changes are displayed on all site collections that reuse this content, as we are using continuous crawl.
  • Content Source - Columns used for Querying or Refiners must either be Site Columns or part of Content typesConfigure Search & Faceted navigationSometimes having a Content Source specially for Catalogs might be a good idea to enable fresh content (e.g. changing Refiners require full crawl). With the new “Re-index List” settingsPromote crawled properties, configuremanaged properties to be returned in search results, querying across,sortable, filterable, or used in recommendations?Category pages and catalog item pages are page layouts that you can use to show structured catalog content consistently across a site. By default, SharePoint Server 2013 can automatically create one category page layout and one catalog item page layout per catalog connection. Pages based on these layouts are created in the Pages library of a publishing site when you connect the site to a catalog.
  • The most important step into tailoring and adapting the XSP in your project is to understand what goes behind the
  • you are not able to configure security trimmed links via managed metadata navigation. Everybody with access to the selected web will see all configured navigation linksWe used a term store to tag all the documents with the right category. To allow a real fast upload and publish process we mixed the metadata with a folder structure and worked with the default column values for the different folders. This enables the publisher to open that special library with the explorer view and allows a very fast upload with integrated tagging.
  • All automatically created managed properties use the Text data type. To make sure that that the refiners are displayed in the correct format, you should only enable an automatically created managed property as a refiner if it is based on a site column that uses the data type Text, Managed Metadata, or Person or Group. For other data types, you must create a managed property, add the type code to the property name, and enable the managed property as a refiner.
  • Category pages and catalog item pages are page layouts that you can use to show structured catalog content consistently across a site. Unless you have already deployed any of your own, by default, SharePoint will automatically create one category page layout and one catalog item page layout per catalog connection. Pages based on these layouts are created in the Pages library of a publishing site when you connect the site to a catalog.
  • Term-drivenmeansthatpractically content isaddedinto the page via the CSWP with the obviousaddedadvantage of not having to create multiple pages, but rather content isdynamicallyretrievedfrom the search index – which translates intohavingonly 2 pages (by default).Enabled via the «Term-Driven pages» tab in the Term store management tool – whichalsoConsistent look and feelacross multiple categories and product typesManaged navigation abstracting the navigation whilecreatingfriendly-URLS
  • By setting this reference, when visitors browse to a Category page on the publishing site, the actual content in the source page ContosoCategoryPage.aspx will be used to display information – which at its turn is actually using targeted CSWP plus the. It is important to understand that visitors will not see the page name ContosoCategoryPage.aspx, but instead a friendly URL. 
  • Connecting the actualpublishing site to a catalog, and configuring which terms should be used from the “Product Hierarchy” term set creates automatically a new CONTENT SOURCE which is restricted to the content of that particular Catalog. Because we have used the same term set to tag the items in our catalog and to build our site navigation, we can use a term from our site navigation to search for catalog items that have been tagged with that same term.Therefore the query in the CSWP will only display search results for items that are in the catalog - Products Results result source, and that have been tagged with either the TERM currently under selection – or its children (in the picture - "Audio", or any of the children of "Audio", for example "MP3 players" or "Speakers“)The 2nd most important aspect is “TERM UNDER SELECTION” – what practically means is that
  • Any organizations needs to understand their return on investments made on a particular platform require some sort of analytics in order to gain deeper insight into how users are using the system. Often IT managers are promoting SharePoint as a big success in their organizations, however approaching business users very often reality is different. Understanding how SharePoint is being used, would lead to adapting content strategies, provide more relevant content and improve adoption. SharePoint 2013 includes significant improvements with regards to analytics processing engine. Let’s see which are these features are these that would help understand and shape user’s experience on our site.
  • Usage Analytics > Recommendations - help generating report of type “People who viewed this also viewed this” – data is stored in the Search index for further processing in reports.The importance of the usage analytics is crucial in
  • Visitors do something on your website, for example, they view an item. This generates a usage event.The usage event is recorded in the Event store.The usage events are sent to the Analytics Processing Component where they are analyzed. The result is sent to the Search index.When visitors navigate to a page that contains a Recommendations or Popular Items Web Part, a query is automatically issued and sent to the search index.The query results are returned from the search index and displayed in the Recommendations and Popular Items Web Part on your website.
  • Transcript

    • 1. Real-life experience building search- driven applications for product-centric sites Marius Constantinescu Switzerland, GMT+1 April 16th /17th, 2014
    • 2. Managing Consultant blue-infinity SA Geneva Switzerland Contact @c_marius c_marius@msn.com http://nettitude.wordpress.com
    • 3. 1.Introducing organizational scenario 2.Understanding Cross-site content publishing 3.Does it really work ? > our experience, trade- offs, solutions 4.Search-driven applications
    • 4.  Source > Collaboration Workspaces  Multiple collaboration site collections  Each to its own content publishing processes & security management  Target > Published Intranet  Flexible content publishing with respect to security rules already in place  Support content aggregation across multiple sources  Multilingual support  Relevant content targeting  Usage tracking  Performance considerations
    • 5. I. Planning  Identified authoring sites, interviewed owners, identify current content publishing processes  Mapped-out existing content across various site collections, including security  Identified fields meant for sharing, filtering, sorting or querying across II. Preparations 1) At source  Deployed new structures (sub-sites, lists, etc.) to better serve our content rollup needs > new IA promoting consolidated content types, site columns, taxonomy  Enable lists as Catalogs  Use PowerShell (and migration tools) to migrate existing content into new structures  Re-classify content where needed  Establish common Assets location, update links 2) At Destination  Prepare target publishing sites topology 3) At Farm level  Configure dedicated Content Source & Crawling schedule in Search SA for the cross-site publishing (enlist Catalogs into Content Source)  Run a Full-Crawl
    • 6. Independent Authoring and Publishing  Promotes Content reusability  Clear separation of responsibilities  Support for Multilingual content publishing scenarios Build next-gen user interfaces  Advanced query building capabilities empowering Information Workers  Freedom of choice in applying different layouts to category/items pages  Display templates (for refiners, search results, etc.) for unprecedented UI flexibility Power of search  Analytics and recommendations  Scaling and performance  Across site collection boundaries  Automatically updated UX
    • 7. Generally available • Query rules, display templates, rank models, managed navigation, search schema, analytics & recomandations, entity extraction, CSOM, KQL, query builder, result sources Available in Office 365 • Content Search web part (CSWP), Content Iterm Reuse Web Part (CIRWP) • Cross site publishing (XSP) & Category/Item page layouts On-premises only • Product catalog site collection template • User segmentation and adaptative interfaces • Taxonomy Refinement Panel Web Part • Faceted navigation – supports taxonomy refiners • No Suport for Anonymous access for XSP (e.g. Public web-sites)
    • 8. Separate presentation from storage • Different teams working on content & design • Choice of design on authoring vs. published sites Flexible and dynamic • Can be used virtually for any type of list (not only Pages) • Multiple authoring sites > multiple publishing sites Breaking down site collection boundaries • Write once > reuse multiple times • Easily publish content across site collections – not using Content Deployment Eliminate large list thresholds • Take advantage of search high performance • Ability to distribute content across many lists/libraries, with adequate security Allows flexible & dynamic publishing • Whenever you want, wherever you want
    • 9. Content Catalogs Faceted navigation, Refiners • Managed Navigation • Managed properties Content Search, Catalog Item Reuse Web parts Query Builder Query Rules Display Templates
    • 10. Index SharePoint Content Search Publishing External
    • 11. Content Source •Authoring Site Collection(-s) •List(-s) to share as Catalogs •Configure anonymous access •Primary key fields (used in building the final unique URL to the “product”) •A Managed metadata column used in the Category- based navigation Search & Faceted Navigation •Share navigational Term-Sets •Prepare for Faceted navigation > used for Category browsing (generic or specific) •Define Refiners (term-specific or same for all) Content Destination •Target Publishing Site Collection (-s) •Connect to Catalogs •Select “product” ID & [Group] •Establish URL building User Interface •Select/Customize Master Pages, Category & Item pages •Customize Search Display templates •Search/Catalogs web parts (Relevant or Recommended results) •User Segmentation  Not using “Product Catalog” site template forAuthoring site requires activation of the “Cross-Site Content Publishing” site collection feature + creation of appropriate site columns used later as managed properties, category navigation, “product” unique Id, etc.  The “Product Catalog” site template does not exist in Office 365
    • 12. Deploy content types at site collection level [recommended] Deploy site columns vs. list columns [If any] Create custom lists, attach content types Populate (& publish) all fields needed as Managed Properties Enable lists as Catalogs Run Full-Crawl Deploy Activate Cross-Site Collection Publishing “Publishing” site NOT required (but recommended when variations will be used) Prepare Identify Authoring site(-s), consider multilingual, content security strategies Identify data to publish across > content types hierarchies & shared site columns Consider faceted navigation hierarchy & refiners Consider the one column to hold the Unique Item Id Plan A. Either start by using the “Product Catalog” site collection  It run as a Publishing site, and activated “Cross-site Collection Publishing” site collection feature – enables the “Use as Catalog”,  Added the Product Catalog list with Content types (Product & Product with Image)  Site Columns (Item Number, Group Number, Language Tag, Item Category & Rollup Image) B. Any other site template (including existing sites) would require redoing the steps & structures manually [Office 365] - The “Product Catalog” template does not exist (choose option “B”)
    • 13. Multiple Content Types scenario: • Define base Content type - not needed to inherit from default ”Product with Image” (do consider adding a sort of unique “product Id” – for friendly-URL building) • Consider specificities of each product & plan adequate columns for each “product-specific refiner” • Faceted navigation – one or multiple managed metadata columns can be used to build navigational hierarchies. • [Recommendation] Do not think a too deeper hierarchy (< 3) – allow for additional refiners in specific cases. Televisions Laptops Cameras Title Title Title Brand Brand Brand Description Description Description Price Price Price Item Number Item Number Item Number Technology (LED; LCD, Plasma) CPU Type(DSLR, Bridge, etc.) Max- Resolution(720P, 1080i, 1080P) Screen Size Optical Zoom Screen-Size (40,42, 50, 60) Hard Drive Lens Type Tip – columns added by default “Product with Image” content type are automatically added as Managed Properties – for your custom ones you need to consider doing it manually.
    • 14. News Announcements Classifieds Events Title Title Title Title Start Date Start Date Start Date Start Date Description Description Description Description Category (Science, Technology, Sports, ) Category Category (Automotive, Real- Estate, Carrier, Pets, ) Category Expiry Date Expiry Date End Date Scope(Local, Regional, Global) Scope Scope Scope Accessibility (Private, Public, Team, Project, Department, ) Accessibility Accessibility Accessibility Type Hire, Retirement, Policy Type Real-Estate > Buy, Sell, Rent, Professional Services Type (Meeting, Holidays, ) Define the shape of the data to be used • Map the data, identify Entity specific attributes • Define Content types - a ”Product with Image” provided with default “Product Catalog” list • Reuse shared site columns • At least one column must be Managed Metadata (Item Category - by default already mapped to “Product Hierarchy”) – used to define managed Navigation • When creating columns use SingleWordsWithNoSpaces ( or special Characters – this will become Internal name (fixed) > rename will only update Display Name • By default Approval is ON – either approve items or disable it prior to Full Crawl – items is ignored otherwise. Tips • Site Columns get promoted as managed properties in search (but only as Text columns) • Create your own base CT to have others inherit from - idea of sharing same common base • Content Type Hub (not available in Office 365) or Solution-based deployment could be an option
    • 15. Documents Catalogs Pages Digital Assets SharePoint Content www Ext. CMS LOB + more External Content User Behavior (+custom events) Content & Authoring FAST Search Publishing User Experience REST/OData Page Framework Display Templates Variations Query
    • 16. 3 1 2
    • 17.  Multiple Content types?  Which columns should be searchable, used in filters?  What information will be used in the Navigation hierarchy > terms should be pinned or not?  Shared (Reusable) Columns  Preferable to use Site columns vs. List columns  Could be different per “product” (catalog item) must be configured Product Code Title Television Display Type (LCD, LED, Plasma) HD-Ready (720P, 1080P, UHD) Description Price Computer CPU Screen Size (13, 14, 15, 17) Camera Type (DSLR, Point'n'Shoot) Resolution (in MegaPixels) All from Product + Screen Size (40, 55, 60, 77) Hard drive RAM Optical Zoom (24x) Digital Zoom (12x) Lens Type Storage Format (SDHC, SD) Code Title Description Price Title Description Price Title Description Price Code Code
    • 18. Refiners are filters narrowing search results They come in different types and shapes – tightly related to underlying data type  [New] Range-based (sliders) and multi-valued refiners are available Only managed properties can be configured  [New] Via the use of «Yes latent» Farm Administrators can delegate to a Site Collection administrator the possibility to decide. [New] Refinement web parts can now be configured individually in-page (horizontal or vertical) Refiners – why use them?
    • 19. Televisions [Catalog] Cameras [Catalog] Computers [Catalog] Content Search Web Part Managed Properties Content Search Web Part Content Search Web Part Title ows_q_TEXT_ProductCatalogItemNumber ows_q_TEXT_ProductCatalogGroupNumber ows_taxId_ProductCatalogItemCategory ows_r_IMGE_PublishingRollupImage ows_q_CHCS_DeviceScreenSize Site Column Title Brand DeviceScreenSize Site Column Type Single line of text Managed Metadata Choice 1 Crawled Properties 2 3 Title ProductCatalogItemNumberOWSTEXT ProductCatalogGroupNumberOWSTEXT owstaxIdProductCatalogItemCategory PublishingImage DeviceScreenSizeOWSCHCS 4 Refiners Refiners Tips • The Catalog Item Reuse WP auto detects rendering mechanism based on the naming of managed properties
    • 20. (*) Require either Farm Administrator or Search SA administration delegation – unless provided groups are used Read more @ http://nettitude.wordpress.com/2013/10/17/introducing-indexed-property-bag-in-sharepoint-2013-a-searchable- collection-of-properties/
    • 21. • The actual Catalog(contentclass:sts_listitem OR IsDocument:True) SPSiteUrl:http://contoso/sites/catalog ListId:3a3f66cd-9741-4f15-b53a-b4b23c3187ea • The Category column owstaxidProductCatalogItemCategory • The term under selection (its GUID) #c771504f-6a2f-423f-98de-0e12fcfa08c9 (:) is the actual separator specifying the “contains”
    • 22. Content Item Reuse default Web part is automatically provisioned with the default “Product Item”
    • 23. Why the need for new concepts? Editing XSLT is a cumbersome - even for the veterans Modern Web requires Standardization – empower Power-Users Client-side "templating" techniques are current trends (e.g. Knockout, Kendo UI, Razor) What are design templates? Re-usable Styles Files for your Content based & Search Results Web-Parts Where does one use "Design templates"? Search Results & Web parts, Catalog reuse web parts What does one need to create a new template ? Access to Master Page library Your favorite web development tool (even Notepad) to create them To eliminate the for designers and power users to work with XSLT (and the use of ddwrt JavaScript functions) each time they a new look & feel is needed, SharePoint 2013 introduces Design Templates. Each display template consists of two files (in Master Page library under Display templates):  An HTML file (.html) - the actual template  JavaScript File (.js) - the script that makes the magic happen – automatically generated  jQuery supported, or custom JavaScript and CSS  Custom managed properties can be displayed (from search results)
    • 24. Control Display Template Which Cont rol Display Template
    • 25. Search Analytics • Analyze content being added into the index (such as links, anchor text) and together with clicks on search results gets added into the Links database, leading further to improved relevance & reporting. Usage Analytics • User’s actions (such as Clicking on links, viewing search results) generate usage events (standard or custom) which can further contribute to recommendations, popularity reports, most viewed links, etc. SearchAnalytics • Search Clicks boost/demote ranking of items in the search index based on user clicks • Deep Links improve relevance of sub-pages in a site based on what user clicks in results UsageAnalytics • Usage Counts how many times items (in lists/library & search results) are Viewed, Clicked • Recommendations identify patterns in usage, relying on Usage Counts to build relationships graphs • Activity ranking analyses trends & adapts ranking of items in search results based on the Usage Events
    • 26. 1) Views – a usage event is registered when a visitor views an item on your site (event type ID 1) 2) Recommendation 1) Displayed (ID 2) – a usage event is registered when an item is displayed as a recommendation on your site. 2) Clicked (ID 3) – a usage event is registered when a visitor clicks an item that is displayed as a recommendation on your site. • Map a single crawled property to UsageAnalyticsID managed property to support recommendations • Property must be part of the URL for the Usage Event to be recorded properly • At least 3 different users must be performing the activity • Log events pointing to item URL in the Authoring site #Get Usage events available $ss = Get-SPEnterpriseSearchServiceApplicationProxy $ssp.GetAnalyticsEventTypeDefinitions([Guid]::Empty, 3) | ft More at http://blogs.technet.com/b/tothesharepoint/archive/2014/01/21/modify- the-content-search-web-part-display-template-and-use-windows-powershell-to- start-usage-analytics-in-sharepoint-server-2013.aspx
    • 27. • Query rules (prioritize promoted results, add additional result blocks, directly influence ranking – dynamic ordering, sorting, query-based use of a different ranking-model, etc.) • Search Schema (adapt contribution weight by changing context of targeted managed properties) – requires Farm /Search Service Administrator • Custom ranking model • Default Search model • Search Ranking Model with Two Linear Stages General • Catalog Ranking Model • Popularity Ranking Model • Recommender Ranking Model Special People
    • 28. Session Time (GMT) Time (EST) Title Level Speaker Twitter #SP24S090 5:00 1:00 Using the Content Enrichment Web Service with SharePoint Server 2013 Search Technical - Advanced Sezai Komur - NEC Australia @sezai #SP24S021 6:00 2:00 2013 Search, Display Templates, Query Rules, Result Types Technical - Beginner Omer Zubair - CSC @Omer_Zubair #SP24S047 8:00 4:00 Real-life experience building search-driven applications for product-centric sites Technical - Advanced Marius Constantinescu - blue-infinity SA @c_marius #SP24S032 10:00 6:00 Custom Indexing Connectors - How to integrate external system into your SharePoint Enterprise Search Technical - Advanced Heinrich Ulbricht - Communardo Software GmbH @h_ulbricht #SP24S083 11:00 7:00 Search First Migration with SharePoint 2013 – Benefits / Disadvantages Technical - Intermediate Max Melcher - Alegri International Service GmbH @maxmelcher #SP24S034 14:00 10:00 The Search Immaturity Cycle, and How to Create a Search Strategy Business - Intermediate Jeff Fried - BA Insight @jefffried #SP24S009 16:00 12:00 10 Things to Know about Search in SP2013 and Office 365 Business - Beginner Agnes Molnar - Search Explained @molnaragnes #SP24S019 18:00 14:00 Search Topology and Optimization Technical - Advanced Mike Maadarani - MCM Consulting @mikemaadarani #SP24S050 22:00 18:00 Search Driven Application Development in SharePoint 2013 Technical - Intermediate Matt Youngstrom - Magenic @spguru