Skip to content
SharePoint Sample Search Configurations
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.gitattributes
.gitignore
CrawlTimeSchema.xml
CrawlTime_SearchConfiguration.xml
HideFromDelveConfiguration.xml
README.md
TagBoost-Low-SearchConfiguration.xml
TagBoost-Max-SearchConfiguration.xml
TagBoost-Medium-SearchConfiguration.xml

README.md

SharePoint Sample Search Configurations

SharePoint Sample Search Configurations

  • TagBoost-Max-SearchConfiguration.xml - Boost equal to Title
  • TagBoost-Medium-SearchConfiguration.xml - Boost equal to SocialTag
  • TagBoost-Low-SearchConfiguration.xml - Boost equal to Body
  • CrawlTimeSchema.xml - Add CrawlTime managed property to see when an item was last crawled
  • HideFromDelveSchema.xml - By using a Yes/No column named HideFromDelve in SharePoint you can omit them from the Delve board

Description

Any column which is of type managed metadata in SharePoint will get it's values boosted with this search schema update.

For a detailed description of when and how to use these files check out How to: Boost metadata in SharePoint search results

Technical implementation

The search configuration file is creating a new managed property named TagBoost, mapping the catch-all crawled property ows_taxId_MetadataAllTagsInfo to it.

The different files are then associating the context level of TabBoost to the weight group of already existing managed properties in the default rank profile.

Installation SharePoint Online

The files can be imported as search configurations files. For SharePoint Online do this at the tentant level from https://tenant-admin.sharepoint.com/_layouts/15/searchadmin/importsearchconfiguration.aspx?level=tenant

Installation SharePoint 2013 - On-premises

If you install at a site collection or in a multi tenancy environment follow the same procedure as for SharePoint Online. Remember that theany schema update done at a site or site collection level will only be valid for searches executed on that site collection. Meaning if content is residing on one site collection and search center on another, it won't work. Then you have to deploy the changes globally to the SSA.

If you want to do deploy the boost at the SSA level, you will manually have to create the managed property, change the weight group and map the crawled property as shown in How to: Boost metadata in SharePoint search results.

You can’t perform that action at this time.