EJP RD Metadata Schema Classes
The tables that follow describe all classes depicted in Figure 5. The tables also provide usage notes for the classes’ properties.
To facilitate navigation within this document, each class is hyperlinked to its corresponding sections within this chapter. By identifying which sections are applicable to your resource, you can jump directly to the relevant fields to describe your resource’s metadata.
Mandatory Classes
Class |
Definition and usage note |
URI |
|---|---|---|
To add resources to the EJP RD Virtual Platform the organisations that provide the resources need to be registered first. For each organisation, the biobanks, patient registries, guidelines, datasets (which may have associated data services) or data services (with no specific dataset), provided by the organisation, need to be added. |
foaf:Organisation |
|
“Resource” |
“Resource is a generic concept from the DCAT2 vocabulary. In our metadata model, we extended it with Rare Disease specific concepts like Biobank and Patient registry, which means that you rarely use this class directly, but indirectly through its extensions. We recommend that you avoid using dcat:Resource directly for your document unless the type that you are looking for is not available in this table (not a Biobank, Patient Registry, Dataset, Data Service, or Guideline). At least one of the resource types described in this table is Mandatory.” |
dcat:Resource (use dcat:Dataset, dcat:DataService, ejprd:PatientRegistry, ejprd:Guideline, or ejprd:Biobank according to your resource type) |
Mandatory Classes (per resource type)
Warning
You must use one (and only one) of the mandatory classes specified in the table below to characterise your resource. Choose the class that best represents the type of resource you are describing.
Class |
Definition and usage note |
URI |
|---|---|---|
Patient Registries (Resource Type) |
Defines all the patient registries for this EJP RD resource in the case where datasets are about content of a rare disease resource such as a patient registry. This class can be used under Catalogue. |
ejprd:PatientRegistry |
Biobanks (Resource Type) |
Defines all the biobanks for this EJP RD resource in the case where datasets are about the content of a rare disease resource such as a biobank. This class can be used under Catalogue. |
ejprd:Biobank |
Dataset (Resource Type) |
Required only when your organisation provides access to 1 or more datasets. This describes details about your dataset(s). However, a single dataset can have different ways in which they are made available to potential users. How a dataset can be accessed is defined in the Distribution. |
dcat:Dataset |
Data Service (Resource Type) |
There are two types of data services in the EJP RD VP – those that query safe data/metadata via an interface (e.g. EJP RD Beacon v2 API), and those that do not serve data, but rather provide analytical or statistical services on potentially sensitive data (e.g. a graph plotting service). The former is associated with the Dataset record from which it serves, while the latter is associated with a Catalog. |
dcat:DataService |
Guideline (Resource type) |
This concept describes guidelines that a resource may have about a particular context. An example would be “Biomarker Development Manual”. |
ejprd:Guideline |
Recommended Classes
Warning
Note that this class is mandatory for FDP Reference Implementation and FiaB, since you cannot create any kind of dataset without first having a Catalog, even if the Catalog has almost no useful metadata
Class |
Definition and usage note |
URI |
|---|---|---|
If your organisation wants to bundle numerous datasets, data services, biobanks, patient registries, or guidelines together under a single title, you need to fill in this sheet. |
dcat:Catalog |
Optional Classes
Class |
Definition and usage note |
URI |
|---|---|---|
A single dataset can be made available in different ways. I.e., it can be downloaded, or it can be accessed online. |
dcat:Distribution |