Open data releases
Every quarter the public datasets of the open data hub are frozen as a release named by year and quarter, for example 2026.4 for October to December 2026. A release never changes: each file keeps its SHA-256 checksum, its row count and its schema version, and earlier releases stay downloadable. Cite a release to let others find exactly the data you used.
Open data hub · Read-only JSON pattern (api.json) · DCAT-AP 3 catalogue with every version
How to cite
Cite the release you used. For the latest release:
Quantum Europe open data, release 2026.4, 2026-10-28, https://odiez-lab.westeurope.cloudapp.azure.com/quantum-europe/open-data/releases/2026.4
Releases have no DOI yet; the release address above is permanent.
Versions
| Release | Generated | Datasets | Files | What changed | Manifest |
|---|---|---|---|---|---|
| 2026.4 | 2026-10-28 | 43 | 57 | First release: 43 datasets. | manifest.json |
How releases work
- A release is built once a quarter from the public downloads of the open data hub, exactly as anyone can download them. Restricted tools and the expert directory are never part of a release.
- The manifest lists every dataset with its rows, SHA-256 checksum, schema version (raised when its fields change), licence and the time it was generated, and the dates of the source snapshots such as OpenAlex and CORDIS.
- The record identifier register gives each organisation and project a portal id that never changes between releases, with ROR, LEI, Wikidata and CORDIS ids where they exist; merged records keep a redirect.
- The read-only JSON pattern pages through a release: records.json takes page, per_page and exact-match filters.