Difference between revisions of "SUNScholar/Researcher Identification/5.X/ORCID"
Jump to navigation
Jump to search
m |
m |
||
| Line 2: | Line 2: | ||
'''[[SUNScholar/Researcher_Identification|BACK TO RESEARCHER IDENTIFICATION]]''' | '''[[SUNScholar/Researcher_Identification|BACK TO RESEARCHER IDENTIFICATION]]''' | ||
</center> | </center> | ||
| + | ==Requirements== | ||
| + | The ORCID feature in DSpace needs to consult an external database when doing identity lookups. | ||
==Step 1 - Enable the ORCID authority control plugin== | ==Step 1 - Enable the ORCID authority control plugin== | ||
Revision as of 19:03, 3 June 2015
BACK TO RESEARCHER IDENTIFICATION
Contents
Requirements
The ORCID feature in DSpace needs to consult an external database when doing identity lookups.
Step 1 - Enable the ORCID authority control plugin
Edit the following file:
nano $HOME/source/dspace/config/dspace.cfg
Search for ORCID authority control and remove comments to enable.
See example below.
plugin.named.org.dspace.content.authority.ChoiceAuthority = \
org.dspace.content.authority.SolrAuthority = SolrAuthorAuthority
Step 2 - Configure the plugin
Search for ORCID based authority control and uncomment the hashes.
See example below.
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
Step 3 - Enable the authority event listener
Search for the following and ensure the "default" listener includes "authority".
event.dispatcher.default.consumers = authority, versioning, discovery, eperson, harvester
Step 4 - Rebuild DSpace
Click here to rebuild DSpace.
Step 5 - Import existing authorities
After the rebuild, populate the authority index by running the following script:
$HOME/bin/dspace index-authority
