Submitted by Robert Peters on Wed, 2018-06-13 00:00
ORCID enables and stores assertions between a researcher’s ORCID iD and identifiers for their activities and affiliations. This post describes the anatomy of assertions and new functionality to enhance transparency and traceability - and ultimately trust - in the assertions stored in the ORCID Registry.
Submitted by Robert Peters on Wed, 2018-03-07 00:00
Our Director of Technology, Rob Peters, shares his thoughts on using blockchain, together with persistent identifiers, to enable reliable connections between researchers and their research outputs beyond just journal articles.
Submitted by Robert Peters on Mon, 2017-02-13 22:18
We are delighted to announce the release of our new API, version 2.0. Find out why it’s needed, how it improves upon the current API (version 1.2), and more in this interview with our Director of Technology, Rob Peters.
Submitted by Robert Peters on Mon, 2016-04-04 00:00
One of ORCID’s core principles is that individuals control their ORCID iD and the information attached to it. ORCID systems are designed so that nothing can be added to an individual’s ORCID record without his/her explicit consent. With an upcoming change to the ORCID API we will be strengthening user control, ensuring that individuals’ default visibility preferences apply to everything in their ORCID record. Read our post to understand how this change may affect you.
Submitted by Robert Peters on Tue, 2015-11-17 00:00
What could be cooler than a Codefest at GitHub? Read on to find out more about what the ORCID development team and other Codefesters got up to at our November Outreach meeting!