Faceted Navigation: Open Parametric

    
Share/Bookmark

Problem Summary

This pattern shares many of the characteristics of Faceted Navigation: Vertical Stack, in that:

  • Users need to evaluate and understand the overall navigation space and see what's available at a glance
  • Users need to refine their results to locate specific records or explore relevant subsets.

However, its origin lies in the requirement to provide a faceted navigation experience for users who prefer by convention a "parametric search" style of interaction in which the facets are laid out in a horizontal sequence and are displayed in their "open" state by default. This is typical of sites such as Newark, i.e., manufacturers and distributors of "parameterized" products such as electronic components.






Usages

The usages are the same as for Faceted Navigation: Vertical Stack, however:

  • This pattern is aimed predominantly at users who want to be aware of and actively consider tradeoffs among varied facets and may prefer (by convention) a "parametric search" style of interaction in which the facets are laid out in a horizontal sequence with dimension values displayed in their “open” state by default.
  • As a consequence of the above, this style of faceted navigation supports the use of "inline" mementos, i.e., markers within the faceted navigation panel that indicate which facet values are currently selected. As a result (in contrast to Faceted Navigation: Vertical Stack), the current navigational state is implicit in the state of the navigation menu, meaning that a separate breadbox may not be necessary.

Constraints and Challenges

• Displaying too many choices can be overwhelming for the user, particularly as the facets are all displayed in their "open" state by default.
• Displaying the facets in fixed positions can lead to wasted screen space (in displaying facets that would otherwise have been refined away).
• If the width of all the combined facets is greater than the width of the page, horizontal scrolling will be required. As a result, some facets will be hidden from view at any given time.
• Arranging the facets in an N by M table and wrapping them across the page can remove the need for horizontal scrolling, but depending on how the facets wrap, space can be wasted (e.g., if six facets are laid out in a table that is five columns by two rows). In addition, this approach risks pushing the search results below the fold/out of the user’s immediate view without scrolling.

Solution Elements

  1. Support solution elements #1 to #8 from the Faceted Navigation: Vertical Stack design pattern.
 
  1. Support solution elements #2, #4, #5, and #6 from the Breadbox design pattern.
 
  1. Limit the number of facets initially displayed to an easily scanned list that does not require horizontal scrolling.
 
  1. Display the facets in a consistent left-to-right sequence.
 
  1. Provide a visual or textual cue inviting users to see more/all facets when more facets than those displayed onscreen are available.
 
  1. When users select the "more/all" option, present the additional facets to the right of the existing ones, using a suitable UI control (e.g., a horizontal scrollbar).
 

Cautions

  1. Changing the ordering/sequence of facets when they get refined away risks disorienting the user.
 
  1. Presenting too many facets in a horizontal grid or table risks information overload and compromises the user's ability to readily discern and interact with available refinement options.
 

Comments (0)

Leave a comment...

 

 


Your comment:




 
 
 

 

Additional Examples

Further Reading