Ed Pentz: relevant content on this site

ORCID Outreach Event at CERN

Ben O'Steen — Thu, 22 Sep 2011 10:23:00 +0000

Program

10:00 Welcome and what’s new – Howard Ratner, ORCID Chair (Slides [PPTX 2.55Mb])

Talk discussed:

Key quote “ORCID will work to support the creation of a permanent, clear and unambiguous record of scholarly communication by enabling reliable attribution of authors and contributors”

Re-statement of the 10 ORCID principles

Various demographics and participant statistics

Illustration of how the Trusted Partners can give more weight to the assertions made in a profile by a researcher by ‘agreeing’ (same_as):

An overview of other researcher ID initiatives and some bullet points on why they feel ORCID is different:

Only not-for-profit contributor identifier initiative dedicated to an open and global service focused on scholarly communication

ORCID is backed by a non-profit organization with over 250 participants behind it

ORCID is backed by many different stakeholders

Publishers are an important ORCID stakeholder but are just one part

ORCID is serious about building an open system

ORCID is the only researcher identifier that is not limited to discipline, institution or geographic area

ORCID is the one to bridge them all by registering the identifiers of all other relevant standalone services (silos big and small)

10:30 What ORCID already does and will do next – Brian Wilson and Geoff Bilder for the Technical Working Group (Slides [PPTX 3.8Mb])

Talk covered:

Development approach, timeline and progress overview

Discussion of the form of ORCIDs as URLs

Overview of what the Query API will provide (non-technical)

Details of the VIVO/ORCID collaboration and code resulting from that.

11:00 Open Q&A on the above

11:30 Cool, but who’s going to pay for that – Craig Van Dyck and Ed Pentz for the Business Working Group (Slides [PPTX 1.19Mb])

Talk covered:

Details of the financial models and projections for the ORCID project

Expected cost to institutions, publishers and funders

$2.75 million required as investment capital (to be paid back after the project breaks even)

13:30 ORCID and me: synergies – Each followed by animated discussion with the audience

ORCID and researchers – Cameron Neylon, STFC

Cameron’s key points were:

Without giving researchers total control over their data and their profile, the system will fail. This includes the power to not list works and co-authorship that the researcher does not want to show.

The most authoritative information you have about a researcher, WILL be from the researcher. Not the institution, not the publisher, but the researcher. It is up to them to specify what is ‘true’ or not.

Researchers wanted three things:

Online profiles that could be used to generate CVs (as maintenance-free as possible) – “It should just know about what articles I publish”

Tracking and aggregation of non-standard outputs in repositories (eg Data, software). This also relates to an identifier being used as a marker that I can use to say “This is a scholarly output for me” even on non-traditional outputs (eg blog posts)

And this is the key. Automating and simplifying grant submissions systems but critically manuscript submission systems. That got clearly the most votes, is probably actually the most tractable and offers the most opportunity for immediate traction with researchers.

ORCID and data – Jan Brase, DataCite (Slides [PPT 0.5Mb])

Provided an overview of DataCite and why it exists (no current convention for citing datasets, attributing impact to them or linking them to the articles which use them)

“DataCite is part of ORCID as ORCID is a community, DataCite is about linking all types of scientific content together, and author identification is one of the key issues”

DataCite search interface: http://search.datacite.org/ui

An example PANGAEA dataset (NB not the one used in presentation unfortunately): http://doi.pangaea.de/10.1594/PANGAEA.733100

ORCID and funding agencies – Carlos Morais-Pires, European Commission (Slides [PDF])

Provided the EU context for FP8, and where ORCID and related efforts may fit within the overall strategy, including overarching figures and funding information.

No questions were raised immediately following this talk, but it did give a very good context to the levels of money that the EU is pushing into this area.

ORCID and your university library – Consol Garcia, Biblioteca del Campus del Baix Llobregat (a Prezi which I cannot find online, may be private)

Provided a good illustration of why the ‘first name, last name’ paradigm falls flat for many cultures and languages.

Asked many questions about what ORCID may do to help libraries but also how it could fit within library practices as they currently stand.

[Ben: Fundamentally, it raised more issues about current library practices and its shortfalls than what a global id for researchers could do]

ORCID and your repository – Najko Jahn, Universität Bielefeld

The presentation gave an overview as to the work they had been doing for the past year or more on their repository. They had already begun to tackle the author disambiguation problem, assigning IDs to authors and so on. Librarians suggest which works to attribute to researchers, and the researchers were able to simply confirm or deny that the work was authored by them. They had done so for approximately 300 of their researchers.

The key question he posed at the end was “What would adopting ORCID do for my repository?” which is a perfectly valid question, given the work they had already undertaken to disambiguate. The discussion was slow, but eventually focussed on the difference in scope – their researcher IDs were locally valid without a widely understood API to query about them, and an international ID system would have a global scope, with effort being made so that the API is as simple but useful as possible.

ORCID and your journal – Brian Hole – Ubiquity Press

Talked about how ORCID may work with a small, independent publisher and what made them different from others (publishing by researchers, for researchers)

ORCID Executive Update (Sept 11)

Ben O'Steen — Thu, 22 Sep 2011 06:50:00 +0000

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 http://www.youtube.com/watch?v=yhrbmUbF0IE - 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

Money:

(much of the following is taken from Ed Pentz’s powerpoint presentation: http://orcid.org/sites/default/files/bwgsep11.pptx 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 http://www.dataliberation.org/)
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.