About
Zenodo as a publication provider of dataset: deposits a hub's datasets and gets their DOIs (the sandbox outside production)
Provides
Services
ZenodoProviderZenodoService
Routes
/zenodo/test
Configuration
| Setting | Default | What it does |
|---|---|---|
ZENODO_ACCESS_TOKEN |
Required | A personal access token of the account that owns the hub's records, with the deposit:write and deposit:actions scopes. Create it under Applications on zenodo.org for production, and on sandbox.zenodo.org anywhere else: the two sites have separate accounts and tokens. Without one nothing is sent. Has no default, so the product must set a value. |
ZENODO_API_URL |
empty | The deposition API. Empty means https://zenodo.org/api/deposit/depositions in production, which ZENODO_ALLOW_PRODUCTION must still allow, and the sandbox, sandbox.zenodo.org, anywhere else. |
ZENODO_ALLOW_PRODUCTION |
false
|
Calls to zenodo.org are refused unless this is true, in production too: its DOIs are permanent, and a test run once minted three. Set it in the .env of the one deployment that publishes the hub's real records, not in a product's [tool.splent.config], which every build reads: product:build makes each deploy a production one, a staging server's included, so the profile cannot tell them apart. |
ZENODO_CONNECT_TIMEOUT |
5
|
Seconds to wait for Zenodo to accept a connection. |
ZENODO_READ_TIMEOUT |
30
|
Seconds to wait for Zenodo's answer to any call but the upload. Each timeout bounds one call, and a publication makes several inside the user's request: with these defaults close to four minutes, retries aside, which a 120 s gunicorn or nginx cuts short (see the README). |
ZENODO_UPLOAD_TIMEOUT |
90
|
Seconds to wait for Zenodo's answer once the ZIP is sent. Zenodo checks the file before it answers, so this grows with the largest dataset. |
ZENODO_MAX_RETRIES |
2
|
Times a read, an update or a delete is sent again after a connection failure or a 429, 502, 503 or 504. A create, an upload or a publish never is, since a second one would make a second deposition, file or DOI. |
ZENODO_KEYWORDS |
empty | Keywords every deposit gets after the dataset's own tags, for example the hub's name so its records can be found together. None by default. |
ZENODO_COMMUNITY |
empty | The identifier of a Zenodo community each deposit asks to join, such as the hub's own. The community's curators accept or decline each request. Empty asks to join none (D22: whether uvlhub has one is its owner's call). |
ZENODO_ACCESS_RIGHT |
open
|
open, or closed for records whose files only their owner sees on Zenodo. |
These are the defaults. A product changes them in its own pyproject.toml, under [tool.splent.config], or in .env.deploy in production.
Dependencies
In product lines
-
openhubs_spl
In a group
One or more of the publicacion group, when a product takes that group
Needs
authdataset
Extension points
Services
ZenodoProviderZenodoService
Routes
A refinement can add routes to its blueprint
Other features fill its hook slots. A refinement can override its templates and services or extend its models without forking it.
Compatibility
Python
>=3.13
SPLENT framework
>=1.30.0
Python packages
requests>=2.33,<3