Breadbox

RSS

Problem Summary

The breadbox is a container that aggregates the parameters defining the current search/navigational state for a given set of search results in a single location or zone (i.e., a conceptual "box"). More powerful and flexible than traditional static breadcrumbs, a breadbox can include category parameters, faceted attributes, and keyword search terms. A breadbox:

Addresses signposting needs for the user by providing a consistently located and visible reminder of his navigational context as it changes with the application or removal of navigational refinements. The breadbox aggregates mementos for all search/navigation criteria in one location.
Allows the user to modify search results by selectively removing individual refinements.
Provides the user with the necessary information and tools to make adjustments to the navigational context to obtain an optimal result set.

Usages

In applications where the primary means of navigation is through the selection of facets and values.
When the user requires an awareness of the current navigational state.
In complex applications where users may need to apply several facet selections to produce a manageable set of search results.

Constraints and Challenges

Purpose: The breadbox must clearly communicate its function in the interface and differentiate itself from the faceted navigation and other breadcrumbs or signposting that co-exist on the page. Faceted navigation is the means for selecting facet values; the breadbox displays the search criteria and allows for modification or removal of individual elements.
Visibility: To be useful, the breadbox must be visually prominent enough to attract the user's attention.
Screen real estate: The breadbox should integrate closely with faceted navigation menus and search results without pushing either below the fold or otherwise compromising their visibility.
Presentation: Different types of facets may require different presentations. Keywords, non-hierarchical facets, hierarchical facets, and other refinements must be able to co-exist and clearly communicate the context of the user's search.

Solution Elements

Expand All

Reserve a consistent location for the breadbox to appear on every result page.
- If vertically oriented: above the vertical stack of guided navigation.
- If horizontally oriented: across the top of the search results.
- To help establish that the breadbox tracks the user’s refinements as they are made, its location must reflect the close connection with the faceted navigation menu. This will also help to distinguish the breadbox from other breadcrumbs or signposting devices elsewhere on the page.
Show More...

For each refinement --search term or facet value -- the user applies, present a discrete breadcrumb, or "memento", in the breadbox that is visually recognizable as an independent unit.

In cases where a dimension value is part of a hierarchy (such as "category"), the memento may be presented as a hierarchical structure to reveal the higher levels.

Show More...

Display the breadcrumbs sequentially, based on the order in which they were selected by the user. Dimensions of the same type, however, should cluster into groups regardless of the order in which they were selected.
- For example, within a breadbox that includes several attribute mementos, the "category" and "subcategory" mementos should appear next to each other or as a group to convey their hierarchical relationship.
- Avoid an implication of hierarchy for mementos in the breadbox if there is not one implicit in their structure. In a horizontal breadbox, dividers between mementos such as ">", or "/" imply a hierarchical relationship.
Show More...

Each refinement breadcrumb/memento should have a visible control to remove it from the search context.
- Graphic icons or "(X)" are preferred over "clear" or other similar text to communicate that the mementos may be removed from the search context.
- Individual attribute mementos should be removable in any order, regardless of the order in which they were initially added.
- Mementos that are part of a hierarchy may also be removed by the user regardless of the order in which they were added, but any mementos that are children of the node being removed must also be removed at the same time. Other mementos may also need to be removed depending on the relationships among the facets, as certain attributes may no longer be applicable within the context of a wider scope (see "Rationale" section, below.)
Show More...

Consider prohibiting the user from removing the initial keyword term or browse selection for his search.

Removing the initial foundation of the search can lead to an awkward set of results, as all refinements were made based upon this foundation.

Show More...

In most cases, facet values in the breadbox should be displayed as name/value pairs, showing the name of each facet and its associated value.
- But if the data set is simple and there is not likely to be any ambiguity about the meaning of a particular facet value, the value alone may be presented.
- Measurements or technical attributes should always be presented with the name of the dimension to clarify context. For example, "width: 4 inches (X)", "thickness: 0.125 inches (X)".
Show More...

When multiselect facets are used (e.g., when a user can select more than one value within a facet at the same time to create "unions"), display facet values in the breadbox as part of the facet group, regardless of the order in which they were selected.

Show More...

Create a separate group for hierarchical mementos and non-hierarchical mementos in the breadbox.
- If a horizontal breadbox is used, consider listing non-hierarchical mementos separately from the hierarchical mementos.
- If a vertical breadbox is used, create groupings of mementos by including dimension name labels.
Show More...

When "search within" functionality is present, group the "search within" term(s) together with any initial keyword search term.

Show More...

Top

Cautions

Expand All

Avoid displaying non-hierarchical attribute mementos in a manner that implies hierarchy.

Show More...

Avoid presenting hierarchical and non-hierarchical breadcrumbs together without separation.

Show More...

Top

Rationale

Expand All

Why prevent the user from removing his or her initial keyword search term?

Why separate hierarchical mementos from non-hierarchical attribute mementos?

Top

Comments (0)

Expand All

Related Patterns

Search Box

Faceted Navigation: Vertical Stack

Search Within

Additional Examples

bulbs.com

1800flowers.com

Breadbox

Problem Summary

Usages

Constraints and Challenges

Solution Elements

Reserve a consistent location for the breadbox to appear on every result page.

For each refinement --search term or facet value -- the user applies, present a discrete breadcrumb, or "memento", in the breadbox that is visually recognizable as an independent unit.

Display the breadcrumbs sequentially, based on the order in which they were selected by the user. Dimensions of the same type, however, should cluster into groups regardless of the order in which they were selected.

Each refinement breadcrumb/memento should have a visible control to remove it from the search context.

Consider prohibiting the user from removing the initial keyword term or browse selection for his search.

In most cases, facet values in the breadbox should be displayed as name/value pairs, showing the name of each facet and its associated value.

When multiselect facets are used (e.g., when a user can select more than one value within a facet at the same time to create "unions"), display facet values in the breadbox as part of the facet group, regardless of the order in which they were selected.

Create a separate group for hierarchical mementos and non-hierarchical mementos in the breadbox.

When "search within" functionality is present, group the "search within" term(s) together with any initial keyword search term.

Cautions

Avoid displaying non-hierarchical attribute mementos in a manner that implies hierarchy.

Avoid presenting hierarchical and non-hierarchical breadcrumbs together without separation.

Rationale

Why prevent the user from removing his or her initial keyword search term?

Why separate hierarchical mementos from non-hierarchical attribute mementos?

Comments (0)

Leave a comment...

Your comment:

Related Patterns

Additional Examples

Further Reading