Sign up now for Client Certification Foundation Course - June cohort!
Pure's logos
Pure Help Center for Pure Administrators

If you are a researcher, or other non-admin at your institution, click here.

  • Home
  • Announcements
  • Release Notes
  • Technical user guides
  • Training
  • Events
  • Support
  • Contact Us
  • Home
  • Knowledge base articles
  • Data Sources and Integrations

How Can We Help?

Search Results

Filter By Category

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Contact us

Bulk Upload ORCID IDsBulk Upload ORCID IDs

What 

If using the Configurable Person Synchronisation job and later wish to also populate ORCID IDs from the same source, is this possible? 

How 

The easiest way to populate ORCID IDs in a bulk is to use the Pure API or use the Bulk Change IDs on content-job KB-452 

Below describes the pitfalls for start using the Configurable Person Synchronisation job for also populating ORCID IDs in Pure: 

Configurable Person synchronisation SYNC_ONCE or SYNC

'SYNC_ONCE'

  • For a one time bulk population of ORCID IDs on Persons.
  • Only works on not-yet created persons in Pure, not for existing persons.
  • This might not populate ORCID IDs on all persons, as this setting will not update ORCID ID data on Persons already created by the synchronisation job. SYNC_ONCE means the ORCID ID will be imported upon person creation in Pure, hereafter it will not be part of the synchronisation. If the ORCID ID field was empty at the time of the person creation, the field will not be updated later on if the ORCID ID suddenly appears in the source. 

'SYNC'

  • Can be used for adding ORCID IDs on both not-yet created and existing persons.
  • The downside is, that if an existing person already has an ORCID ID on his/her person record pre-running the job, the 'SYNC' will then overwrite any existing ORCID IDs on the persons in Pure - and it might even overwrite with empty values if no ORCID ID in source, so potentially deleting an existing ID in Pure.
  • Another scenario to be aware of, is, if a researcher has authorised ORCID exports and you run the Configurable Person Synchronisation Person job with 'SYNC' ORCID ID field, then the job will overwrite the existing ORCID ID. Deleting or replacing with another ORCID ID the authorisation token is then lost (the token we save is only valid in combination with the ORCID ID). The researcher will need to re-authorise export to ORCID. 

More information

KB-34 How to use the Person ID Import job
KB-452 Bulk change IDs on content 
KB-78 Setting up the ORCID ID on a Person

Published at October 15, 2023

Download
Table of Contents
  1. What
  2. How
Related Articles
  • Synchronisation and employment terminations
  • Check Which WoS Edition Outputs are Imported From
  • Web Service: 524 Endpoint Becomes Persistent
  • ORCID Mapping of subtypes
  • Export to SciVal
Keywords
  • ids
  • synchronisation - configuration
  • 5.18.0
  • synchronisation - data source
  • synchronisation
  • sync once

Was this article helpful?

Yes
No
Give feedback about this article

    About Pure

  • Announcements

    Additional Support

  • Events
  • Client Community
  • Training

    Need Help?

  • Contact Us
  • Submit a Support Case
  • My Cases
  • Linkedin
  • Twitter
  • Facebook
  • Youtube
Elsevier logo Relx logo

Copyright © 2025 Elsevier, except certain content provided by third parties.

  • Terms & Conditions Terms & Conditions
  • Privacy policyPrivacy policy
  • AccesibilityAccesibility
  • Cookie SettingsCookie Settings
  • Log in to Pure Help CenterLog in to Helpjuice Center

Knowledge Base Software powered by Helpjuice

Expand