<field>elements. Please note that fields with the prefix
FACET_should exist in the index for this purpose, as these are processed more efficiently due to your configuration. Fields with the prefix
FACET_are automatically generated during indexing for all
MD_*fields and for
YEAR. Configured should still be the regular field names - the special faceting fields are used internally automatically.
labelFieldcan contain an index field for label values that differs from the faceting field. For example, grouped metadata containing different names of a city (e.g. "Instanbul" and "Constantinople") can be facetted using a common standard value (e.g. a URI). A value composed of the different names is displayed to the user, and the faceting is done using the standard value.
translateLabelscontrols whether listed labels of the facets are to be translated by the messages files. This functionality is active by default and can optionally be switched off.
DC) should be configured as
<hierarchicalField>. The attribute
initialElementNumber=""defines the number of faceting values initially displayed after a search. All others are displayed by expanding the respective faceting element.). The attribute
sortOrder=""can be used to set the initial sorting within the faceting. Possible values are
numerical_desc. If no sortOrder is set, the hits are automatically sorted by occurrence in descending order. The order in the configuration file reflects the order in the interface.
priorityValues, (semicolon-separated) values can be specified which should always be sorted on top if these values occur, independent of the other sorting of the faceting values.
YEARfield is defined, it is displayed in the form of a slider in the interface.
<geoField>is configured, it must have the value
WKT_COORDS, the field through which a geospatial search can be performed in SOLR. Then a map widget will be displayed for each search, through which the search results can be faceted by geographic areas. If there are search results with geographical coordinates, they are displayed in a map above the search results list, too. The attribute
displayResultsOnMapcan be used to control whether markers are displayed in the map widget for all search hits with geo-coordinates. The default is
<geoField>element can also have a
predicateattribute attached to it that describes how to search for matches within a range. There are three possible values:
WKT_COORDS- points or polygons - are completely within the search range. This is the default value.
WKT_COORDSsomehow intersects the search range.
WKT_COORDSthat completely contains the search range.