• The answer to this question depends on your integration plans and what systems you are using. You can get an idea of what is required for different systems by checking the ORCID workflows.
• If you are using a third-party system, it may already support ORCID, in which case you will need only ask the vendor to enable ORCID functionality and provide your ORCID member API production credential. To register for production credentials for a third party system, complete this form. If you are using a vendor product that does not support ORCID, call your product representative and ask them about their plans for ORCID integration.
• If you are using homegrown systems, you will need staff who understand APIs, XML (or JSON), and OAuth, and can read technical documentation. You will also need a detailed workflow plan for where to add ORCID fields, where you will be collecting ORCIDs from your researchers, and a means to securely store access tokens collected during the OAuth process.
• The ORCID US Community provides tier 1 technical support, and ORCID has a support desk as well as technical documentation online, and an API users listserv. The ORCID US Community “ORCID API Basics & Benefits” webinar recording is also a good place to start.

System requirements vary depending on what type of system you want to integrate with ORCID. See ORCID integration workflows for system setup information.

Consult the ORCID US Planning Guide for assistance on factors to consider before beginning the technical integration process. When you're ready to begin technical work, follow the instructions on ORCID's Getting Started guide.

The ORCID API (application programming interface) provides the mechanism by which ORCID iD record data (name, email, education, employment, funding, works) is read, written, updated, and shared between systems. Learn more about the ORCID API.

Not necessarily, but in order for your integration to reap the benefits of ORCID, individuals will need to create and use their ORCID iD. Outreach to individual researchers can take place before, during, and after the technical integration process.

It is possible to customize the interface that individuals will see when they are asked to grant permission for an institution to connect with their ORCID iD record. Learn how.

Learn how to search data in the ORCID registry using the ORCID API.

Once a system is configured to communicate with the ORCID registry via the ORCID API, queries can be run on any of the data contained within affiliated ORCID records, depending on what data you're hoping to collect. Note that institutions must ask individuals to connect with their ORCID iD records, and individuals must set their ORCID record permissions to "public" or "trusted party" for data to be collected. ORCID member organizations have access to on-demand reporting through the ORCID Member Portal.

Webhooks can be used in order for local systems to receive notifications any time data on an ORCID record is updated or changed, which makes it easier to keep data in sync. Learn how to register webhooks.

No. Individuals must register for their own ORCID iD and opt-in to sharing their ORCID iD record data. Institutions no longer have the ability to batch-create iDs for individuals. It is strongly recommended to not create or submit ORCID iD data on behalf of another person. Learn more.

The individual researcher has full control over the visibility of the data in their ORCID record, and the privacy of their ORCID iD record. Learn more about ORCID trust.

ORCID records can contain biographical information, employment and education history and other affiliations, funding received, works, peer review activity, and research resources used. See more details about the types of data in ORCID records.

No, ORCID does not collect demographic data. ORCID does NOT collect or store other identifying or sensitive information such as date of birth, gender, credit card numbers or other financial information, medical information, physical address, phone numbers, social security numbers, passport, or national identity numbers. There are no fields in the ORCID data structure to hold any of this information. ORCID understands that collecting this kind of data is common in the US, but other countries specifically do not collect personal data as a way of supporting diversity, equity, and inclusion. Learn more.

Many research institutions in the US are already part of the ORCID Institutional account login option, thanks to eduGAIN and the InCommon Federation. When signing in to an ORCID record, users can select "Institutional account," type in the name of their institution, and login using their institutional credentials. Learn more about Single Sign-on.

See how to find ORCID record holders at your institution or contact orcidus@lyrasis.org for more info.

Yes, individuals may create more than one ORCID iD record if they wish to use different names for different works, such as a pseudonym or stage name. ORCID also has a straightforward way to manage duplicate iDs and merge more than one record together.

Duplicate data entries are managed based on the presence of an identifier, such as a DOI for publication data. Entries containing the same identifier are automatically grouped together, and the individual may select which entry is the "preferred source." If a duplicate entry does not contain an identifier, both entries will appear as duplicates. The works section of ORCID is the only section in which duplicates are automatically grouped in this way.

This is not recommended. Manual or copy/paste entry leaves room for error and does not provide trustworthy data. ORCID strongly recommends gathering authenticated ORCID iDs by requiring an individual to sign in to their ORCID iD record. Learn more.

See the ORCID US Membership page.

Any non-profit research institution in the United States may join. See the ORCID US Membership page for details.

If your institution is not yet ready to become an ORCID member, it is never too early to promote awareness of the benefits of ORCID iDs for individuals:

• Use the ORCID Outreach Resources to promote anticipation, action, and awareness of ORCID
• Use the ORCID US Outreach Planning Guide to get more ideas for outreach strategies
• Learn how to partner with internal stakeholders to gain value from ORCID
• Teach researchers how ORCID can work for them
• Teach researchers how to link their ORCID iDs with existing integrations like CrossRef and DataCite
• Look into third-party systems that have already integrated ORCID – if the vendor you use is not yet integrated, ask them to!