Page History

...

Storage of related metadata

Configuration -

...

wip

In the Enabling the ORCID authority control section, you have been told to add this block of configuration.

solr.authority.server=${solr.server}/authority
choices.plugin.dc.contributor.author = SolrAuthorAuthority
choices.presentation.dc.contributor.author = authorLookup
authority.controlled.dc.contributor.author = true
authority.author.indexer.field.1=dc.contributor.author

The ORCID Integration feature is an extension on the authority control in DSpace. Most of these properties are extensively explained on the Authority Control of Metadata Values documentation page. These will be revisited but first we cover the properties that have been newly added.

• The solr.authority.server is the url to the solr core. Usually this would be on the solr.server next to the oai, search and statistics cores.
• authority.author.indexer.field.1 and the subsequent increments configure which fields the authority consumer indexes.

That's it for the novelties. Moving on to the generic authority control properties:

• With the authority.controlled property every metadata field that needs to be authority controlled is configured. This involves every type of authority control, not only the fields for ORCID integration.
• The choices.plugin should be configured for each metadata field under authority control. Setting the value on SolrAuthorAuthority tells DSpace to use the solr authority cache for this metadatafield, cfr. Storage of related metadata.
• The choices.presention should be configured for each metadata field as well. The traditional values for this property are select|suggest|lookup. A new value, authorLookup, has been added to be used in combination with the SolrAuthorAuthority choices plugin. While the other values can still be used, the authorLookup provides a richer user interface in the form of a popup on the submission page.
• More existing configuration properties are available but their values are independent of this feature and their default values are usually fine: choices.closed, authority.required, authority.minconfidence.

Changes to the configuration always require a server restart before they're in effect.Explain which configuration parameters are available, in which files they can be found and which procedure is required for updating. Does it require a rebuild or is a tomcat restart enough, etc?