• 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

Learning Patience: Taking a Step Back on Affiliation Assertion Requirements

November 6, 2018 By Laure Haak

ORCID is committed to enabling traceable connections between researchers and their activities and affiliations.  This includes using identifiers for things (such as DOIs) and places (such as organization identifiers), as well as people. In many cases, however, identifiers are not yet widely used. In some cases, there is not yet an understanding that identifiers are needed.

When we first launched affiliation functionality in 2013 (see Organizational Affiliations Now Part of ORCID Record), our focus was on organization identifiers.  These made it possible for us to create an organization pick list for researchers to choose from when adding employment and education affiliation information to their ORCID record.  Since then, researchers have used this pick list to make over 5m such assertions, and increasingly their institutions are using the ORCID API to add affiliation information for their own researchers – to date, researchers have given permissions for over 100K such assertions.

However, what about researchers who have more than one affiliation at the same institution, over time or at the same time?  In this case, simply connecting a person’s ORCID ID with an organization ID is not enough. And even with additional role metadata, there is no clear way to resolve the affiliation: to find a web page or other independent digital information for that affiliation.  Some institutions have faculty and staff profile pages, but by and large these pages are removed when a faculty member moves to a new organization. And let’s not even ask about students, who most often don’t have any online representation hosted by their institution.

As part of our push toward trusted assertions (see Assertion Assurance Pathways: What Are They and Why Do They Matter?), we decided that our new API release candidate (3.0) should require affiliation assertions added to an ORCID record by any source to include either a persistent identifier – which we knew was a stretch – or, what we thought was achievable now, an affiliation start date.  Verifying that someone has ever worked at institution X is significantly harder than verifying that they worked at X during a particular time period.

However, thanks to your feedback on our new API release candidate, we now know that, for many in our community, this bar is currently too high. So, by popular request, we are temporarily rolling back the start date/identifier requirement for affiliations in API 3.0. We will be taking time over the next 6-9 months to work with the community to gain a better understanding of your workflows and information sources and to engage with partners to test approaches.  If you are interested in working with us on this project, please contact me.

In the meantime, we will be:

  1. Displaying “date created” for items on the ORCID record and in the API
  2. Requiring organization IDs for the asserting organization and the affiliation itself
  3. Ensuring that only those organizations that have a direct relationship with the affiliation may post it to the ORCID record.  This means that Institution X may ONLY post affiliations pertaining to their institution. We will be managing this using organization IDs for the asserting organization and the affiliation being posted
  4. Encouraging (but not requiring) the use of start dates in affiliation assertions
  5. Encouraging pilot integrations that test use of identifiers for the affiliation
  6. Encouraging inclusion of a local webpage URL (such as a faculty or staff profile) in the affiliation assertion, preferably in an archived format (see e.g., https://www.webcitation.org)

Our Engagement team will be responsible for working with members to ensure these guidelines are communicated, and also adhered to in our Collect & Connect badging processes.

We look forward to working with our community to improve transparency and trust in affiliation assertions. Please contact us if you have questions or suggestions.

Related ORCID posts

  • Assertion Assurance Pathways: What Are They and Why Do They Matter?
  • Building a Robust Research Infrastructure, One PID at a Time
  • New Feature Alert: Upgraded Affiliation Types

1ORCID API Versioning

Blog

Filed Under: News

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