G06 · PAGE · record-modelGCRI dossier · service level R0
GCRINexus RegistryEstablished
Nexus Registry · Record model

Data and evidence record model

Nexus Registry, a platform of The Global Centre for Risk and Innovation (GCRI), is designed to hold different kinds of record, from programme states to publications and evidence, in one consistent model. This page sets out that model: how records are identified, which schemas describe them, whose authority each record carries and how its origin is shown. It describes the structure only; released records appear on public records. The current service level is R0: information and enquiries.

Nexus RegistryRegister
  1. 01FieldsGovernance and institutions, Research and evidence
  2. 02STEM methods3 canonical methods applied
  3. 03Topics8 subject pages
  4. 04Counterparts5 platforms in shared fields
  5. 05PublisherThe Global Centre for Risk and Innovation

GCRI · Established · service level R0

01In brief

The short answer.

The Nexus Registry record model is the single structure for every kind of record the Registry holds, from programme states to publications and evidence: how records are identified, which schemas describe them, whose authority each carries and how its origin is shown. It describes structure only; released records appear on public records.

02Geography

Digital demand and connectivity in Poland.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Poland as an example geography for this subject.

Urban demand centres and the hubs that anchor digital and data infrastructure.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Registry · fieldDESIGN FIGURE
03Record types

The kinds of record the Registry is designed to hold.

TypeWhat it records
ProgrammeA national or regional programme and its state over time
PublicationA released report or paper, its identifiers and its versions
EvidenceA dataset, model result or finding, with its evidence label and limits
ParticipationA consented record of a contribution or role, within programme boundaries
CorrectionA change to another record, with its reason and reviewer
04Common fields

What every record carries.

  • a permanent identifier, never reused;
  • the record type and the schema version it follows;
  • the issuer and the authority under which the record is held;
  • the origin: sources, dates and method, with an evidence label;
  • the status and validity period;
  • the visibility class: public, restricted or protected;
  • the version, with links to what it supersedes and what supersedes it.
05Authority

The Registry records authority; it does not create it.

Each record names its owner, the institution with authority over its content, and the steward who maintains it in the Registry. The owner decides what the record says and whether it may be published. The Registry checks that the record is complete and consistent with its schema, and keeps its history. A listing confers no certification, endorsement or public authority.

06Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
Persistent identifierA long-lasting reference to a digital object, person or organisation, such as a DOI, ORCID iD or ROR ID, that resolves even when locations change.
Controlled vocabularyAn agreed list of terms used to describe data consistently.
Schema validationChecking each incoming record against a formal definition of required fields, types and values.
07Schemas

Schemas are versioned and published.

Structure

Versioned schemas

Each record type has a schema with a version. Changes take a new version, and old records keep the schema they were made under.

Meaning

Documented fields

Each field's meaning and allowed values are documented, including the status glossary.

Links

Linked, not copied

Records refer to each other and to external registries by identifier.

08Questions

Questions and answers.

Is a participation record a credential?
No. It records a consented contribution or role within programme boundaries. It is not a licence, a qualification or an employment record.
Who can create a record?
Records are created by or for their owners, through a purpose-bound review. See submit and request review.
Can a record be deleted?
A record can be withdrawn from public view, and personal data can be erased where the law requires. The identifier and a notice remain.
Where are the schemas published?
Schema documentation is published on the Registry as each schema is released for public use.
Why is the record model public before the records?
So that owners, auditors and reviewers can see how a record will be structured and judged before any record is released, and can question the model itself.
Nexus Registry

Bring your expertise to this field.

The current service level is R0: information and enquiries. 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.

Have questions?