Re: [jats-list] ORCID ID Tagging and Best Practices

Subject: Re: [jats-list] ORCID ID Tagging and Best Practices
From: Nikos Markantonatos <nikos@xxxxxxxxxx>
Date: Thu, 18 Apr 2013 20:05:01 +0300
Dear Kevin,

You can possibly use a <uri> or an <ext-link> inside each <contrib> containing the ORCID ID, for example:

<contrib-group>
<contrib>
<name><surname>Fauller</surname>
<given-names>Betty Lou</given-names>
</name>
<degrees>BA, MA</degrees>
<uri content-type="orcid" xlink:href="http://orcid.org/1792-3336-9172-961X"/>
</contrib>
</contrib-group>


Regards,
Nikos Markantonatos
Atypon


On 04/18/2013 07:56 PM, techlist wrote:
Dear JATS List,

Recently we have been researching if there is a common practice for
adding ORCID IDs to earlier versions of the NLM DTDs (and specifically,
for Journal Publishing v2.3 and v3.0) for those publishers who do not
yet wish to migrate their content to JATS.

The online documentation for Journal Publishing Tag Library/NISO JATS
Version 1.0 shows <contrib-id>, with the definition being:

"One identifier for a person such as a contributor or principal
investigator. This element will hold an ORCID, a trusted publisher's
identifier, a JST (Japanese Science and Technology Agency) identifier,
or an NII (National Individual Identifier)."

And with an example using @contrib-id-type="orcid":

...
<contrib-group>
<contrib>
<contrib-id
contrib-id-type="orcid">http://orcid.org/1792-3336-9172-961X</contrib-id

<name><surname>Fauller</surname>
<given-names>Betty Lou</given-names>
</name>
<degrees>BA, MA</degrees>
</contrib>
</contrib-group>
...

Because <contrib-id> is not contained in the Journal Publishing v2.3 and
v3.0 tag sets, would anyone be able to suggest a best practice tagging
example for either of these cases?


With regards,


Kevin Lawson,
Publishing Technology SP
Dartmouth Journal Services



--
Confidentiality Notice: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication by someone other than the intended recipient is prohibited.


Current Thread