This section describes refinements for attributes that can have
multiple values. It discusses how to configure attributes for multi-select
refinements and also how displaying such refinements affects the user
interface.
About multi-select attributes
If an attribute on your records can have more than one value, it is known as multi-select. For example, an attribute "Flavor" on wine records can have values "Apple" and "Apricot".
Configuring attributes for multi-select refinement
You configure whether an attribute is multi-select by changing the value in the system-navigation_Select attribute of a PDR for a particular attribute defined on records in your data domain, using the Configuration Web Service or Integrator.
Multi-select refinements and the user interface
If an attribute is configured as multi-and or multi-or, this affects the way the Endeca Server calculates the refinements for such attributes, and therefore, has implications for the display of such refinements in the user interface.
Avoiding dead-end query results
Be careful when rendering the selected attribute values of multi-or attributes. It is possible to create an interface that might result in dead ends when removing selected attribute values.
Refinement counts for multi-or refinements
Refinement counts on an attribute that is multi-or indicate how many records in the result set will be tagged with the refinement if you select it. When no selections are made yet, the refinement count equals the total number of records in the result set if that refinement were selected. However, for subsequent refinements, the refinement count may differ from the total results set.