On Wed, Jun 17, 2015 at 1:08 PM, Hilton Gibson <hilton.gib...@gmail.com> wrote:
> We are implementing ORCID with our DSpace 5.2 using the XMLUI. > We are not clear what the purpose of the "index-authority" script is? > See: > http://wiki.lib.sun.ac.za/index.php/SUNScholar/Researcher_Identification/5.X/ORCID#Step_5_-_Import_existing_authorities_.28Optional.29 > > Does the DSpace authority record for an eperson have precedence over the > ORCID record? > If I believe that the existing "eperson" records are not accurate and > authoritative, should I run this script? > Hi Hilton, first, authors (the metadata field) or authority identifiers (optionally associated with the metadata field) are currently completely unrelated to epersons (which represent DSpace users). Second, index-authority is a new, built-in implementation of an authority index in DSpace 5 called SolrAuthority, that also happens to associate ORCID IDs with the authority record. What index-authority does is, as the official documentation describes [1], look at all authors in your repository and for each unique author (which is the string of the author's name if you don't already use a different authority implementation) creates a record in the SolrAuthority index. It is meant to be run as a one-off command after you first enable SolrAuthority (should you run it again later, the records will be recreated with different IDs, which is obviously something nobody wants). After that initial run, new records are added using an event consumer. [1] https://wiki.duraspace.org/display/DSDOC5x/ORCID+Integration#ORCIDIntegration-Importingexistingauthors&keepingtheindexuptodate Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
_______________________________________________ Dspace-general mailing list Dspace-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-general
