Skip to Content

ORCID Executive Update (Sept 11)

ORCID in a nutshell (current strategy):

  • ORCID is a registry of profiles for people involved in research – a profile can be created by the person themselves (self-registry) or by what is termed a Trusted Partner, such as a University or Publisher.
  • The people using the system decide who is and is not a researcher, not the system itself.
  • A self-registered profile, for “John Smith” for example, can state that it is the same ‘John Smith’ in a profile created by a Trusted Partner and vice-versa. (akin to the semantic web’s “sameAs”)
  • Profiles which are linked like this in both directions (researcher to trusted partner and back again) are trusted more than a profile without such verifying claims.
  • Profile data can have varying levels of privacy: fields can be made public (anyone can see the data), protected (only those that a researcher authorises can see the data) or private (only the researcher can see it). It is expected that when profiles are linked in the above manner, the researcher’s privacy settings will cover the data submitted by the other parties too (but this mechanism is by no means confirmed or implemented yet.)
  • A researcher will be able to authorise other parties to access their protected data using a scheme called OAuth. This is a simple process for the user, and requires little to be remembered on their part. An example Twitter OAuth authorisation can be seen in the first 30 seconds of - blink and you’ll miss it.
  • The main selling point for the system at this time is that it is attempting to save a researcher’s time spent filling in publisher and funder forms for article and bid submissions by having the pertinent details automatically drawn from their ORCID profile (once the publisher/funder’s system has been authorised via the aforementioned OAuth)
  • The later selling point, when a tipping point of signed up users is reached, is expected to be for the universities, funders and publishers. The ability to draw up an REF return or to see which publications have been made as a result of which project funding is an expected feature.
  • It is expected that usable ORCIDs will be assigned from Q2 2012


(much of the following is taken from Ed Pentz’s powerpoint presentation: WARNING: new Powerpoint required to view.)

  • Current projections suggest that the ORCID system will require operating costs of around $2.1 million a year for the next few years.
  • The organisation has approximately 6 months left of funding capital left to work with and is on a funding drive at this moment.
  • It is looking to follow in other CrossRef project’s footsteps by asking publishers and the like for loans – it projects that it will reach the break-even point in 5 to 6 years.
  • No researcher is going to pay for access to the service to create and use a profile and its ID.
  • The Trusted Partners are expected to pay – what the value-added services might be for these parties are still in discussion.
    • The 5 to 6 years break-even point is based on what seems to be a conservative uptake by these parties – however, the system still needs to be sold to them! The following figures are extremely preliminary (tiering is based on number of people/size of organisation):
[Ben: Just repeating - these figures are pre- pre- pre-alpha and subject to change at the drop of a hat. In fact, I'd bet that they already have]

Things yet to be dealt with (my opinion):

  • Whilst no-one has stated a problem with ORCID’s software being Open Source, it has yet to be released as an Open Source Project. The code base that they are working on, IP belonging to Thomson-Reuters, has been scrubbed of any Thomson-Reuters specific code and they (T-R) have agree that it is suitable to be placed under an OSI licence. It just hasn’t been done yet.
  • The ORCID software release was planned to be just a deployable .war file – without source code. This obviously is not acceptable if the O in ORCID is to remain to stand for Open (in spirit if not pedantically.)
  • How privacy is to be handled with multiple parties asserting various pieces of information is not yet decided or agreed upon. This type of functionality is quite a deal-breaker for many academics.
  • How malicious or false claims are going to be dealt with, at a policy level, has not been clear. What level of recourse will an individual have against false claims made (mistakenly) by a trusted partner and vice-versa? Researchers making multiple accounts? Profiles made by bored teenagers for ‘fun’?
  • There is still a short-term gap of investment funding required of $2.75 million dollars – it remains to be seen what occurs if the code is still not made open source by the end of six months if no other sources of capital is found.
  • Whilst other identifier schemes can be easily included within an ORCID profile, it is not clear if – at an organisational level – if they would be happy if another organisation used the ORCID code to set up another ‘ORCID’ system. Due to the timeline of when ORCID might go live (Q2 2012), the urgency with which other organisations require them might force other systems to be put into place much earlier. For example, as Andrew Treloar jokingly quoted on the ORCID outreach event’s live chat: “If you guys have an ORC-ID, then I want an ELF-ID” – could the next ORCID-free six months force some funders to take matters into their own hands?
  • ORCID exit-strategies – both for the organisation and for individual profiles. What happens when the money runs out? What happens to the data? If someone wanted ‘out’, is there a way for them to remove all their data and take it with them? (in a similar vein to
  • The authorisation system relies on OAuth (which is no bad thing) but I don’t think that the time required for existing organisation to adopt this has been adequately estimated. ORCIDs use on other systems to save time and effort filling in forms is a crucial part of the ‘sales pitch’ to academics – this hasn’t gotten the visible focus I would’ve expected.

Dr. Radut | blog_post_tf