Appearance
ORCID
needs verificationAn Open Researcher and Contributor ID (ORCID) iD is a persistent researcher identifier, commonly written in the shape 0000-0000-0000-0000. LT uses it to discover a researcher's papers, prove control of an identity through OAuth (an authorization flow), and preserve attribution. The identity-model document describes the intent; current code corroborates the claim-versus-proof split.
Open ORCID to see the researcher-identity service itself. LT uses its sign-in and linking flow to establish control of an identity.
A claim is editable profile data. Login looks up the active social-account link only. It does not auto-link an account by a typed iD or provider email. An unlinked ORCID returns a registration response; linking occurs through an explicit authenticated flow.
Only one account may actively link a given ORCID; linking conflicts are rejected. The proposal also distinguishes claims from proof and describes conflict validation. Treat broader proposed user-interface details as needing verification.
The gate is role-specific
Core requires the creator's linked ORCID for researcher-created Publication and Profile Video. The current configuration does not require it for coordinator-created works. This is narrower than the brief's universal “ORCID required to publish” description.
At publication, Core stores published_orcid_id with the name and OpenAlex attribution. Reassociation can connect retained works to a returning researcher when the previous researcher records are dead or missing, preserving the frozen attribution.
Sandbox and production ORCID are separate environments. Core selects one through ORCID_ENVIRONMENT, with sandbox as its default. Do not assume a sandbox account proves access to production.
For maintainers: source references
These references require repository access. Everything needed to understand this page is explained above.