Schema-validated ingestion
Incoming records are validated against a versioned schema before they enter the registry. Records that fail are quarantined with the reasons, not partially loaded, so a malformed field never reaches a public view.
GCRI · Registry
Data engineering, interoperability and stewardship are the working base of a registry: the schemas that define a record, the pipelines that ingest and transform it, the identifiers and crosswalks that link it to other systems, and the stewardship that keeps it accurate over time. Every provenance, correction and rights commitment on this platform depends on them.
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 governance and institutions and 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.
Incoming records are validated against a versioned schema before they enter the registry. Records that fail are quarantined with the reasons, not partially loaded, so a malformed field never reaches a public view.
Free-text names of people, organisations and works are matched to ORCID, ROR and DOI records. The match method and confidence are stored with each link, and uncertain matches are routed to a steward.
Each transformation records its inputs, code version, responsible agent and time as PROV statements, so any published field can be traced back to the source rows that produced it.
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.
The data classes behind Data engineering at Registry 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 |
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.
| Idatha | Indima | Label |
|---|---|---|
| Crossref and DataCite metadata | Reference metadata for registered works and outputs | REPORTED |
| ORCID records | Contributor identity and linked works | DECLARED |
| ROR registry | Organisation identifiers, name variants and relationships | REPORTED |
| Partner programme records | Ingested programme and participation records | REPORTED |
| Pipeline run logs | Lineage and transformation history | OBSERVED |
Process explorer · Process
10 steps·4 stages·2 gates
Inqubo
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.
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.
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 | Every record is validated against the published schema version; failures are counted and reported, never dropped silently |
| Reconciliation against source | Record counts and checksums are compared with the source system after every load |
| Lineage audit | A sample of published fields is traced back through the provenance graph to its source rows |
| Round-trip test | Records are exported, re-imported and compared field by field to expose lossy mappings |
Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.
Data and Compute stewards data engineering, interoperability and stewardship for the Consortium and reviews how it is applied across platforms.
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.
Ungalokothi uthumele idatha yomuntu siqu, imininingwane ebucayi yengqalasizinda noma noma yini ongenalo ilungelo lokuyabelana ngayo. Umnikelo ubuyekezwa ngaphambi kokusetshenziswa; ukuwuthumela akunikezi ubuqambi noma amalungelo okuhlela, futhi ukusekela akuthengi muphumela.
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.
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.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.