- the facets that were calculated (probably mirroring all categories in the order requested)
- the facet values for each facet that had at least one hit in the search result set (constrained by the limit set in the request)
- the number of hits for each facet value in the result set
the cql query clause that must be ANDed with the original query in order to search for the hits for the given facet value (this can simply be derived "\[facetField\]=\[facetValue\]") Wiki Markup
- A normalized version of the requested facet parameters, to prevent the client from having to maintain that state, and to show what default paging parameters were applied by the server (in the even that they weren't specified).
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="723f08da-788c-4dcc-ba01-fa872c91a799"><ac:plain-text-body><![CDATA[
[facetName1],[maxValueCount],[offset] [facetName2],[maxValueCount],[offset] ]
The maxValueCount and offset are optional paging parameters. If excluded, the server decides the paging rules which will be explicitly listed in the response.
dc.format dc.date,10, dc.subject,10,10
A request for all of the represented dc.format values, the first 10 represented dc.date values and the second page (of length 10) of the dc.subject values represented in the search results. (Sort order for paging is left up to the server, but is generally expected to be alphabetical. If sort order is a problem, the client always has the option to request all values, and handle sorting and paging at their end.