All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
Info | ||
---|---|---|
| ||
Please note that ORCID API 1.2 was turned off on August 1, 2018. To use the current ORCID API 2.x, you will need DSpace 5.9 or DSpace 6.3 or newer. Details: DS-3447. |
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
...
Running this script again will update the index and keep the index clean. For example if an author occurs in a single item and that item is deleted the script will need to be run again to remove it from the index. When run again it will remove all records that no longer have a link to existing authors in the database.
Usage in DSpace
...
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.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.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.webui.browse.index.2 = author:metadata:dc.contributor.*,dc.creator:text
should become webui.browse.index.2 = author:metadataAuthority:dc.contributor.author:textauthoritychoices.closed
, authority.required,
authority.minconfidence
....