Page History
...
| Tasklist | ||||
|---|---|---|---|---|
| ||||
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name|| |F|M|T|1389620440889| |stuart.yeates@vuw.ac.nz|Use Case and high level benefits. Can someone with limited technical background understand what this is about?| |FT|M|T|1389620638059| |bram1412336317233|antoinesnyers|Step by step how to use. Can someone with limited technical background use the feature?| |F|M|T|1389620491621| |bram|Technical implementation details. Did you provide enough details for other developers to add or extend on your work?| |FT|M|T|1389620524789| |bram1412336325525|antoinesnyers|Configuration. Did you describe which aspects of your contribution can be configured and where configuration happens?| |F|M|T|1389620576924| |bram|Template text cleanup. Have you removed the template text that was initially included on this page?| |T|M|T|1389620841679|1407497211523|bram|Installation details. If your functionality will not be enabled by default in DSpace, provide details on how the functionality can be installed or enabled.| |
...
This will iterate over every solr record currently in use, query the ORCID web service for the latest data and update the information in the cache. If configured, the script will also update the metadata of the items in the repository where applicable.
Configuration
...
In the Enabling the ORCID authority control section, you have been told to add this block of configuration.
...
Changes to the configuration always require a server restart before they're in effect.
Integration with other systems beside ORCID
The authority cache and look-up functionality can be extended to use other sources than ORCID. However some JAVA development is necessary for this. Specific instructions can be found in the readme file of the org.dspace.authority package.
Overview
Content Tools