GCRI · Registry
Public recordWhat the Nexus ecosystem publishes and runs, as data
Interoperable registries
How the Registry connects to the registries and standards around it: what it publishes today, which identifiers it carries or plans to carry, and which research registries the estate reads for display. Each row says whether it is in place, specified or not started.
Four formats, one snapshot.
The same 1,256 records, in the formats other registries and tools read.
Details and digests are on the API and bulk download page.
| Format | File | Content |
|---|---|---|
| JSON | nexus-registry.json | Every record with its fields and relations; versioned and digested. |
| CSV | nexus-registry.csv | One row per record, for spreadsheets and databases. |
| JSON-LD | nexus-registry.jsonld | schema.org, DCAT, Dublin Core terms and PROV-O terms; every record is a node with a stable address. |
| RO-Crate | ro-crate-metadata.json | A Research Object Crate 1.1 descriptor of the dataset, listing the files with their digests. |
The JSON-LD uses W3C DCAT for the catalogue and datasets, Dublin Core terms for titles, identifiers, rights and relations, schema.org for types and status, and PROV-O for programme activities. The crate follows RO-Crate 1.1.
The UNI is the key; the others are crosswalks.
From the open-standards stack of the Nexus Standards. A crosswalk field is where the external identifier is stored on a record.
| Identifier | Role | Crosswalk field |
|---|---|---|
| UNI (NS-1) | primary key for every artefact | none |
| DOI (DataCite via Zenodo) | citable persistent identifier for published artefacts | relatedIdentifiers[IsIdenticalTo, DOI] |
| ORCID | person identifier for creators | creators[].orcid |
| ROR | organisation identifier for publishers and affiliations | creators[].ROR, publisher ROR |
| SPDX | licence identifiers | rights.license |
| SWHID (Software Heritage) | intrinsic identifier for archived source | relatedIdentifiers[IsIdenticalTo, Other] |
| ISO 3166-1 alpha-3 / UN M49 | REGION segment of the UNI | uni.region |
| hexagonal / DGGS cell ids | spatial subject keys for passports and products | subjectRefs |
The registry does not mint DOIs, ORCID iDs or ROR identifiers. Creator and publisher fields in the catalogue are at legal review required, so no ORCID or ROR value is published yet; where a record has one, it is carried as a related identifier.
Bibliographic and catalogue metadata.
The export forms the standards define for a catalogue record.
| Standard | Role | Export |
|---|---|---|
| DataCite Metadata Schema 4.5 | canonical bibliographic record | toDataCite |
| Zenodo deposition metadata | deposit payload | toZenodo |
| Schema.org (Dataset, SoftwareSourceCode, ScholarlyArticle, CreativeWork) | web discovery (Google Dataset Search) | toSchemaOrg (JSON-LD in page head) |
| CodeMeta 3.0 | software description (codemeta.json) | toCodeMeta |
| CITATION.cff 1.2 | citation file for repositories | toCitationCff |
| STAC 1.0 | spatio-temporal assets (EOP, The Global Risks Index (NXS-GRX) products) | toStacItem / toStacCollection (NS-3b; extent only as stated) |
| DCAT 3 | data catalogue interoperability | toDcatDataset (NS-3b) |
| PROV-O | provenance graph (derivations, corrections) | toProvBundle (NS-3b; relatedIdentifiers to PROV predicates, record refs to PROV specialisation-of / prov:wasRevisionOf) |
| OpenAPI 3.1 | service descriptions (SV category) | NS-6 |
Versioned releases on Zenodo, with a DOI, are the planned canonical record.
Each snapshot version is to be deposited on Zenodo as a citable release with a DOI and a RO-Crate, and discovered through OpenAIRE. Until the deposit account is connected, the files on this site are the published copy.
| Index | Via | Gives |
|---|---|---|
| Zenodo | deposit API (sandbox then production) | DOI, OAI-PMH exposure, OpenAIRE harvesting |
| OpenAIRE | Zenodo harvesting | EU research graph visibility |
| Google Dataset Search | Schema.org JSON-LD on public pages | dataset discovery |
| Software Heritage | codemeta.json and public repository archival | SWHID and long-term source archive |
| Crossref / DataCite Commons | DOI metadata | citation graph |
| Nexus resolver | /uni/{uni} (NS-7) | one landing page per UNI with all crosswalks |
- Deposit only records whose legal state is approved and whose access right is open or embargoed; legal review required, restricted and prohibited never leave the repository.
- Every deposit carries the UNI in keywords (nexus-uni:<uni>) and in the description, and the returned DOI is written back to the record as related identifiers[IsIdenticalTo, DOI].
- New versions use Zenodo’s new-version flow under the same concept DOI; the UNI stays the same (NS1-R1).
- Publication on Zenodo is a publication act of the publisher ref institution, recorded in the register of legal decisions.
Research registries read for display.
Pages of the estate can list recent works from open scholarly services. A source is called only when the owner has admitted it for the page use; the others are listed and never queried.
| Service | State for institution pages | Register review state |
|---|---|---|
| OpenAlex | Pending | Legal review required |
| Crossref | Pending | Legal review required |
| DataCite | Pending | Legal review required |
| Zenodo | Pending | Legal review required |
| arXiv | Pending | Legal review required |
| Europe PMC | Pending | Legal review required |
| OpenAIRE Graph | Pending | Legal review required |
Which standard governs which interface.
| Interface | Governed by |
|---|---|
| Identifier and resolver | NS-1, NS-7, NS-16 |
| Citation form | NS-2 |
| Dataset and product metadata | NS-3b: STAC, DCAT and PROV-O |
| Publication and DOI | NS-8 (open) |
| Surfaces that carry a UNI | NS-6 |
| Conformance and crosswalk | NS-14 |
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
- Nexus Standards, the proposed NS series (nexustandards.com)
- W3C Data Catalog Vocabulary (DCAT) version 3
- W3C PROV-O: the PROV ontology
- DataCite DOIs for research data
- ORCID persistent identifiers for researchers
- Research Organization Registry (ROR)
- Zenodo
- Crossref REST API
- OpenAIRE Graph
- RO-Crate 1.1 specification
- JSON-LD 1.1
Questions and answers.
Does the registry have an API?
Can I harvest it with OAI-PMH?
Which DOI should I cite?
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 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.