Elsevier Pure participates in ORCID’s Certified Service Provider program, and its connection to ORCID is one of the most-used integrations in the platform. But “Pure talks to ORCID” is doing a lot of work in that sentence: linking an iD, authorizing an export, and importing publications are three separate mechanisms with different triggers, different schedules, and different failure modes. This guide is scoped specifically to how that connection actually behaves day to day — not to general Pure setup, which is covered in our Pure implementation and data-migration checklist.
Linking is not syncing
Before any data moves in either direction, a researcher has to link their ORCID iD to their Pure profile and explicitly authorize Pure to act on it. This is a standard OAuth-style authorization: the researcher signs in to ORCID and grants Pure permission to read and, separately, to write to their record. ORCID’s own permission model draws a hard line between these — a connected service can be granted read access to trusted-party-visible data and, independently, write access via the /activities/update and /person/update API scopes. Linking the iD alone does not turn on data flow in either direction — a researcher can have a linked iD with exports switched off, or exports on and imports never run, depending on what was authorized and what the institution has configured.
Because this is a genuine permission grant rather than a one-time confirmation, it shows up on the researcher’s own ORCID account too: the institution appears under “Trusted organizations” in the researcher’s ORCID settings for as long as the connection is active.
Auto-export: Pure to ORCID
Once a researcher has authorized Pure to write to their ORCID record, an institution can enable automatic export of that researcher’s Pure content — typically publications and other research output entries visible on their Pure profile — to their linked ORCID record. This is an administrator-level configuration, not a per-researcher one: the Pure administrator sets how often the export job runs, with published support documentation describing options ranging from weekly, daily, monthly, quarterly, or yearly, down to a fully custom schedule, or manual only. A researcher can also trigger a one-off export on demand from their own profile workspace in Pure, without waiting for the next scheduled run — useful right after linking an iD for the first time, or after a correction that shouldn’t sit in the queue until the next cycle.
Several institutions that publish their own Pure-ORCID guidance describe the automatic job running on a daily cycle at a fixed early-morning time once a researcher has authorized it, though the exact cadence is an institutional configuration choice, not a fixed product default — check your own institution’s research office or library guide for the schedule actually in effect, since it varies by deployment.
Auto-import: ORCID to Pure
The reverse direction — pulling publications into Pure from a researcher’s ORCID record — is a separate, deliberately triggered action rather than a background sync. In Pure, this lives under Research Output > Import from Online Source > Import from ORCID, where the linked ORCID iD is used to query the ORCID registry for works already on that researcher’s record. The researcher (or an administrator acting on their behalf) then reviews the returned list and chooses which entries to bring into Pure, rather than every ORCID work being ingested automatically and unconditionally. This matters in practice because ORCID records commonly contain works added by multiple sources — the researcher themselves, a publisher via a trusted-party work assertion, Crossref auto-updates, or another CRIS entirely — and not everything sitting on the ORCID side is necessarily something the institution wants duplicated into its system of record without review.
Why “auto-import” and “auto-export” aren’t symmetrical
It’s worth being explicit about this because the terminology invites the assumption that Pure and ORCID simply mirror each other. They don’t. Export can genuinely run unattended on a schedule once authorized. Import, in the interfaces Pure documents publicly, is a search-and-select action a person initiates — there isn’t an equivalent standing job that silently adds new ORCID works into Pure the moment they appear. An institution that wants publications flowing into Pure from ORCID on an ongoing basis needs a person (researcher or delegate) to periodically run the import step, or to rely on other ingestion sources — Scopus is the more commonly automated publication feed in most Pure deployments — rather than assuming ORCID import behaves the same way export does.
Common troubleshooting issues
Stopping the connection has to happen from ORCID, not Pure
Because the authorization lives on the researcher’s ORCID account as a trusted-organization grant, revoking it is done from ORCID’s side: the researcher removes the institution under “Trusted organizations” in their ORCID account settings. There typically isn’t an equivalent “disable my export” toggle that a researcher can throw from inside Pure itself to the same effect — the permission grant is the thing controlling the flow, and ORCID is where that grant lives.
Duplicate publication records
Because an ORCID record can be populated from several sources at once — Pure’s own export, a publisher’s automated deposit, a researcher’s manual entry, another institutional system — the same publication can land on the ORCID record more than once if the metadata strings (title, journal name, DOI presence or absence) don’t match closely enough for ORCID to treat them as the same work. ORCID provides a “group” or “merge” mechanism for a researcher to consolidate duplicate entries into one grouped work rather than deleting either copy outright.
A deleted work reappears after the next sync
If a researcher deletes a work from their ORCID record that originated from Pure, and Pure’s automatic export is still running on schedule, the next export cycle can add that same work back — because from Pure’s side, nothing changed about the underlying Pure record that would tell it the export should stop. The more durable fix for “I don’t want this visible on ORCID” is usually to change that work’s visibility setting on the ORCID side (to trusted-parties-only or private) rather than deleting it, since a visibility change persists in a way a deletion followed by another automatic export does not.
Nothing imports or exports even though the iD is linked
The most common cause is an incomplete authorization rather than a broken connection: the iD can be linked for identity/read purposes without the separate write authorization having been granted, or vice versa, and a researcher may not realize these are distinct steps. It’s also worth checking, on the institutional side, whether automatic export is enabled at all for that researcher population — this is an administrator-level setting, discussed from the deployment-policy angle in our Pure implementation checklist — rather than something every linked profile gets by default.
Frequently asked questions
Does Pure automatically import new publications from ORCID?
Not on its own as a standing background job. Pure’s documented ORCID import is a search-the-registry-and-select action run from Research Output > Import from Online Source > Import from ORCID — a person has to initiate it and choose which returned works to bring in. Automatic, unattended flow runs in the export direction (Pure to ORCID), not the import direction.
How often does Pure export to ORCID?
Whatever schedule the institution’s Pure administrator has configured for the automatic export job — published options include weekly, daily, monthly, quarterly, yearly, a custom interval, or manual-only — plus an on-demand one-off export any authorized researcher can trigger themselves at any time from their profile.
Can a researcher stop Pure from writing to their ORCID record?
Yes, by revoking the institution’s access from the “Trusted organizations” section of their own ORCID account settings. That withdraws the permission grant the export relies on; there’s no separate researcher-facing off switch on the Pure side that accomplishes the same thing.
Why do I have two copies of the same publication on my ORCID record?
Almost always because more than one source added it and the metadata didn’t match closely enough for ORCID to recognize them as the same work — a Pure export alongside a publisher deposit or a manual entry is a common combination. ORCID’s merge/group function consolidates these into a single grouped entry.
Is Pure’s ORCID integration officially certified?
Pure has held ORCID integration since 2016 and participates in ORCID’s Certified Service Provider program, which is ORCID’s own assurance that a member’s implementation of import, export, and exposure of researcher data meets its integration requirements.
For the broader deployment context — deciding whether ORCID connection should be mandatory, opt-in, or encouraged for faculty, and where it fits alongside the rest of a Pure rollout — see our Pure implementation and data-migration checklist. For the identifier concepts underlying this integration, see our entries on ORCID iD, ORCID record permissions, the ORCID API, and CRIS interoperability, or our practical walkthroughs on registering and searching ORCID iDs and ORCID profile optimization. If you’re still evaluating CRIS vendors rather than administering an existing Pure deployment, see our Pure vs. Symplectic Elements vs. VIVO vs. DSpace-CRIS comparison.
