Working together to align the global networkAn independent, community effort to standardize researcher identification

Geoffrey BilderInterim Technical Director, ORCID

Developer Update: 2012ORCID Outreach Meeting15 May 2012

ORCID Phase 1.0Intro to Demo

Who am I?

Laura Paglione

Gorlug Waakop

ORC-IDMiddle Earth DepartmentOf HomeShire Security

Yogi Bear

ORS-IDJellystone National Park

✔Orchid

✘ ✘Pronunciation

Self-AssertedIdentity

http://www.identitywoman.net/the-identity-spectrum#utm_source=feed&utm_medium=feed&utm_campaign=feed

Kaliya Hamlin

Self-AssertedIdentity

Socially-ValidatedIdentity

Socially-ValidatedIdentity

Organisationally-ValidatedIdentity

Organisationally-ValidatedIdentity

Self-AssertedIdentity

Socially-ValidatedIdentity

Organisationally-ValidatedIdentity

Automated-Tools

DisambiguatedIdentity

Socially-ValidatedIdentity

Organisationally-ValidatedIdentity

Phase 2

Self-AssertedIdentity

Phase 1

1.0 1.x

Launch

TIMELINE 2012-13 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3

Build Phase 1.0

Phase 2 Development Build Phase 1.1 Launch Phase 1.0

Phase 1.0 Work Statement

“Thomson Reuters, an ORCID member, has contributed the source code for an existing self‐claim identity system that has been used in a production setting for three years (ResearcherID). There are no restrictions on ORCID’s use of the source code, but the donated code still has several dependencies on proprietary back‐end systems and is also missing several features that ORCID has identified as being essential to the launch of a successful system. Phase one work will consist of replacing proprietary dependencies and implementing these missing features.”

Changes I

• Upgrade and/or replace out‐of‐date library dependencies.

• Replace the existing identifier structure.

• Replace the proprietary authentication/authorization backend.

• Replace the proprietary bibliographic artefact database.

Changes 2• Replace the existing internal service APIs

with a modern, public “restful” API.

• Incorporate OAuth authentication & profile exchange functionality.

• Modify the system’s privacy mechanism to support tertiary control (private/protected/public) at the field level.

• Enable institutional seeding of profile records on behalf of their researchers.

Changes 3

• Modify authentication/authorization mechanism to support “delegated” management of profiles (e.g. a researcher can grant permission to a departmental secretary or librarian to edit a profile on their behalf).

• Include production‐level publication lookup features from CrossRef.

• Expose minimal provenance (i.e. “sponsor”) information for metadata records.

Phase 1.0 Work

Close integration of the ORCID system with third‐party submission and evaluation systems will be vital in order to drive uptake of the service and in order to allow stakeholders to derive immediate benefit from the service. Functionality supported will include:

Functionality

• Institutional seeding of profiles (i.e. batch upload, alerting)

• Delegated management of profiles

• Profile exchange into grant/manuscript submission systems and other identifier/profiling systems

Functionality 2• Fine‐grain control of privacy settings at

the claim level (e.g. public=”share with anybody”, protected=”share with parties authorized via OAuth2”, private=”do not share”)

• ORCID resolution (both via GUI and API)

• Metadata search (both GUI and API based)

Details: Replacements

• Struts2 -> Spring MVC 3.1

• JSP -> Freemarker

• MySQL -> PostgreSQL 9.1

• iBatis -> JPA 2.0 implemented by Hibernate 3.6.3

• Prototype.js -> JQuery 1.7

• Ant -> Maven 3

• XML-RPC -> REST using JAX-RS 1.1 implemented by Jersey 1.12

Details: Additions

• SOLR for searching

• Twitter Bootstrap for styles, layout, and UX

• OAuth2 implemented by Spring Security 3.1

• Spring IOC 3.1 for improved code structure and test coverage

• Liquibase for robust database schema change tracking, migration and rollback

1.1 Hit List• Implementation of the “Callback API”

• Redesign of site UI

• Replacement of boilerplate text, including EULA, Privacy Policy, FAQ, etc. Semantico is building an inventory of these screens.

• Schema changes recommended by privacy committee including removal of physical address elements and addition of patent-claiming

• Privacy model changes recommended by privacy committee

• Implementation of anti-spamming in signup process (Captcha). To prevent bots from registering fake profiles which include links to ads, porn, etc.

• Bibliographic artefact management

• Implementation of availability and system instrumentation monitoring tools (e.g. JMX consoles, Pingdom availability tests, etc.)

• Labelling of "orphaned" profiles.

TIMELINE 2012-13 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013

Start Registering ORCIDs Publicly

Build Phase 1.0

Staff Hired

Initial University Onboarding

Manuscript System Onboarding

Ongoing Ecosystem Integration

Widespread Feedback of ORCIDs Throughout Scholarly Systems

Phase 2 Development Build Phase 1.1 Launch Phase 1.0

And...

Thank YouFind out more at http://about.orcid.org

Sign up for newsletter at http://about.orcid.org/newsletter/subscriptions

Follow @orcid_org on Twitter