Static view: the interactive graph runs where this page’s scripts and WebGL can; every node is also linked on this page.
Reports · Risk Academy · Open science
Zenodo · ORCID · ROR · DataCite · OpenAIRE
Open science, by default
Every edition and every accepted contribution is deposited openly, identified persistently and described with open metadata, so it can be found, cited, reused and corrected anywhere.
- Repository
- Zenodo
- concept and version DOIs
- Licence
- CC BY 4.0
- metadata CC0
- Standards
- 8 parts
- Nexus Standards applied
A release record, as it will read at deposit.
Release recordA release record: digest, signatures, DOI and the open indexes. Illustrative interface; example values.
Your record, curated into the edition.
Your record, step by step, from deposit to citation.
You keep your own record and DOI; curators accept or decline it into the Reports community in the open, and an accepted record is linked from the edition and indexed.
| Step | What happens | Source |
|---|---|---|
| 01 Deposit your record | Upload your files to Zenodo under your own account and add your ORCID iD; the record and its DOI stay yours. | |
| 02 Describe it | Fill the DataCite fields and add related identifiers, so the record says what it is, who made it and what it relates to. | |
| 03 Choose a route | Submit it to the Reports community, or send its DOI through the Risk Academy gateway (GW-ACADEMY). Either way it reaches the same curators. | |
| 04 Curators decide in the open | Curators accept or decline the request with a reason that stays visible on the request. | |
| 05 Linked and indexed | An accepted record gets a UNI, is linked from the edition as a source or supplement and flows to OpenAIRE and OpenAlex. | |
| 06 Cited with your DOI | The next edition cites the record with its DOI and credits you; a correction to it becomes a new version, never a silent edit. |
A teaching model of the process, not a forecast and not a record of any run; dates and counts on this page come from the programme record. Sources: Reports governance at Risk Academy (2026); Zenodo, repository of record for Reports deposits (2026); DataCite Metadata Schema (2024).
Describe your record once, in every format.
Describe your record once, in every format.
Fill in your record and copy the metadata Zenodo, GitHub and citation managers read: the InvenioRDM REST JSON, the legacy .zenodo.json and a CITATION.cff. Nothing leaves your browser.
A worked example for a dataset. With scripts on, this becomes a form that writes the three files for your own record.
{ "metadata": { "resource_type": { "id": "dataset" }, "title": "Flood exposure of rail assets in the Rhine basin", "publication_date": "2026-10-19", "creators": [ { "person_or_org": { "type": "personal", "family_name": "Doe", "given_name": "Jane", "identifiers": [ { "scheme": "orcid", "identifier": "0000-0002-1825-0097" } ] }, "affiliations": [ { "name": "Example University" } ] } ], "description": "Exposure of rail track and stations to river flooding, with sources and method.", "rights": [ { "id": "cc-by-4.0" } ], "subjects": [ { "subject": "flood" }, { "subject": "rail" }, { "subject": "exposure" } ], "related_identifiers": [ { "identifier": "10.5281/zenodo.0000000", "scheme": "doi", "relation_type": { "id": "issupplementto" } } ], "version": "1.0.0" }, "access": { "record": "public", "files": "public" }, "files": { "enabled": true } }{ "upload_type": "dataset", "title": "Flood exposure of rail assets in the Rhine basin", "creators": [ { "name": "Doe, Jane", "orcid": "0000-0002-1825-0097", "affiliation": "Example University" } ], "description": "Exposure of rail track and stations to river flooding, with sources and method.", "access_right": "open", "license": "cc-by-4.0", "keywords": [ "flood", "rail", "exposure" ], "related_identifiers": [ { "identifier": "10.5281/zenodo.0000000", "relation": "isSupplementTo", "scheme": "doi" } ], "version": "1.0.0", "communities": [ { "identifier": "nexus-reports" } ], "notes": "Contributed through Nexus Reports at Risk Academy." }cff-version: 1.2.0 message: "If you use this work, please cite it as below." title: "Flood exposure of rail assets in the Rhine basin" type: dataset authors: - family-names: "Doe" given-names: "Jane" orcid: "https://orcid.org/0000-0002-1825-0097" affiliation: "Example University" version: "1.0.0" license: CC-BY-4.0 keywords: - flood - rail - exposure- 01DepositCreate a record on Zenodo under your own account, with your files and your ORCID iD.
- 02DescribePaste the metadata this builder writes, or fill the same fields in the Zenodo form.
- 03Send to the communitySend the record to the Reports community and its Risk Academy sub-community.
- 04CurateCurators accept or decline in the community’s requests, with a reason, in the open.
- 05LinkAn accepted record is linked from the next edition as a source or supplement and receives a UNI.
The Reports community on Zenodo opens with the first operational edition. Until then, send the record’s DOI through the gateway on any page and it is reviewed the same way. Nexus material is published under CC BY 4.0; external material keeps its own licence.
How an edition is published.
| Element | How it is done |
|---|---|
| Repository | Zenodo deposit for each edition: the PDF, the HTML package and the data bundle |
| Identifiers | Concept DOI for the edition, version DOI for each version, a UNI for every finding and figure |
| Metadata | DataCite metadata with ORCID for people, ROR for organisations and funder identifiers |
| Package | RO-Crate with DCAT, PROV-O, CITATION.cff and CodeMeta |
| Integrity | A signed manifest and build provenance for every release; content credentials on figures |
| Corrections | A new version with the notice; the concept DOI resolves to the latest version |
| Discovery | OpenAIRE, OpenAlex and OAI-PMH harvesting follow from the DOI and the metadata |
Open platforms, and what each does.
| Platform | What it does for Reports | What you can do | Link |
|---|---|---|---|
| Zenodo | Repository of record: editions, data bundles and accepted contributions with DataCite DOIs; the concept DOI resolves to the latest version. | Deposit your own record and submit it to the Reports community. | Visit Zenodo |
| ORCID | Contributor identity: your iD travels in the metadata, so DataCite can update your ORCID record. | Add your iD; credit follows your CRediT role. | Visit ORCID |
| ROR | Organisation identity for affiliations and publishers. | Name your organisation; it is resolved to its ROR record. | Visit ROR |
| Software Heritage | Code and models preserved with a SWHID; releases archived on Zenodo with CITATION.cff and CodeMeta. | Point to a release; the exact version is cited. | Visit Software Heritage |
| DataCite and Crossref | DOIs and their relations (new version of, supplemented by, derived from) keep the record linked. | Cite your existing DOI; it is linked, never re-registered. | Visit DataCite and Crossref |
| OpenAIRE and OpenAlex | Discovery: deposits flow into the OpenAIRE Graph and OpenAlex. | Nothing to do; it follows from the DOI and the metadata. | Visit OpenAIRE and OpenAlex |
Eight parts applied to every record.
Reports applies these Nexus Standards parts (preparatory working drafts, 2026) with the external standards they adopt. Conformance is attestation, not certification.
| Part | Title | How Reports applies it |
|---|---|---|
| NS-1 | The UNI and the artefact catalogue | Every edition, finding, figure and accepted contribution receives a UNI that resolves to its record and versions. |
| NS-2 | Citation and attribution | Editor-first citation (NR-CIT-1), CRediT contributor roles, machine forms from one citation record. |
| NS-3b | Dataset and product metadata profile | Data bundles in DCAT, STAC and PROV-O, packed as RO-Crate, so every value resolves to its source. |
| NS-5 | Figures, maps and visualisation | Figures carry source, licence, boundary source and content credentials. |
| NS-12 | Software, models and AI/ML artefacts | Code and models carry CodeMeta, CITATION.cff and SPDX identifiers; AI assistance is disclosed. |
| NS-13 | Open standards development process | Comments and proposals on report method enter as dockets, answered in the open. |
| NS-14 | Conformance and crosswalk to external standards | Report metadata crosswalks to DataCite, InvenioRDM, schema.org, JATS and Crossref; conformance is attestation. |
| NS-16 | UNI application profile | One profile for articles, documents, code, data, APIs and interfaces. |
Five states, never mixed.
- ●OBSERVED
- Measured directly and cited.
- □REPORTED
- Published by a named source and cited.
- ◆ESTIMATED
- A programme analytical value, with its method on the page.
- ○SCENARIO
- Conditional on stated assumptions, never a prediction.
- ◎EXPERT INPUT
- Structured judgement from named roles, with the method stated.
Contribute evidence from this page.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-ACADEMYSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsRisk AcademySee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Around the reports at Risk Academy.
Bring what you know to the next edition.
Every quarter closes on a sealed evidence cut. Contributions received before the cut are reviewed for that edition; later ones wait for the next.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.