How Can We Help?
How to Stop ORCID Export on Former PersonsHow to Stop ORCID Export on Former Persons
The ORCID integration can help maintain accurate affiliation data in ORCID and provide flexibility for managing ORCID connections for former and returning employees.
This is valid from Pure 5.34.0, parts from 5.34.2
When leaving the institution (employee gets former)
When an employee leaves the institution, and the affiliation is set to Former, the ORCID authentication for that person is paused automatically, meaning their details and publications will no longer be parsed or updated.
Pure will send a final data push to ORCID to ensure the affiliation end date is properly recorded.
If the person later rejoins the institution, the ORCID authentication will be reinstated automatically.
When revoking permission
Additionally, the person can log into ORCID at any time to Revoke permissions for Pure to export to ORCID
If the ORCID job is to run the final data push on a former employee and the permission has been revoked, the job will throw a warning log (From 5.34.2):
“WARN log: Unable to complete the final ORCID export for this former employee. ORCID access may have been revoked by the user.”
If an Active person on the other hand has revoked permission for Pure to export to ORCID, the job will throw this error log:
“ERROR log: The access token is no longer valid. The user may have revoked access to Pure for a redirect to their ORCID profile. To correct this, the user must reauthorize their ORCID credentials or remove the current ORCID credentials from their profile”
If a former person later rejoins the institution, but the person revoked permission meanwhile, the ORCID authentication will not be reinstated automatically. You will see the above error log.
Follow the recommendations displayed in the error log.
Published at November 21, 2025
