{"id":1095,"date":"2011-04-24T16:17:31","date_gmt":"2011-04-24T14:17:31","guid":{"rendered":"http:\/\/www.itidea.nl\/?p=1095"},"modified":"2011-04-24T16:19:32","modified_gmt":"2011-04-24T14:19:32","slug":"search-refiners-part-4-user-selection-based","status":"publish","type":"post","link":"https:\/\/www.itidea.nl\/index.php\/search-refiners-part-4-user-selection-based\/","title":{"rendered":"Search Refiners (part 4) \u2013 User selection based"},"content":{"rendered":"

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

    \n
  1. Search Refiners part 1 – Expanding the OOTB search Refinement Panel <\/a><\/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 (this post)<\/li>\n<\/ol>\n

    After building a chart based search refiner, now it’s time to get some interaction in the selection of search terms. In this post I will show you how to use jQuery in combination with the RefinementManager.
    \nWith interaction I mean the user can drag a search term to a place on the screen to refine the results. Unfortunately the OOTB Refinement Panel and the results webpart ‘talk’ to each other by the parameters in the url. Therefor a postback must occur to actually refine the results with the selected term. But a little animation just looks great.\u00a0<\/p>\n

    For the drag and drop functionality I used the standard jQuery library and a custom jQuery UI selection. With this functionality in hand I created my own drag and drop implementation for this specific solution.\u00a0<\/p>\n

    Script part<\/h3>\n

    Because I already have a little experience with programming against the RefinementManager class in the chart based example I first focused on the drag drop functionality.
    \nTwo divs are placed on the screen:
    \n1. to list all the terms the user can choose from to select
    \n2. the already selected terms by the user\u00a0<\/p>\n

    The items in both divs has to have the ability to drag items from and to drop items to. The user has to have the possibility to drag items from the ‘terms to select’ part to the ‘selected terms’ part and vice versa.
    \nBoth the divs contain an unordered list with list items.
    \nSo a single div with items in it looks in plain HTML like:<\/p>\n

    \r\n<div>\r\n<ul>\r\n<li>item01<\/li>\r\n<li>item02<\/li>\r\n<\/ul>\r\n<\/div>\r\n<\/pre>\n
    A single item has to be draggable to move it from the ‘terms to select’ to the ‘selected terms’ part(and vice versa). So the li element has to be draggable.
    \nOn the other hand when a li element a dragged, the list to which the single item has to be added has to be droppable, the ul element.\u00a0<\/p>\n
    To accomplish this just a few lines of jQuery are neccesary, the rest is alredy build in the jQuery libraries.<\/p>\n
    \r\n\u00a0\u00a0\u00a0 var $currentSelectedItems = $("#selectedTerms"),\r\n\u00a0$baseItemList = $("#termsToSelect");<\/pre>\r\n\u00a0\r\n\r\n\u00a0\u00a0\u00a0 \/\/make the li's in the selectedTerms div draggable\r\n\u00a0\u00a0\u00a0 $("li", $currentSelectedItems).draggable({\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 appendTo: $baseItemList,\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 helper: "clone"\r\n\u00a0\u00a0\u00a0 });\r\n\u00a0\r\n\r\n\u00a0\u00a0\u00a0 \/\/make the ul in the selectedTerms div droppable\r\n\u00a0\u00a0\u00a0 $("ul", $currentSelectedItems).droppable({\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 accept: "#termsToSelect li",\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 hoverClass: "ui-state-hover",\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 drop: function (event, ui) {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 moveTerm(ui.draggable, $currentSelectedItems);\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }\r\n\u00a0\u00a0\u00a0 });\r\n<\/pre>\n
    The draggable functionality is nothing special. The element passed to appendTo is the container during dragging. Second the clone helper is used here, which means a clone of the actual item is dragged around. Another option here is original, which drags the original item around.\u00a0<\/p>\n
    The droppable functionality uses different options. First I’m telling the element what items to accept: an li element within ‘termsToSelect’. Second a nice hover class and finally a function is specified what to do when the actual drop occurs: move the term to from ‘terms to select’ to ‘selected terms’ and navigate to the url which the item received from the RefinementPanel (getting there soon).\u00a0<\/p>\n
    \r\n\u00a0\u00a0\u00a0 \/\/move term\r\n\u00a0\u00a0\u00a0 function moveTerm($item, $listToAdjust) {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 $item.fadeOut(function () {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 var $list = $("ul", $listToAdjust);\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 $item.appendTo($list).fadeIn();\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 window.location.href = $item.find('a').attr("href");\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 });\r\n\u00a0\u00a0\u00a0 }\r\n<\/pre>\n
    \u00a0\u00a0<\/p>\n
    The script above is the script which act on the ‘selected terms’ part ($currentSelectedItems or $(“#selectedTerms”)). The same functionality have to be added to the ‘terms to select’ part. Because it’s almost the same this code it’s left out here for readability.\u00a0<\/p>\n
    That’s is with all the script, let’s move the code behind all this.\u00a0<\/p>\n
    The webpart<\/h3>\n
    The code behind this (just a regular webpart) works with the RefinmentManager class of the page as in the chart based example, the previous post in this series. The extra functionality here is that the selected term is needed from the RefinmentManager’s filter. If a term is selected or not is just another node in the refinement xml, just as Value and Url as shown in the following code listing:
    \n\u00a0<\/p>\n
    \r\nstring filterValue = filter.SelectSingleNode("Value").InnerText;\r\nstring filterUrl = filter.SelectSingleNode("Url").InnerText;\r\n\u00a0\r\n\r\nif (filter.SelectSingleNode("Selection").InnerText.Equals("Selected"))\r\n{\r\n\u00a0\u00a0\u00a0 dateSelectedList.Add(new ListItem(filterValue, filterUrl));\r\n}\r\nelse\r\n{\r\n\u00a0\u00a0\u00a0 dateToSelectList.Add(new ListItem(filterValue, filterUrl));\r\n}\r\n<\/pre>\n
    dateSelectedList and dateToSelectList are both generic lists of ListItems and in the RenderContents method the items in the lists are added to the appropriate containers.\u00a0<\/p>\n
    After putting this all together it looks like the folowing image when no selection are made by the user:
    \n    \"\"<\/a><\/p>\n
    When dragging starts from ‘terms to select’ the location where to drag to is highlighted:
    \n    \"\"<\/a><\/a>\u00a0<\/p>\n
    Because ‘helper’ was set to ‘clone’ earlier the item that’s dragged, ‘Past Week’, is still in the ‘terms to select’ container and also moving around the screen.\u00a0<\/p>\n
    When dropping the item for a moment the screen looks like (because of the ‘appendto’ option):
    \n    \"\"<\/a>\u00a0\u00a0<\/p>\n
    And then a postback occurs and it looks like:
    \n    \"\"<\/a>\u00a0\u00a0\u00a0\u00a0<\/p>\n
    And the terms displayed behave just like the OOTB refiners.\u00a0\u00a0\u00a0\u00a0<\/p>\n
    Summary<\/h3>\n
    The OOTB refinement functionality is great, but it can be made much more attractive with just a little script as shown in this post. What I’ve shown you here is just a little example with one of the possibilities to make it more attractive. There are a lot of jQuery libraries with excellent functionality which you can use to do all kinds of stuff and don’t forget the design. This example looks nothing like a nice production ready refiner, but go wild and make it look awesome.<\/p>\n","protected":false},"excerpt":{"rendered":"
    In this series:\u00a0\u00a0 Search Refiners part 1 – Expanding the OOTB search Refinement Panel Search Refiners part 2 – Use of CustomFilters Search Refiners part 3 – Chart based Search Refiners part 4 – User selection based (this post) After … 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":[20,11,42],"class_list":["post-1095","post","type-post","status-publish","format-standard","hentry","category-sharepoint-2010","tag-c","tag-jquery","tag-sharepoint-2010"],"_links":{"self":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1095","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=1095"}],"version-history":[{"count":13,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1095\/revisions"}],"predecessor-version":[{"id":1113,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1095\/revisions\/1113"}],"wp:attachment":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/media?parent=1095"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/categories?post=1095"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/tags?post=1095"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}