DMP OPIDoR data models for machine actionable DMPs

The following is a description of the data models currently in use to structure the content of DMPs that are produced either in the context of a scientific project or a research entity (research unit, platform, data infrastructure, observatory... )

The diagrams below illustrate the content structuration of a DMP.

A DMP includes three high-level classes (blue boxes): metadata about the plan (Meta), information about the project (ResearchProject) or the entity (ResearchEntity) and one or several research outputs (ResearchOutput).

The management of a research product throughout its lifecycle is described by the answers to an established list of questions. Classes (represented by yellow-filled boxes) represent the structured content of an answer to a question. Classes are made up of properties and sub-classes (yellow-bordered boxes). The yellow-bordered boxes represent the existing sub-classes. These are combined in a modular way to build the main classes. All classes can be extended by adding properties or sub-classes.

The class-derived display forms (called Templates Json) can be customized to provide the relevant information (labels, examples, default or constant values, registries, external resources, ..).

The SpecificData class (hatched box) enables the creation of specific forms built on classes that are not part of the common model. For example, this class is used for the MesoatLRServiceRequest template.

To begin navigating through the different classes and enums (registries), we recommend starting at the highest level : DMP. For each class, a data dictionary and a Json schema are provided, as well as the templates (standard or customized) for the implemented classes.

For example for DataStorage, DataStorage corresponds to the parent class that is implemented in DMP OPIDoR as DataStorageStandard. This schema has been extended and customized to meet the needs of certain data centers or other entities, such as MesoatLR data center or Clermont Auvergne mesocenter. In the latter cases, customized lists of service types have also been created.