...

This document outlines the Plateau 1 Core Metadata Schema, detailing the classes and entities involved and offering implementation guidance (usage notes) for developers at regional nodes. It specifically addresses the schema's design and application but excludes discussion on the national catalog, its onboarding process, and future schema expansions. Additional information and versions are available on GitHub.https://github.com/Health-RI/health-ri-metadata/.

Intended Audience

Designed for a technical Technical audience tasked with implementing the metadata schema and stakeholders interested in a detailed understanding of the core schema.

Introduction

...

and Scope

To make it easier to share, find and reuse information scattered across different sources, the research community in the Netherlands has agreed to index its resources in a national catalog (add link to portal documentation Lucie Kulhankova ). The national catalog in turn aims to be indexed in international catalogs. One of the necessary conditions to achieve this goal is a common agreement on the minimum elements needed to search, find and reuse such resources. These elements and their properties are components of the Core Metadata Schema.

Scope

The Core Metadata Schema is a formal shared conceptualisation of the requirements to find and reuse information across Health-RI nodes via the national catalog. It represents a set of minimal elements for describing each resource (including dataset) with common metadata. This scope is consistent with the functionality provided in the Plateau 1 National catalog release package (Lucie Kulhankova add link to documentation on plateau 1 and portal development releases).

The core model (see Diagram) can be further extended and specialised to reflect domain-specific requirements (domains may include omics, imaging, etc). Therefore, we expect additional versions to be released according to the requirements of Plateaus 2 and beyond. All versions will be published via https://github.com/Health-RI/health-ri-metadata/.

The core model is being reviewed by the community of nodes that make up the Health-RI ecosystem (see Feedback section). The final release of this version will be a prerequisite for resources to be included in the national catalog (Lucie Kulhankova add Portal link) and benefit from its offered features. How to implement this model and connect to the national catalog is described in the onboarding documentation. The offered features of the national catalog are defined in Plateau 1 (Lucie Kulhankova add link to Plateau 1 doc)data, the Health-RI nodes decided to list resources in a national directory that can be accessed internationally. They all agreed on what basic information should be included, and that the catalog should be iwhich led to the creation of the Core Metadata Schema. This schema describes the minimum amount of information that should be used to describe resources across Health-RI nodes through the national directory, which is in line with what Plateau 1 offers. The schema can be changed to meet the needs of different areas, and new versions will be released in the future. The onboarding documents have details on how to implement and connect, and the Plateau 1 documents explain what each feature can do.

Notes on Alignment

To create the current core metadata schema, we examined existing metadata from the COVID-19 national portal, metadata schema provided by Health-RI nodes (e.g., ABC metadata), and standards used in portals across Europe and beyond (e.g., W3C, DCAT, DCAT-AP). Then, with assistance from metadata specialists from the hub and nodes, we began mapping their classes and properties. The mappings are detailed in the mapping table. Finally, after conceptualisation, we decided to reuse DCAT and DCAT-AP for its implementation. This version of the Core metadata schema includes DCAT v3 and some selected DCAT-AP mandatory classes and their definitions. The most important entities are those that form the core of the DCAT application profile. DCAT-AP is a DCAT application profile for the exchange of information about catalog of datasets and description of data services in Europe. Hence, the Core metadata schema ensures compatibility with international catalogs which also use DCAT-AP. This is mainly because the DCAT application profile covers the identified requirements.

...

Recommended Properties

Distribution

An available distribution of the dataset.

...