eLife supports ORCID IDs for authors. Erudit supports 3 other author IDs too: isni, researchid, scopus.
User Stories
Author
[ ] As an author, I want to be able to see which, if any, ORCID ID has been associated with an author name so that I can check this information is correct.
Production staff
[ ] As production staff, I want to be able to see where an ORCID associated with an author goes so that I can check that correct page is linked.
[ ] As production staff, I want to be able to remove an ORCID ID from an author so that I can remove errors in ORCID attribution.
[ ] As production staff I need to be able to see whether an ORCID is authenticated so I can ensure the correct information is passed on to the downstream processes.
Erudit/PKP/SciELO
[ ] As QC staff, I want to be able to check which IDs have been associated with an author so I can ensure they are correct.
[ ] As QC staff I need to be able to see whether an ORCID is authenticated so I can ensure the correct information is passed on to the downstream processes.
But what if . . . ?
Considerations
The ORCID ID display guidelines ask that the full URL is used, even though the number after https://orcid.org/ is a PID (persistent identifier)
However, we believe for storage the content in the XML should be optimal for reuse and persistence and store only the ID (XXXX-XXXX-XXXX-XXX). For display purposes, it should be formatted with the ORCID url and the logo as defined by their requirements.
Another ORCID display requirement is that their logo appears next to the full URL.
For eLife ORCID IDs for authors will be exported from the previous system when they have been added using an integrated verification/login process, which means they require the additional attribute of @authenticated="true"; for PKP this will be a mixture and for Erudit they will not be. This attribute is required to differentiate.
For eLife additional ORCID IDs should only be added to an article during proofing using an integrated verification/login process - due to validation requirements, production staff will not be able to add IDs manually, which means they require the additional attribute of @authenticated="true"
We need to make sure that ORCID IDs added during proofing are attributed to the author they belong to - in the current proofing system, it’s possible to get an ORCID associated with the wrong author. We do this currently by clicking on the ORCID IDs, which are rendered as hyperlinks to the ORCID pages.
eLife's production vendor should provide the ORCID login interface above Texture.
XML requirements
Should be captured as a <contrib-id>, as a child of <contrib>. All author ids MUST have an @contrib-id-type to identify which ID is being referred to. Accepted @contrib-id-type values are:
orcid
isni
researchid
scopus
Authenticated ORCID IDs require an attribute of: authenticated="true"
NickDuf
commented
5 years ago
eLife supports ORCID IDs for authors. Erudit supports 3 other author IDs too: isni, researchid, scopus.
User Stories
Author
Production staff
Erudit/PKP/SciELO
But what if . . . ?
Considerations
@authenticated="true"; for PKP this will be a mixture and for Erudit they will not be. This attribute is required to differentiate.@authenticated="true"XML requirements
Should be captured as a
<contrib-id>, as a child of<contrib>. All author ids MUST have an@contrib-id-typeto identify which ID is being referred to. Accepted@contrib-id-typevalues are:Authenticated ORCID IDs require an attribute of:
authenticated="true"Taken from: https://github.com/elifesciences/TextureRequirements/issues/10