• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Connecting Researchers and Research

Sign in/Register
  • About
        • Our Mission
          • 2025 Vision
          • ORCID Trust
          • Annual Reports
        • Team
          • ORCID Board
          • ORCID Team
          • Work with Us!
        • Services
          • Member Portal
          • Annual data files
          • Member API
          • Public API
          • ORCID Registry
        • Governance
          • Bylaws
          • Board Elections
        • Policies
          • Privacy Policy
          • Dispute Procedures
          • Public Client Terms of Service
          • Open Source Project License
          • Public Data File Use Policy
          • Terms of Use
          • Brand Guidelines
  • For Researchers
        • Benefits for Researchers
        • Researcher FAQ
        • Video Tutorials
        • Sign in / Register
        • Get Help
  • Membership
        • Membership Benefits
          • Benefits for Funders
          • Benefits for Publishers
          • Benefits for Research Organizations
          • Benefits for Research Resources
        • Get Membership
        • Member List
        • ORCID Map
        • Membership Comparison
          • Basic Membership
          • Premium Membership
          • ORCID Consortia
        • ORCID Consortia
          • Consortia Agreement
          • Consortia Onboarding Checklist
          • Roles and Responsibilities of ORCID Consortia
  • Documentation
        • Features
          • Member Portal
          • Member API
          • Public API
          • ORCID Registry
          • Annual Data Files
        • Workflows
          • Journal Articles
          • Employment
          • Peer Review
          • Funder and Grants
          • View More
        • Integration Guide
          • Getting Started with Your Integration
          • Sandbox Testing Server
          • Registering a Member API Client
          • Integration and API FAQ
          • View More
        • API Tutorials
          • Get an Authenticated ORCID iD
          • Read Data on a Record
          • Add and Update Data on an ORCID record
          • Hands On with the ORCID API
          • View More
  • Resources
        • ORCID Community
        • Community Programs
          • Certified Service Providers
          • ORCID API Users Group
          • Historical Task Forces, Working Groups, and Steering Groups
        • Get Involved
          • Community Groups
          • Developers
          • Give Feedback
          • ORCID API Users Group
        • Member Resources
          • ORCID Enabled Systems
          • Publishers Open Letter
          • Funders Open Letter
          • Standard Member Agreement
          • Outreach Resources
          • Register a Sandbox API Client
          • Register a Production API Client
  • News & Events
        • News
          • ORCID News
          • Member News
          • Consortia News
          • Integration News
          • Blog
          • Release Notes
        • Events
          • Events Calendar
          • Webinars

Scaling Up: Easier ORCID iD Authentication for Everyone

December 4, 2018 By Matthew Buys

At its core, ORCID enables researchers to make connections between themselves (via their ORCID iD) and their activities and affiliations (via other identifiers and APIs).  These connections are asserted either by the researcher or, with their permission, by ORCID members.

Ensuring that researchers have control over their iD and the information connected to it is one of our core principles. To fully wield that control, researchers must be able to understand both what information has been asserted and who has made the assertion. Making this information transparent also helps build trust in iD-ID connections.

Assertion Anatomy

While assertions might seem straightforward, things can get complicated quickly. We care about three relationships in an assertion:  

  • Item origin – whoever published the activity or is the affiliated party  
  • Assertion origin – whoever collects the ORCID iD and makes the connection to an item
  • Source – whoever adds the information to the researcher’s ORCID record  

The “who” in these sources may be the same or different.  For example, a researcher can manually add something to their record, they can use a Search and Link Wizard, or they can give permission to a member to update their record.  At present, there’s no way of telling which of these three pathways were used to connect information to an ORCID record.

We think it is important to change that.  Doing so will both make it possible for researchers to request updates to incorrect information (such as a name misspelling), and for the consumers (such as universities, funders, publishers, and researchers) to make informed decisions about what information to re-use.

Engaging our Community

To explore methods for articulating assertions, we are launching Research Information Platform Engagement (RIPEN). The RIPEN program will allow us to test a technological approach to clarifying  the provenance of information on ORCID records, using JSON Web tokens (JWTs) to reduce the technical burden of integrating authenticated ORCID iDs into workflows. RIPEN brings together a number of projects and themes we have been working on since our launch, including researcher control, authentication, and auto-updates.

Our overarching goals for the RIPEN program are to:

  • Test our implementation. Ensure that our technology and messaging are easily understandable and meet community requirements
  • Improve data quality and trust. A primary goal is to improve trust in iD-ID connections, by ensuring adherence to ORCID best practices for authentication and assertion assurance
  • Broaden reach. Expand the community that can interact with ORCID technology by reducing technical development cost and barriers to implementation

Step-wise Approach

We will be rolling out the RIPEN program in three stages.  In the spirit of eating our own dog food, the first partner implementer is … ORCID!  We will be testing out JWTs (pronounced “jots”) in our own systems, using them to collect authenticated iDs from staff, board and working group members, to delegate user permissions between our app for collecting iDs and our SalesForce CRM system, and to update ORCID records with affiliation assertions into ORCID records.  Another key part of the program is to collect data on the time and cost of implementing this technology compared with using our current three-legged OAuth methodology.  

We are starting our work now, and expect to share more about our progress around March 2019.  We are in the process of recruiting partners for Stage 2, which we anticipate launching early in 2019.   We will decide whether to move on to Stage 3 after evaluating the program in discussion with our Board, tentatively at their October 2019 meeting.

Stay tuned for more!

Related Posts and Pages

  • Assertion Assurance Pathways: What Are They and Why Do They Matter?
  • What’s So Special About Signing In? 
  • The Importance of Opt-In
  • ORCID Principles  
Blog

Filed Under: News, Release Notes

Primary Sidebar

Search

Sign up for blog updates

We will only use your email to notify you when we have new blog posts. You can unsubscribe at any time. See our Privacy Policy for more information.

Check your inbox or spam folder to confirm your subscription.

Recent Posts

  • 2020: A Look Back As We Venture Forward
  • New Integration – GIST
  • New Integration – University of Victoria
  • New Integration – Vidatum Technologies
  • New Integration – Mendel University in Brno

Blog Posts by Category

  • Consortia News (39)
  • Integration News (48)
  • Member News (30)
  • News (429)
  • ORCID News (192)
  • Release Notes (74)
ORCID logo

CC0 The text of this website is published under a CC0 license Images and marks are subject to copyright and trademark protection.

  • About ORCID
  • Privacy Policy
  • Terms of Use
  • Accessibility Statement
  • Contact us
  • Dispute procedures
  • Brand Guidelines
ORCID uses cookies to improve your experience and to help us understand how you use our websites. Learn more about how we use cookies. Dismiss