Designing Faceted Search: Getting the basics right (part 3)
Join the DZone community and get the full member experience.Join For Free
faceted search offers tremendous potential for transforming the search experience. it provides a flexible framework by which users can satisfy a wide variety of information needs, ranging from simple fact retrieval to complex exploratory search and discovery-oriented problem solving. but how do we extend such a framework to accommodate not just dozens of facet values, but thousands, or even tens of thousands? it is clearly not practical to display such lists in their entirety. so how can we provide adequate flexibility yet ensure that the user is not overwhelmed in these situations? in this post, we’ll examine the main approaches. in so doing i’d like to acknowledge the work of james kalbach , whose previous posts on the subject may be the first attempt to document the topic in a comprehensive manner.
2. display formats and scalability
in previous posts we reviewed a number of display formats for facets and whether their default state should be open or closed by default. a key principle to emerge from that discussion is that it is important for facets to offer an appropriate information scent , i.e. revealing their content and providing navigational cues to help users to formulate productive search strategies. in practice, this means that facets should ideally be open by default, and display a representative sample of facet values. of course, exactly what constitutes ‘representative’ can be defined in many ways, but in effect this usually entails ordering the list of values by frequency (or some other measure of popularity) and then displaying the first half dozen or so. this raises the question: if the user does want to see the full list of values, how do we extend the display to accommodate them?
there are three main solutions to this problem:
- avoid it entirely by displaying the complete list of facet values by default (although this approach is not always applicable for reasons we’ll discuss below)
- use an expandable container that extends on demand to accommodate additional values.
- use a secondary container to display the longer list, with an associated transition to communicate the relationship between the two.
let’s examine each approach in turn.
3. display all values by default
the simplest approach to the problem of showing more values is to avoid it completely by displaying the complete list of facet values by default. this is possible if a display format is used that can scale to accommodate lists of arbitrary length, such as a scrollable container. however, it also assumes that the lists of values are bounded in some way to a manageable size. scroll bars may be infinitely scalable in principle, but in practice few users would wish to deal with lists of more than hundred items or so (and in many cases significantly fewer).
an example of displaying all items by default can be found at carzone , which by default displays facets in a vertical stack configuration using scrollable containers for lists of greater than a dozen or so (such as makes & models in the example below):
a variation on this approach can be seen at farnell , which displays facets in the open parametric configuration. this arrangement applies the principle along both axes: the facets themselves are displayed within a horizontal scrollable panel (extending off the screen to the right) and the values within each of the facets are displayed within vertically scrollable containers. all of the scroll bars appear as required (so they are suppressed for facets with fewer than a handful of values):
4. expandable containers
for many applications, however, displaying all facet values by default is not a scalable solution. instead, a ‘by request’ approach is required. perhaps the simplest of these approaches is to present an option to expand the facet inline, i.e. extend its dimensions to accommodate a larger set of values. an example of this approach can be found at ncsu libraries , which displays the top 5 values by default, but expands this vertically to accommodate the top 30 when the ‘show more’ link is selected (as illustrated by the subject facet in the image below):
this approach is conceptually simple; few users would find the transition between states confusing or intrusive. however, one flaw in this particular execution is that there is no option to show fewer values once a facet is expanded, except by closing it completely. consequently, once two or more facets have been expanded, it is very difficult to review the contents of the remaining facets without repeated scrolling.
a variation on this approach can be seen at hoovers , whose option to see more values results in a vertical scroll bar appearing within each facet (as illustrated by the location and employees facets):
again, the approach is conceptually simple, with a straightforward transition between states.
5. secondary containers
while the first two approaches display both the collapsed and expanded set of facet values within the same container, a third approach is to display the expanded set in a new container, and communicate the relationship between the two using visual design cues and/or an appropriate transition.
perhaps the most lightweight variation on this approach is to use a detail overlay to display the full set of facet values adjacent to the original set. artist rising ’s ‘more choices’ link, for example, displays the remaining facet values as a secondary list, extending the original set in a contiguous manner. one advantage of this approach is that the sort order is preserved, e.g. in the example below the complete list of subjects is still presented in descending order of record count:
a variation on this approach can be seen at food network , which shows three values by default but presents an option to show more of any facet on request. this approach uses an overlay as before, but instead of displaying just the additional values it displays the entire list:
this has the advantage the list can now be displayed in alphabetical order (to facilitate visual scanning). note that in this display the record counts are suppressed, possibly to reduce any confusion that may arise by displaying such counts in an apparently unsorted order (or perhaps just to reduce clutter and allow the alphabetic ordering to be more apparent).
the transition from one sort order to another may introduce something of a cognitive disconnect for some users, although this is mitigated somewhat by the minimal size of the collapsed list. note also that the contents of the overlay in this case are limited to a maximum of 50 values, presumably to mitigate the overhead of scrolling an extended list.
a somewhat heavier approach is to use a modal overlay to display the full set of facet values. an example of this can be seen at ebay , which uses the overlay to present the complete list of values for each facet in its own pane. this design allows only one facet to be visible at any one time (in keeping with the principles we discussed in the previous post on interaction models for faceted search ). in common with food network, this approach limits the display of expanded facets to the top 50 or so:
both of the above approaches support the principle of minimising the disruption to the user’s mental flow by staying on the page . a more heavyweight approach is to present the list of values on their own page, which is the approach adopted by amazon on certain sections of their site (e.g. footwear). the example below shows the use of multi-select facets displayed using checkboxes in a vertical stack configuration, with options to ‘see more’ for both brand and seller:
however, selecting the ‘see more’ option (e.g. for brand) loads a new page displaying the entire set values for that facet:
surprisingly, this page presents the options as hyperlinks (rather than checkboxes), which as we have seen in a previous post are better suited to single select facets. indeed, that is exactly how they behave: selecting one value immediately returns the user to the original results page with that facet value now applied. interestingly, it seems the list of values attempts to be exhaustive, which can produce some extremely long pages (e.g. such as the list of authors for the entire books section).
6. hybrid approaches: search within facets
in the sections above we discussed the primary approaches to showing more values, such as extending the existing container or displaying a new one. what these approaches have in common is that they allow the user to browse a longer list of values to make further selections. however, an alternative approach exists, which allows the user to search for specific values rather than browse. an example of this can be seen at linkedin , which by default displays multi-select facets using checkboxes in a vertical stack configuration:
as expected, each of these facets shows the first half dozen or so values by default (ordered by record count), with an option to “show more…” that extends the list to include the first dozen or so. but what makes this design different is the use of the text field (shown below the current company and location facets). as soon as the user starts to type into this box, an autocomplete dialog appears with up to ten suggested values. in this respect, this design offers a more complete experience than the others above, since it allows the user to either search or browse to select further facet values.
over the last few weeks we’ve looked at some of fundamental design issues in faceted search, such as
(e.g. where to place the faceted navigation menus) and
(e.g. whether they should be open or closed by default) and
in this article, we’ve complemented that with a review of the various
techniques for managing long lists of facet values. this means that the
complete list of articles on faceted search design now covers the
- designing faceted search – (part 1: layout & state)
- designing faceted search – (part 2: fundamental principles + display formats)
- designing faceted search – (part 3: showing more values)
- interaction models for faceted search
wayfinding and navigation in faceted search
with a subject as rich and complex as faceted search, no review can ever be complete, and there is always more to learn, explore, and debate. and we’re aware that this collection of articles still lacks a comprehensive discussion of the issues surrounding the use of record counts and smart dead ends. but we’d like to think that this article marks the final section for a forthcoming book chapter on designing faceted search.
of course, if you think we’ve missed any topics or would like to suggest others, then we’d love to hear. feel free to drop me a line either here or via email at tgr at uxlabs.co.uk.
Published at DZone with permission of Tony Russell-rose, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.