Repository navigation
Spec 031: ORCID "Claim your work" on the node content service - #996
Open
adamjohnwright wants to merge 1 commit into
Open
adamjohnwright wants to merge 1 commit into
adamjohnwright wants to merge 1 commit into
Conversation
The spec, plan and tasks for porting the old website's ORCID module to the node content service, as decided on 16 Nov 2026: node only, never Java; built against a stub ORCID, then ORCID's sandbox on the test site; production later. - spec.md: five stories, FR-001 to FR-031, three open questions for the maintainer (revocation at sign-out, the sandbox Person, where claim records go), each with a recommendation. - contracts/endpoints.md: the eleven old endpoints against the new, one by one; the claims keep their paths, body and answer. - contracts/orcid-works.md, checks.md (C1-C27, each with its breakage), research.md (R1-R13), data-model.md, quickstart.md, tasks.md (T001-T028). - The register of declared differences gains the ORCID section (12 rows, spec only) and the three open decisions; spec 006's T110 points here. No implementation code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The spec, plan and tasks for porting ORCID "Claim your work" to the node content service, as decided on 16 Nov 2026: keep the feature, port it to node (never Java, no Java fallback), build and test against a stub ORCID, then ORCID's Sandbox Member API on the test site. Production credentials and switching production are out of scope. No implementation code.
Replaces spec 006's T110 (#114), which now points here. Adds the ORCID section (12 rows, spec only) and three open decisions to
documentation/declared-differences.md.specs/031-orcid-claim/spec.md: five stories, FR-001 to FR-031, three open questionscontracts/endpoints.md: each old endpoint against the newcontracts/orcid-works.md: what is sent to ORCID (Member API v3.0)contracts/checks.md: C1 to C27, each with the breakage that must turn it redresearch.md(R1 to R13),data-model.md,quickstart.md,tasks.md(T001 to T028)Endpoints
/orcid/loginstate(and PKCE if ORCID checks it), redirect URI from settings, optional?return=(site paths only)/orcid/callbackand/content/orcid/callbackstate, exchanges the code on the server, new session, 302 to/orcid-callback?outcome=…; never passes on the code/orcid/token/orcid/signoutsuccess/orcid/authenticated{enabled, signedIn, orcid?, name?}/orcid/claim/{all,pa,pr,ra,rr}ClaimingSummary; ≤100 works per ORCID call; statuses 401/403/404/409/502/504/orcid/{orcid}/worksOrcidWork[]/orcid/let-us-know-your-orcid{title, subject, message}, no token, no captcha keyTokens live only in the service's memory behind an opaque
HttpOnlycookie (30 minutes idle, 8 hours at most). There is no token, code, secret, iD or name in any answer, log or file. The feature is on only when its settings are complete, and ORCID's production servers are refused without an explicit switch. No test ever reaches ORCID.Open questions for the maintainer
ORCID_TEST_PERSON=<sandbox iD>:<dbId>) in the host's private settings, honoured only with the stub or sandbox, naming a Person whose owner agrees.report.tsalready reports searches. Claims only, never a token, and no sign-in record.Redirect URIs to register on the sandbox client (placeholders):
https://<test-site>/content/orcid/callback,https://<test-site>/ContentService/orcid/callback, and the same two underhttp://localhost:<port>.🤖 Generated with Claude Code