Zenodo Archival Workflow
SynDB reserves manuscript reproducibility DOIs through a hosted Zenodo OAuth
integration owned by the API service. Personal access tokens are not supported
for this workflow. The window-v2 upload to draft 20692792 is an operator step
with a personal token: see just ms-zenodo-upload in
evidence recapture. The browser UI and syndb article archive ... CLI both call
the same SynDB API endpoints; Zenodo access and refresh tokens never leave the
API process.
OAuth Application
Register the OAuth application in production Zenodo with these values:
| Field | Value |
|---|---|
| Application name | SynDB Archival Depositor |
| Description | OAuth integration used by SynDB to create archival reproducibility deposits and reserve manuscript DOIs. |
| Homepage | https://github.com/memorycircuits/SynDB |
| Production API redirect URL | https://api.syndb.xyz/v1/archive/zenodo/oauth/callback |
| Local API redirect URL | http://localhost:8080/v1/archive/zenodo/oauth/callback |
| Future UI callback URL, if the UI terminates OAuth directly | https://app.syndb.xyz/oauth/zenodo/callback |
| OAuth scopes | deposit:write deposit:actions |
The hosted implementation uses the API callback. The legacy localhost callback URLs are only relevant for direct-Zenodo emergency tooling and are not the default workflow.
API Configuration
Configure the API service with:
ZENODO_CLIENT_ID=<Zenodo OAuth app client id>
ZENODO_CLIENT_SECRET=<Zenodo OAuth app client secret>
ZENODO_OAUTH_AUTH_URL=https://zenodo.org/oauth/authorize
ZENODO_OAUTH_TOKEN_URL=https://zenodo.org/oauth/token
ZENODO_API_BASE_URL=https://zenodo.org/api
FERNET_KEYS='["<fernet key>", "..."]'
Zenodo tokens are encrypted at rest in the zenodo_connection table using the
existing FERNET_KEYS configuration. Status responses redact tokens and client
secrets.
Hosted Admin Workflow
Open the admin UI:
/admin/archive/zenodo/
Use a superuser web session or an operator service account. The page can connect Zenodo, create or update the manuscript reproducibility draft, reserve the DOI, upload a bundle, and publish only after explicit confirmation.
The API routes live under:
/v1/archive/zenodo
Draft DOI Reservation
The CLI calls the hosted API by default:
syndb article archive deposition prepare \
--manifest article/reproducibility/ARCHIVE_MANIFEST.md
Reserve a DOI without publishing:
syndb article archive deposition reserve-doi --draft
The reserve command updates article/sections/back_matter.tex and
article/reproducibility/ARCHIVE_MANIFEST.md only after the hosted API returns a
real Zenodo DOI. The deposition remains an unpublished Zenodo draft until
explicitly published.
Upload And Publish
Upload the exact archive bundle after it has been created from
ARCHIVE_MANIFEST.md:
syndb article archive deposition upload-bundle \
--bundle path/to/syndb-reproducibility-bundle.zip
Publication is irreversible on Zenodo and requires an explicit safety flag:
syndb article archive deposition publish --confirm-publish
Use syndb article archive status to print the registered OAuth parameters,
hosted connection state, deposition ID, draft URL, DOI, and publication status.