Refinements are handled slightly differently in Studio than in
other front-end applications powered by Endeca Server.
Studio uses the
Available Refinements component, which utilizes
the Conversation Web Service, while other applications should rely directly on
the Conversation Web Service:
- Studio. In Studio,
each component affected by the
Available Refinements component automatically
uses suggested refinements and information received from refinements
computation, such as the order of refinements or a number of refinements for a
given attribute.
- Other front-end
applications. For other front-end applications powered by Endeca Server,
including custom-built applications, you can use the Conversation Web Service
requests to work with refinements and build the user interface around them,
utilizing the principles of Guided Navigation. For example, you can:
- Request all available
refinements from Endeca Server, so that you can display them as suggested
refinements in the user interface.
- Request a list of
applied refinements from Endeca Server, so that the current navigation state is
reflected in the user interface, showing the users their relative location as
they navigate the data.
- Configure the behavior
of refinements, such as number of refinements to be displayed, or the order in
which to display them, or whether to return records tagged with implicit
refinements.
In the Conversation Web Service, suggested refinements are included
in the navigation menu configuration, and the current navigation state
configuration lets you include applied refinements, both implicit and
explicitly-selected.
For information on how to use the Conversation Web Service requests
for refinements, see
Working with attributes and refinements using the API.
