Page History
...
The spring-dspace-addon-discovery-configuration-services.xml file is located in the dspace.dir/config/spring directory.
Structure Summary
Because this file is in XML format, you should be familiar with XML before editing this file. The configurations are organized together in beans, depending on the purpose these properties are used for.
This purpose can be derived from the class of the beans. Here's a short summaries of classes you will encounter throughout the file and what the corresponding properties in the bean are used for.
Download the configuration file and review it together with the following parameters
Class class: | DiscoveryConfigurationService |
Purpose: | Defines the mapping between separate Discovery configurations and individual collections/communities |
Default: | All communities, collections and the homepage (key=default) are mapped to defaultConfiguration |
class Class: | DiscoveryConfiguration |
Purpose: | Groups configurations for sidebar facets, search filters, search sort options and recent submissions |
Default: | There is one configuration by default called defaultConfiguration |
class Class: | DiscoverySearchFilter |
Purpose: | Defines that specific metadata fields should be enabled as a search filter |
Default: | dc.title, dc.contributor.author, dc.creator, dc.subject.* and dc.date.issued are defined as search filters |
class Class: | DiscoverySidebarFacetConfiguration |
Purpose: | Defines which metadata fields should be offered as a contextual sidebar browse option |
Default: | dc.contributor.author, dc.creator, dc.subject.* and dc.date.issued |
class Class: | DiscoverySortConfiguration |
Purpose: | Further specifies the sort options to which a DiscoveryConfiguration refers |
Default: | dc.title and dc.date.issued are defined as alternatives for sorting, other than Relevance (hard coded) |
Default
...
settings
In addition to the summarized descriptions of the default values, following details help you to better understand these defaults. If you haven't yet, download the configuration file and review it together with the following details.
The file contains one default configuration that defines following sidebar facets, search filters, sort fields and recent submissions display:
- Sidebar facets
- sidebarFacetAuthor: groups
By default, this file contains the "defaultConfiguration" for discovery which contains the following settings:
- Sidebar facets configured:
- sidebarFacetAuthor: contains the metadata fields dc.contributor.author & dc.creator with a facet limit of 10 and , sorted by occurrence count
- sidebarFacetSubject: contains groups all subject metadata fields (dc.subject.*) with a facet limit of 10 and , sorted by occurrence count
- sidebarFacetDateIssued: contains the dc.date.issued metadata field has a , which is identified with the type "date" and is sorted by valuespecific date values
- Search filters The configured search filters:
- searchFilterTitle: contains the dc.title metadata field and has a tokenized autocomplete
- searchFilterAuthor: contains the dc.contributor.author & dc.creator metadata fields and has a non tokenized autocomplete configured
- searchFilterSubject: contains the dc.subject.* metadata fields and has a non tokenized autocomplete configured
- searchFilterIssued: contains the dc.date.issued metadata field with the type "date" and has a tokenized autocomplete
- The configured sort Sort fields :
- sortTitle: contains the dc.title metadata field
- sortDateIssued: contains the dc.date.issued metadata field, this sort has the type date configured.
- defaultFilterQueries
- The default configuration contains no defaultFilterQueries
- The default filter queries are disabled by default but there is an example in the default configuration in comments which allows discovery to only return items (as opposed to also communities/collections).
- Recent Submissions
- The recent submissions
- are sorted by dc.date. accessioned which is a date and a maximum number of 5 recent submissions are displayed.
Many of the properties contain lists which use references to point to the configuration elements. This way a certain configuration type can be used in multiple discovery configurations so there is no need to duplicate these.
...
Overview
Content Tools