validating ORCIDs

[Emanuil Tolev]

Hi all!

I'm working on a prototype service whose idea is to try to identify what kind of identifier a string might be. (e.g. what's 0000-0001-8790-101X :))

Is there a particular format that ORCIDs follow? A checksum digit?

I currently do a regex-based test just to see what the string "looks like" and then make an API call to a service associated with that ID (if one exists). So if I can ascertain that an incoming string loosely looks like an ORCID ("it could be" an ORCID) I'll probably register a small client app and have it GET pub.orcid.org/<orcid> . If that tries to give me data and says HTTP 200 OK, then the incoming string is a valid ORCID (and is possibly other types of ID as well, but that's for me to worry about).

(You can see some examples of other IDs at http://idfind.cottagelabs.com/browse .)

Thanks!
Emanuil Tolev
Associate
Cottage Labs LLP
http://www.cottagelabs.com
Twitter: @cottagelabs

[Peters, Robert]

Hi Emanuil,

Thanks for asking. Yes, you could also add in a checksum check:
http://support.orcid.org/knowledgebase/articles/116780-structure-of-the-orcid-identifier

Cheers,

Rob

--
You received this message because you are subscribed to the Google Groups "ORCID API Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orcid-api-use...@googlegroups.com.
To post to this group, send email to orcid-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/orcid-api-users.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Robert Peters

Lead Developer at ORCID.org

Cellphone: +1.805.440.9056

Email: r.pe...@orcid.org

Skype: rcpeters

Timezone: PST