{"id":1025,"date":"2011-02-07T12:16:09","date_gmt":"2011-02-07T11:16:09","guid":{"rendered":"http:\/\/www.itidea.nl\/?p=1025"},"modified":"2011-04-24T16:20:32","modified_gmt":"2011-04-24T14:20:32","slug":"search-refiners-part-1-expanding-the-ootb-search-refinement-panel","status":"publish","type":"post","link":"https:\/\/www.itidea.nl\/index.php\/search-refiners-part-1-expanding-the-ootb-search-refinement-panel\/","title":{"rendered":"Search Refiners (part 1) – Expanding the OOTB search Refinement Panel"},"content":{"rendered":"

In this series:\u00a0\u00a0<\/p>\n

    \n
  1. Search Refiners part 1 – Expanding the OOTB search Refinement Panel (this post)<\/li>\n
  2. Search Refiners part 2 – Use of CustomFilters<\/a><\/li>\n
  3. Search Refiners part 3 – Chart based<\/a><\/li>\n
  4. Search Refiners part 4 – User selection based<\/a><\/li>\n<\/ol>\n

    Intro<\/h3>\n

    A large multinational company has several contracts. These contract are stored in SharePoint. Based on the
    \nmultinational character of the company the contracts are stored in different languages.
    \nTitles of the documents are all in English, so there is no way to determine from the title in what language the
    \ndocument is written. Therefor a new column is introduced where the language can be stored.
    \nThis column in a lookup column to another list where all the languages are defined.
    \nWhen people are searching for contracts there is no quick way to see in what language the document is written. To
    \nprevent users to open multiple documents to see the language of the content a search refiner will help them out.\u00a0\u00a0<\/p>\n

    The existing OOTB refinement panel can be expanded just with XML.
    \nBefore doing so some preparations has to be done.\u00a0\u00a0<\/p>\n

    Create lists<\/h3>\n

    First a custom list has to be created which will store the possible language values.
    \nA document library has to be added to a site which will contain the documents for the contracts. An additional column
    \nhas to be added to let the user choose the language in which the document is written. This will be a lookup column to
    \nthe previous created list of languages.
    \nA set of documents are uploaded with their languages set.
    \n    \"\"<\/a><\/p>\n

    Crawl content<\/h3>\n

    Start Central Administration, select Application Management and Manage Service Applications. Select Search Service
    \nApplication to display the Search Administration page.
    \nSelect Content Sources and start an incremental crawl.\u00a0\u00a0<\/p>\n

    Create managed property<\/h3>\n

    When this is finished create a Managed Property called Language and add a mapping to the crawled property ows_Language.
    \n    \"\"<\/a>
    \nStart a Full Crawl.\u00a0\u00a0<\/p>\n

    Check if any results are present in the crawled property.\u00a0\u00a0<\/p>\n

    Modify Filter Category Definition<\/h3>\n

    Create an Enterprise Search Center and edit the Refinement Panel. In the webpart properties in the section Refinement
    \nselect the button next to the Filter Category Definition textbox to show all the text in it.
    \n    \"\"<\/a>\u00a0\u00a0<\/p>\n

    The XML is not difficult to read and understand when copying and pasting the XML into an XML file in Visual Studio..
    \nEven without checking on the full Refinement Panel XML schema it’s pretty clear what to do by copying an existing
    \nCategory element and make some changes.
    \nFull explanation of this schema can be found on MSDN here     http:\/\/msdn.microsoft.com\/en-us\/library\/ee819920.aspx<\/a>\u00a0\ufffd
    \nAdd to the filter category definition in the webpart properties:<\/p>\n

    \r\n<Category Title="Language" Description="Language of document" Type="Microsoft.Office.Server.Search.WebControls.ManagedPropertyFilterGenerator" MetadataThreshold="3" NumberOfFiltersToDisplay="3" MaxNumberOfFilters="20" ShowMoreLink="True" MappedProperty="Language" MoreLinkText="show more" LessLinkText="show fewer" \/>\r\n<\/pre>\n
    Don’t forget to uncheck ‘Use default configuration’.
    \nUnchecking this option is quite important. When this checkbox is selected any changes to the filter category definition
    \nconfiguration are not persistent. A better experience would be disabling the Filter Category Definition when this
    \ncheckbox is selected…\u00a0\u00a0<\/p>\n
    Apply and save the changes.\u00a0\u00a0<\/p>\n
    Test the refiner<\/h3>\n
    Start a search on one of the words in the title of one of the documents uploaded in the created Document Library.
    \nNotice the Language refiner on the left.
    \n    \"\"<\/a>\u00a0<\/p>\n
    The values displayed of the Language refiner is default sorted by count. This means the value which is used most
    \nappears on top.\u00a0\u00a0<\/p>\n
    Refiner is not showing<\/h3>\n
    When the refiner is not showing in the Search Center there are a few things to check.<\/p>\n
      \n
    1. Make sure to fully crawl the content after creating the managed property and confirm the crawled property contains
      \nvalues.<\/li>\n
    2. Make sure there is enough data which uses in this case the language. In the above XML the value of the
      \nMetadataThreshold attribute is set to 3. This means the number of results that must contain a value to display the
      \nfilter generator under the filter category is set to 3.<\/li>\n
    3. Uncheck Use Default Configuration in the webpart properties of the Refinement Panel, section Refinement.<\/li>\n
    4. In the webpart properties of the Refinement Panel in the secion Refinement a value is displayed for Number of
      \nCategories to Display. If the number of categories exceeds this number and the new category is defined last in the XML,
      \nit\u00a0won’t show up.\u00a0\u00a0<\/li>\n<\/ol>\n
      Summary<\/h3>\n
      SharePoint provides OOTB an easy way to create your own search refiners.
      \nA crawled property, content and some XML to define the filter category are sufficient.<\/p>\n","protected":false},"excerpt":{"rendered":"
      In this series:\u00a0\u00a0 Search Refiners part 1 – Expanding the OOTB search Refinement Panel (this post) Search Refiners part 2 – Use of CustomFilters Search Refiners part 3 – Chart based Search Refiners part 4 – User selection based Intro … Read More »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[42],"class_list":["post-1025","post","type-post","status-publish","format-standard","hentry","category-sharepoint-2010","tag-sharepoint-2010"],"_links":{"self":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1025","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/comments?post=1025"}],"version-history":[{"count":15,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1025\/revisions"}],"predecessor-version":[{"id":1043,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1025\/revisions\/1043"}],"wp:attachment":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/media?parent=1025"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/categories?post=1025"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/tags?post=1025"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}