Deposit to Zenodo
Prepare a draft deposit and publish it yourself on Zenodo.
In short
Thesivor can prepare a Zenodo deposit for a frozen paper or proposal, a dataset, the software, or one signed-off figure. It creates a draft and stops — you open Zenodo and publish it yourself. The whole flow has only been tested against a local mock, not the real Zenodo server.
1Add a token
Settings → Zenodo: choose Production or Sandbox and paste a personal access token created with deposit:write only. It is stored in your OS secure storage. The app works without a token.
2Choose what to deposit
Only frozen versions. A paper or proposal version's PDF (plus an optional source .zip), a dataset with a generated README, the software with its lock file, or one signed-off figure.
3Check the file list
The dialog shows the exact files and sizes, and lists what was left out and why. Keys, writing-voice samples and internal record files are never uploaded.
4Save the draft
The app validates the metadata, reserves a DOI, uploads the files with progress and retry, and records the draft in record/zenodo. Then open Zenodo to publish.
For technical users
Endpoints follow Zenodo's legacy deposition API: create with prereserve_doi, upload with PUT {links.bucket}/{filename}, status via retrieve, delete an unpublished draft, and actions/newversion for a later version. The client has no publish method and refuses a URL containing /actions/publish before sending. Errors are shown inline with Zenodo's own message; a 429 waits until X-RateLimit-Reset. Live Zenodo (production or sandbox) is UNVERIFIED — all tests ran against a local mock.