Structured publishing in JATS XML
Reports are encoded in JATS so text, figures, tables, references and contributor roles are machine-readable, deposited to indexing services and preserved in long-term archives.
GCRI · Reports
Data engineering for publishing
Data engineering, interoperability and stewardship make a report series findable, citable, archivable and correctable. Structured text, persistent identifiers, rich metadata and version control let each figure be traced to its sources, let corrections travel to every system that holds a copy, and let reports remain readable long after their platforms change.
01Register
Data engineering for publishing on the record.
Method recordSTEM method
- MethodData engineering, interoperability and stewardship
- StewardData and Compute
- Applied inReports
- Data5 inputs
- Checks4 validation steps
- Canonical pageSTEM Commons
02Application
What data engineering, interoperability and stewardship does here.
Data engineering, interoperability and stewardship cover the pipelines, standards and governance that make data usable and trustworthy. They determine whether information from different sectors can be combined for joint risk assessment. In research and evidence, sound data engineering allows hazard, exposure and financial data to be linked consistently. It supports transparent and repeatable analysis of interconnected risk. The canonical description is on the STEM Commons.
Persistent identifiers across the record
Reports carry DOIs and an ISSN for the series, contributors ORCID iDs, institutions ROR identifiers, and datasets and code their own DOIs, linked in deposited metadata.
Versioning and update metadata
Every substantive change creates a new identified version, and corrections and retractions are deposited as update relationships so databases and readers see the current status.
03Methods and evidence
How data engineering for publishing is modelled, measured and tested.
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
Datasets and provenance
The data classes behind data engineering for publishing and what is recorded about each before it is used.
| Data class | Provenance recorded | Resolution stated | Licence checked |
|---|---|---|---|
| Satellite imagery, optical and radar | sensor, processing level, acquisition date | pixel size and revisit | per scene |
| Reanalysis and climate model output | model, experiment, member, version | grid and time step | per release |
| In-situ sensors and gauges | station, instrument, calibration record | point and sampling rate | per network |
| Population and asset exposure | method, vintage, input sources | cell size and unit | per release |
| Boundaries and reference geography | producer, edition, date | scale | per edition |
- Lineage
- W3C PROV record from source to figure
- Principles
- FAIR: findable, accessible, interoperable, reusable
- Gaps
- shown as missing, never filled silently
FAIR guiding principles · GO FAIR and FORCE11W3C PROV · World Wide Web ConsortiumGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
04Data
What the method consumes.
Datasets and records used by data engineering, interoperability and stewardship on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Data | Role | Label |
|---|---|---|
| Crossref and DataCite metadata | Identifier registration, references, funding and update links | Published statistics |
| ORCID public data | Contributor identity and affiliations | DECLARED |
| Research Organization Registry | Institution identifiers | Published statistics |
| ISSN Portal | Series identification and title history | Published statistics |
| Directory of Open Access Journals | Open access status and licence of journal sources | REPORTED |
05Process
How the process runs.
Process
Data engineering for publishing: Build, sign and accept
An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.
01 Request and sources
- 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
- 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
02 Build and verify
- 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
- 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
- 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
- 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
03 Sign and admit
- 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
- 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.
04 Accept
- 09Core Build ReportRecord · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
- 10G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.
The programme year · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.
06Validation
How results are checked.
Pipelines are tested with automated quality checks, schema validation and lineage audits. Reconciliation against source systems confirms completeness.
| Check | How it is done |
|---|---|
| Schema validation | JATS and deposit metadata are validated against their schemas before release |
| Identifier resolution | Every DOI, ORCID iD and ROR identifier in a report is checked to resolve to the intended record |
| Reference integrity | References are matched to their records and screened against retraction and correction notices |
| Archive and licence check | Each version is deposited in a preservation archive with a licence that matches the funder policy |
Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.
08Stewardship
Who maintains the method.
Data and Compute stewards data engineering, interoperability and stewardship for the Consortium and reviews how it is applied across platforms.
09Connected
Where this page leads across the Consortium.
10Questions
Questions and answers.
What are the limits of data engineering, interoperability and stewardship in this field?
Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.
How are results checked?
Pipelines are tested with automated quality checks, schema validation and lineage audits. Reconciliation against source systems confirms completeness.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method’s use, not a run; no result is reported here.
Where else is this method applied?
The canonical method page lists every platform that applies it.
ReportsContribute
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.
GCRIReportsGlobal Systems Risk and ResilienceCountry Systems Risk and ResilienceCountry Quarterly
- EmailGateway GW-GCRISend 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.
- ReportsGCRISee 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.
Reports
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal
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.