[EP-tech] ORCID Support Advance Update
Tomasz.Neugebauer at concordia.ca
Wed Aug 1 17:50:37 BST 2018
Hi everyone who has installed the ORCID Support Advance plugin, Will…
I am still looking to get a clearer picture of what I can expect to happen when I install the ORCID Support Advance plugin on top of the ORCID Support plugin that we currently have working.
What will happen to the ORCID ID’s that we have already collected in the author field of publications?
The description from Will below about ORCIDs from a DOI import says this:
“, the ORCID field uses the creator/editor 'Email' column to lookup user profiles in the repository that have connected to orcid.org so that the creator/editor ORCID field can be verified. As such any ORCID added via a DOI import, might then be erased if the user profile lookup cannot be made. “
Does the above also apply to any ORCIDs that we have been collecting using the ORCID Support plugin?
I don’t think that our depositors have been diligently filling in the email column in the author field during the deposit process, does that mean that the user profile lookup will fail and the ORCID will be deleted for any author that doesn’t have an email listed in the author column?
When does this deletion happen, during indexing? Is there any way to prevent it from happening?
Thanks so much for any insight or advice on this is really appreciated.
From: eprints-tech-bounces at ecs.soton.ac.uk <eprints-tech-bounces at ecs.soton.ac.uk> On Behalf Of Will Fyson
Sent: July 11, 2018 10:16 AM
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] ORCID Support Advance Update
A couple of minor updates have been applied to the ORCID Support Advance plugin, bringing it up to version 1.3.2.
The updates are only very minor, fixing issues where the plugin was generating a few too many messages in the indexer and error logs. A Change Log documenting these most recent changes is available at https://wiki.eprints.org/w/ORCID_Support
Regarding the discussion a couple of emails above in the EP-Tech list ("Import by DOI in ORCID plugin"), a new DOI imported that takes ORCIDs into account is not available at present. Due to the requirements that the ORCID field must be readonly when connected to the member API so that ORCIDs can only be added via an authoritative source, the ORCID field that is added to the creator/editor tables cannot be edited. Therefore to stop values from being entered, which then later cannot be removed, the ORCID field uses the creator/editor 'Email' column to lookup user profiles in the repository that have connected to orcid.org so that the creator/editor ORCID field can be verified. As such any ORCID added via a DOI import, might then be erased if the user profile lookup cannot be made.
This is an issue we're looking into resolving however and so hopefully we should have some updates on it in the future!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Eprints-tech