DMP Evaluation Metrics¶

Authors

The following catalogue lists the DMP Evaluation Metrics defined within the OSTrails project.

No.	ID	Title
1	data.reused.co.1	Reused Dataset Declared in the DMP
2	data.reused.co.2	Reused Dataset Has a Persistent Identifier
3	data.reused.co.3	Reused Dataset Has a Declared License
4	data.reused.co.4	Reused Dataset Has Distribution Information
5	data.reused.co.5	Reused Dataset Has Declared Access Conditions
6	data.reused.co.6	Reused Dataset Contains Personal Data
7	data.reused.co.7	Reused Dataset Contains Sensitive Data
8	data.reused.co.8	Reused Dataset Has an Access URL
9	data.reused.feas.1	Reused Dataset PID Resolves in the Repository
10	data.reused.feas.2	Reused Dataset Access Conditions Match the Repository
11	data.reused.feas.3	Reused Dataset License Matches the Repository
12	data.new.1	New Dataset Declared in the DMP
13	data.new.2	New Dataset Collection or Creation Method Declared
14	data.new.3	New Dataset Has Declared Access Conditions
15	data.new.4	New Dataset Has Sufficient Metadata
16	data.new.feas.1	New Dataset Persistent Identifier Resolves Successfully
17	data.new.feas.2	New Dataset Access Conditions Match the Repository
18	data.new.feas.3	New Dataset License Matches the Repository
19	data.info.cov.1	Dataset Type Specified
20	data.info.cov.2	Dataset File Format Specified
21	data.info.cov.3	Dataset Size Specified
22	data.info.feas.1	Dataset Type Matches the Repository
23	data.info.feas.2	Dataset File Format Matches the Repository
24	data.info.feas.3	Dataset Size Matches the Repository
25	meta.comp.1	DMP Common Standard Field Compliance
26	meta.co.1	Controlled Vocabularies Used in Methodology
27	meta.co.2	Electronic Lab Notebook Referenced as a Technical Resource
28	meta.qual.2	ReadMe File Reference
29	meta.stand.comp.1	Metadata Standards Used
30	meta.form.op.1	Dataset Distributions Use Open File Formats
31	meta.doc.qual.1	Electronic Lab Notebook Linked
32	meta.feas.1	Existence of Dataset Documentation
33	qc.qual.1	Quality Control Methods Stated
34	store.cov.1	Data Storage Location mentioned in the DMP
35	store.cov.2	Use of Secure Storage for the dataset in a trusted repository
36	store.comp.1	Alignment of Storage and Backup with Information Sensitivity
37	store.cov.3	Back up Responsibility
38	store.co.1	Back up Frequency
39	store.comp.3	Version Control Practices for Software
40	stor.feas.1	Stored Dataset Location Confirmed
41	secur.co.1	Security Measures Implementation
42	secur.co.2	Sensitive Data Protection Description
43	secur.co.3	Authorised Access Control
44	secur.co.4	Access Control and User Management
45	secur.co.5	Required Access Procedures
46	secur.comp.1	GDPR and Ethics Compliance
47	secur.feas.1	Final Security Measures Implementation
48	sens.secure.co.1	Sensitive Data Using Method
49	sens.secure.co.2	Provision of Anonymised Synthetic Data
50	data.restrict.co.3	Statement of No Data Restrictions
51	data.lice.co.1	Dataset License Declared
52	soft.lice.comp.1	Software Dataset Has a Standardised Machine-Readable License
53	data.agree.comp.2	Data Access Agreements
54	own.co.2	Data Ownership Role Declared
55	soft.auth.co.3	Software Dataset Author Declared
56	ethics.co.1	Ethical Issues Status Declared
57	ethics.co.2	Ethical Issues and Review
58	ethics.co.3	Justification for Absence of Ethical Issues
59	data.shar.op.1	Data Access Status Open for the Dataset
60	data.shar.co.1	Data License is Present
61	data.shar.co.2	Data Restrictions Reference
62	data.shar.comp.1	Dataset License Complies with Funder Requirements
63	data.shar.feas.1	Repository Access Rights Consistency Aligned
64	data.shar.feas.2	Repository Data License Aligned with the DMP
65	data.shar.feas.3	Embargo Implementation Alignment
66	data.shar.feas.4	Repository Data Restrictions
67	data.shar.comp.2	Embargo Declared in the DMP or Repository
68	repo.co.3	Thematic Data Repositories Referenced
69	repo.comp.2	Repository Conforms with FAIR Data Principles
70	repo.comp.3	Trusted Repository is Used
71	repo.co.4	Verification of Back-up Strategy
72	repo.co.5	Certification of Repository
73	repo.co.7	Used Resources for Preservation
74	repo.co.6	Repository Policy is Present
75	repo.feas.1	Repository Identifier Accuracy
76	repo.feas.2	Long-Term Preservation Dataset
77	repo.feas.4	Dataset Characteristics Are Compatible with the Repository
78	data.exteresource.co.1	Data External Resources Included in the DMP
79	data.exteresource.co.2	Metadata Standard Specified in the DMP
80	data.exteresource.feas.1	Resolvable External Resources
81	data.exteresource.feas.2	OpenAIRE Mentioned Dataset Validation
82	data.exteresource.feas.3	Contributor Roles Follow CRediT Taxonomy
83	data.pid.cov.1	Repository Supports Persistent Identifiers for Datasets
84	data.pid.cov.2	Trusted Repository Referenced
85	data.pid.feas.1	Dataset PID System in the DMP Matches the Repository
86	data.pid.feas.3	Dataset Persistent Identifier Resolves Successfully
87	role.co.1	Research Data Management Roles Declared
88	dmp.valid.co.2	DMP Validation by Data Steward
89	role.pid.co.1	Contributors and Organisations PIDs
90	role.feas.1	Referenced RDM Roles
91	role.feas.2	Data Steward Contribution Reflected in the Destination Repository
92	role.feas.3	Contributor and Organisation PIDs Match the Destination Repository
93	cost.co.1	DMP Includes a Budget for Personnel and Monetary Resources
94	cost.co.2	DMP States No Additional RDM Resources Are Required

Metric 1: Reused Dataset Declared in the DMP¶

Metric ID:: data.reused.co.1
Persistent URI:: https://example.org/metric/data.reused.co.1

Title¶

maDMP declares reused datasets

Narrative¶

Checks whether the DMP explicitly identifies at least one dataset as reused from a pre-existing source.

Intended Outcome¶

Determine whether the reuse of existing datasets is explicitly declared in the maDMP, confirming that the research project accounts for pre-existing data sources rather than treating all data as newly produced.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one dataset entry in the maDMP contains a boolean field indicating reuse.

Failure Criterion¶

No dataset entry contains reuse information.

Tests¶

Test 1: Check for reused dataset declaration

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.co.1",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Declared in the DMP"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the DMP explicitly identifies at least one dataset as reused from a pre-existing source."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/madmp-reused-datasets-declared-json"
  },
  "abbreviation": {
    "@value": "data.reused.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "data reuse"
    },
    {
      "@language": "en",
      "@value": "dataset declaration"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Not specified"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 2: Reused Dataset Has a Persistent Identifier¶

Metric ID:: data.reused.co.2
Persistent URI:: https://example.org/metric/data.reused.co.2
Dimension:: Completeness

Title¶

Reused Data PID

Narrative¶

Checks whether each reused dataset referenced in the DMP includes a persistent identifier such as a DOI, so the original data source can be unambiguously referenced.

Intended Outcome¶

Determine whether reused datasets declared in the maDMP are accompanied by a persistent identifier, such as a DOI or URL-based PID, enabling reliable citation and unambiguous discovery of the original data source.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset declared as reused (is_reused = true), an identifier is present (e.g., dataset_id.identifier) and, where applicable, an identifier type is provided.

Failure Criterion¶

At least one reused dataset is missing an identifier or identifier metadata.

Tests¶

Test 3: Check for reused dataset PID

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.co.2",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Has a Persistent Identifier"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether each reused dataset referenced in the DMP includes a persistent identifier such as a DOI, so the original data source can be unambiguously referenced."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC"
  },
  "abbreviation": {
    "@value": "data.reused.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "persistent identifier"
    },
    {
      "@language": "en",
      "@value": "PID"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 3: Reused Dataset Has a Declared License¶

Metric ID:: data.reused.co.3
Persistent URI:: https://example.org/metric/data.reused.co.3
Dimension:: Completeness

Title¶

Reused Data License

Narrative¶

Verifies that each reused dataset referenced in the DMP declares a license, ensuring that users and researchers know the terms under which the data may be used.

Intended Outcome¶

Determine whether reused datasets declared in the maDMP include a license reference, confirming that the legal terms of use for the source data are known and documented in the plan.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset declared as reused (is_reused = true), license metadata is present, including at least a license reference and, where applicable, a start date.

Failure Criterion¶

At least one reused dataset is missing license information or required license fields.

Tests¶

Test 2: Check License for Reused Datasets

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.co.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.co.3",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Has a Declared License"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether each reused dataset referenced in the maDMP declares a license defining the terms of use."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-license"
  },
  "abbreviation": {
    "@value": "data.reused.co.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "data license"
    },
    {
      "@language": "en",
      "@value": "license reference"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.co.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 4: Reused Dataset Has Distribution Information¶

Metric ID:: data.reused.co.4
Persistent URI:: https://example.org/metric/data.reused.co.4
Dimension:: Completeness

Title¶

Reused Data Source

Narrative¶

Verifies that reused datasets referenced in the DMP are shared with sufficient distribution information, confirming that the data source is accessible and not merely cited.

Intended Outcome¶

Determine whether reused datasets declared in the maDMP include distribution information showing how and where the data is accessible, confirming that the source data is not merely cited but properly referenced.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset declared as reused (is_reused = true), distribution or source metadata is present and contains minimally identifying information such as a title and/or an access location.

Failure Criterion¶

At least one reused dataset lacks distribution or source metadata, or required minimal fields.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.co.4",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.co.4",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Has Distribution Information"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether reused datasets in the maDMP include distribution information confirming the data is accessible and not merely cited."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-distribution-present"
  },
  "abbreviation": {
    "@value": "data.reused.co.4-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "data distribution"
    },
    {
      "@language": "en",
      "@value": "data sharing"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.co.4"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 5: Reused Dataset Has Declared Access Conditions¶

Metric ID:: data.reused.co.5
Persistent URI:: https://example.org/metric/data.reused.co.5
Dimension:: Completeness

Title¶

Reused Data Access

Narrative¶

Verifies the access conditions declared for reused datasets in the DMP, ensuring that it is clear whether the data is openly available, shared under conditions, or restricted.

Intended Outcome¶

Determine whether the access conditions for reused datasets are declared in the maDMP, confirming that it is clear whether the data is open, shared under specific conditions, or subject to restrictions.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset declared as reused (is_reused = true), a data_access value is present and has an allowed value (open, shared, or closed).

Failure Criterion¶

At least one reused dataset is missing a data_access value or contains an invalid value.

Tests¶

Test 7: Check Access Rights for Reused Datasets

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.co.5",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.co.5",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Has Declared Access Conditions"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares the access conditions for each reused dataset, distinguishing between open, shared, and restricted access."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-access"
  },
  "abbreviation": {
    "@value": "data.reused.co.5-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "data access"
    },
    {
      "@language": "en",
      "@value": "access rights"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.co.5"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 6: Reused Dataset Contains Personal Data¶

Metric ID:: data.reused.co.6
Persistent URI:: https://example.org/metric/data.reused.co.6
Dimension:: Completeness

Title¶

Reused Data Personal

Narrative¶

Verifies whether any reused datasets contain personal data, as declared in the DMP, so that appropriate data protection measures and compliance obligations can be identified.

Intended Outcome¶

Determine whether reused datasets declared in the machine-actionable Data Management Plan (maDMP) include an explicit statement about the presence of personal data.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset declared as reused (is_reused = true), a personal_data field exists and is explicitly set (e.g., boolean or controlled value).

Failure Criterion¶

At least one reused dataset is missing personal_data information or contains an invalid or undefined value.

Tests¶

Test 8: Check Personal Data Flag for Reused Datasets

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.co.6",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.co.6",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Contains Personal Data"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares whether any reused dataset contains personal data, enabling appropriate data protection measures."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-personal-data"
  },
  "abbreviation": {
    "@value": "data.reused.co.6-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "personal data"
    },
    {
      "@language": "en",
      "@value": "data protection"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.co.6"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 7: Reused Dataset Contains Sensitive Data¶

Metric ID:: data.reused.co.7
Persistent URI:: https://example.org/metric/data.reused.co.7
Dimension:: Completeness

Title¶

Reused Data Sensitive

Narrative¶

Verifies whether any reused datasets contain sensitive data, as declared in the DMP, so that appropriate security and handling requirements can be identified and applied.

Intended Outcome¶

Determine whether reused datasets declared in the machine-actionable Data Management Plan (maDMP) include an explicit statement about the presence of sensitive data.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset declared as reused (is_reused = true), a sensitive_data field exists and is explicitly set (e.g., boolean or controlled value).

Failure Criterion¶

At least one reused dataset is missing sensitive_data information or contains an invalid or undefined value.

Tests¶

Test 9: Check Sensitive Data Flag for Reused Datasets

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.co.7",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.co.7",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Contains Sensitive Data"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares whether any reused dataset contains sensitive data, enabling appropriate security and handling measures."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-sensitive-data"
  },
  "abbreviation": {
    "@value": "data.reused.co.7-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "sensitive data"
    },
    {
      "@language": "en",
      "@value": "data security"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.co.7"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 8: Reused Dataset Has an Access URL¶

Metric ID:: data.reused.co.8
Persistent URI:: https://example.org/metric/data.reused.co.8
Dimension:: Completeness

Title¶

Reused Data URL

Narrative¶

Verifies that reused datasets referenced in the DMP include a URL, making it possible for users to locate and access the original data source directly.

Intended Outcome¶

Determine whether reused datasets declared in the machine-actionable Data Management Plan (maDMP) include a URL pointing to their distribution or access location.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset declared as reused (is_reused = true), at least one distribution includes a non-empty access_url (or equivalent URL field).

Failure Criterion¶

At least one reused dataset lacks a distribution URL.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.co.8",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.co.8",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Has an Access URL"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether each reused dataset in the maDMP includes a URL so that the original data source can be located and accessed."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-distribution-url-present"
  },
  "abbreviation": {
    "@value": "data.reused.co.8-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "access URL"
    },
    {
      "@language": "en",
      "@value": "data location"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.co.8"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 9: Reused Dataset PID Resolves in the Repository¶

Metric ID:: data.reused.feas.1
Persistent URI:: https://example.org/metric/data.reused.feas.1
Dimension:: Feasibility

Title¶

Repository Reused Data PID

Narrative¶

Validates that the reused dataset declared in the DMP can be found in the destination repository, confirming that the referenced data actually exists and is accessible at the stated location.

Intended Outcome¶

Determine whether the PID for each reused dataset declared in the machine-actionable Data Management Plan (maDMP) corresponds to an existing record in a target repository and resolves via a PID resolver.

Applies To¶

maDMP JSON (dataset reuse declarations)
Target repository endpoint
PID resolver service

Success Criterion¶

For each dataset declared as reused (is_reused = true): 1. The dataset identifier in the maDMP matches an identifier discoverable in the target repository record (e.g., DOI URL), and 2. The dataset PID resolves successfully.

Failure Criterion¶

At least one reused dataset PID: - cannot be matched to a target repository record, or - does not resolve via a PID resolver.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.feas.1",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset PID Resolves in the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the reused dataset declared in the maDMP can be found in the destination repository at the stated location."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-repo-match"
  },
  "abbreviation": {
    "@value": "data.reused.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "persistent identifier"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "data discovery"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 10: Reused Dataset Access Conditions Match the Repository¶

Metric ID:: data.reused.feas.2
Persistent URI:: https://example.org/metric/data.reused.feas.2
Dimension:: Feasibility

Title¶

Repository Reused Data Access

Narrative¶

Validates that the access rights of the reused dataset match those of the destination.

Intended Outcome¶

Determine whether the access rights declared for reused datasets in the maDMP match the access rights recorded in the destination repository.

Applies To¶

maDMP JSON (dataset reuse declarations)
Target repository endpoint

Success Criterion¶

For each dataset declared as reused (is_reused = true), the data_access value in the maDMP matches the corresponding access rights value in the destination repository record (e.g., access_right).

Failure Criterion¶

At least one reused dataset has a data_access value in the maDMP that does not match the access rights recorded in the destination repository.

Tests¶

Test 14: Check Reused Data Access Matches Destination

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.feas.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.feas.2",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset Access Conditions Match the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the access conditions for reused datasets declared in the maDMP match the access policy of the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-access-match"
  },
  "abbreviation": {
    "@value": "data.reused.feas.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "data access"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "consistency"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.feas.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 11: Reused Dataset License Matches the Repository¶

Metric ID:: data.reused.feas.3
Persistent URI:: https://example.org/metric/data.reused.feas.3
Dimension:: Feasibility

Title¶

Repository Reused Data License

Narrative¶

Validates that license of the reused dataset match those of the destination.

Intended Outcome¶

Determine whether the license declared for reused datasets in the maDMP matches the license recorded in the destination repository, confirming that the licensing information is consistent across the plan and the repository record.

Applies To¶

maDMP JSON (dataset reuse declarations)
Target repository endpoint

Success Criterion¶

For each dataset declared as reused (is_reused = true), the license value in the maDMP matches the license value in the destination repository record.

Failure Criterion¶

At least one reused dataset has a license value in the maDMP that does not match the license recorded in the destination repository.

Tests¶

Test 15: Check Reused Data License Matches Destination

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.reused.feas.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.reused.feas.3",
  "title": {
    "@language": "en",
    "@value": "Reused Dataset License Matches the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the license declared for reused datasets in the maDMP is consistent with the license recorded in the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-license-match"
  },
  "abbreviation": {
    "@value": "data.reused.feas.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "reused dataset"
    },
    {
      "@language": "en",
      "@value": "data license"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "consistency"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.reused.feas.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 12: New Dataset Declared in the DMP¶

Metric ID:: data.new.1
Persistent URI:: https://example.org/metric/data.new.1
Dimension:: Completeness

Title¶

New Data

Narrative¶

Verifies that the DMP includes a declaration of at least one new dataset being produced or collected as part of the research project, confirming that data production activities are documented.

Intended Outcome¶

Determine whether the maDMP contains at least one dataset that is not explicitly declared as reused (i.e., a “new” dataset is present).

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one dataset entry exists where is_reused is absent (per the stated check), indicating the dataset is not marked as reused.

Failure Criterion¶

All dataset entries include is_reused (i.e., no dataset is found without is_reused), or no dataset entries exist.

Tests¶

Test 16: Check for new data (no is_reused)

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.new.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.new.1",
  "title": {
    "@language": "en",
    "@value": "New Dataset Declared in the DMP"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares at least one new dataset being produced or collected as part of the research project."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-new-data"
  },
  "abbreviation": {
    "@value": "data.new.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "new dataset"
    },
    {
      "@language": "en",
      "@value": "dataset declaration"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "data production"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.new.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 13: New Dataset Collection or Creation Method Declared¶

Metric ID:: data.new.2
Persistent URI:: https://example.org/metric/data.new.2
Sub-Dimension:: RDM Coverage

Title¶

New Data Collection or Creation

Narrative¶

Verifies that the DMP describes how new data were collected or created, providing transparency about the methods and tools used in the data production process.

Intended Outcome¶

Determine whether the maDMP includes technical resource information describing how new data were collected or created, confirming that the data production process is transparent and documented for future users.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one “new” dataset (i.e., dataset not marked as reused per your convention), the technical_resource object is present and includes: - description - name - id.identifier - id.type

Failure Criterion¶

No dataset provides technical_resource, or one or more required fields are missing (description, name, id.identifier, id.type).

Tests¶

Test 17: Check technical_resource for new data collection/creation

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.new.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.new.2",
  "title": {
    "@language": "en",
    "@value": "New Dataset Collection or Creation Method Declared"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP describes the methods and tools used to collect or create new data."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-new-data-technical-resource"
  },
  "abbreviation": {
    "@value": "data.new.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "new dataset"
    },
    {
      "@language": "en",
      "@value": "data collection"
    },
    {
      "@language": "en",
      "@value": "technical resource"
    },
    {
      "@language": "en",
      "@value": "methodology"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.new.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "RDM Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 14: New Dataset Has Declared Access Conditions¶

Metric ID:: data.new.3
Persistent URI:: https://example.org/metric/data.new.3
Dimension:: Openness / Reuse

Title¶

New Data Access

Narrative¶

Verifies that access rights of the new dataset is specified.

Intended Outcome¶

Determine whether “new” datasets in the maDMP specify access rights and rights information needed to understand how the data can be accessed and reused.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one “new” dataset (dataset not marked as reused per your policy): - data_access exists and has a valid value (open, shared, closed), and - dataset rights information is present (according to the maDMP schema used by your project).

Failure Criterion¶

No “new” dataset contains data_access and/or rights information, or data_access is missing/invalid.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.new.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.new.3",
  "title": {
    "@language": "en",
    "@value": "New Dataset Has Declared Access Conditions"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the access rights for new datasets are explicitly declared in the maDMP."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-new-data-access"
  },
  "abbreviation": {
    "@value": "data.new.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "new dataset"
    },
    {
      "@language": "en",
      "@value": "data access"
    },
    {
      "@language": "en",
      "@value": "access rights"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "openness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.new.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Openness / Reuse"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 15: New Dataset Has Sufficient Metadata¶

Metric ID:: data.new.4
Persistent URI:: https://example.org/metric/data.new.4
Dimension:: Completeness

Title¶

New Data Metadata

Narrative¶

Verifies that the DMP provides sufficient metadata for new datasets to support reproducibility, enabling others to understand, reuse, and validate the data in the future.

Intended Outcome¶

Determine whether the maDMP includes sufficient metadata information for new datasets to support reproducibility, ensuring that future users have enough context to understand, validate, and reuse the data.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one “new” dataset (dataset not marked as reused per your policy), the metadata object is present and includes: - description - language - metadata_id.identifier - metadata_id.type

Failure Criterion¶

No “new” dataset provides metadata, or one or more required fields are missing (description, language, metadata_id.identifier, metadata_id.type).

Tests¶

Test 20: Check metadata for new dataset

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.new.4",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.new.4",
  "title": {
    "@language": "en",
    "@value": "New Dataset Has Sufficient Metadata"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP provides sufficient metadata for new datasets to support reproducibility and reuse."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-new-data-metadata"
  },
  "abbreviation": {
    "@value": "data.new.4-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "new dataset"
    },
    {
      "@language": "en",
      "@value": "metadata"
    },
    {
      "@language": "en",
      "@value": "reproducibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.new.4"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 16: New Dataset Persistent Identifier Resolves Successfully¶

Metric ID:: data.new.feas.1
Persistent URI:: https://example.org/metric/data.new.feas.1
Dimension:: Feasibility

Title¶

Repository PID Resolution

Narrative¶

Validates that the PID provided is resolvable according to its system resolver.

Intended Outcome¶

Determine whether dataset identifiers provided in the maDMP exist and can be resolved using an appropriate PID resolver (e.g., DOI resolver).

Applies To¶

maDMP JSON (dataset identifiers)
PID resolver service (e.g., DOI resolver)

Success Criterion¶

At least one dataset includes a dataset_id, and
The dataset_id resolves successfully using the appropriate resolver.

Failure Criterion¶

No dataset_id is provided, and/or the provided PID(s) do not resolve.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.new.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.new.feas.1",
  "title": {
    "@language": "en",
    "@value": "New Dataset Persistent Identifier Resolves Successfully"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the persistent identifier declared for a new dataset in the maDMP resolves to an accessible online resource."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-id-exists"
  },
  "abbreviation": {
    "@value": "data.new.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "new dataset"
    },
    {
      "@language": "en",
      "@value": "persistent identifier"
    },
    {
      "@language": "en",
      "@value": "PID resolution"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.new.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 17: New Dataset Access Conditions Match the Repository¶

Metric ID:: data.new.feas.2
Persistent URI:: https://example.org/metric/data.new.feas.2
Dimension:: Feasibility

Title¶

Repository New Data Access

Narrative¶

Validates that the access rights of the new dataset match those of the destination.

Intended Outcome¶

Determine whether access rights declared for new datasets in the maDMP match the access rights recorded in the destination repository (e.g., Zenodo).

Applies To¶

maDMP JSON (new dataset access information)
Destination repository metadata (e.g., Zenodo access_right)

Success Criterion¶

For each “new” dataset (per your policy for determining new vs reused), the maDMP data_access value matches the destination repository access_right value.

Failure Criterion¶

At least one new dataset has data_access in the maDMP that does not match the destination repository access rights, or required fields cannot be found.

Tests¶

Test 23: Check new data access matches destination

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.new.feas.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.new.feas.2",
  "title": {
    "@language": "en",
    "@value": "New Dataset Access Conditions Match the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the access rights declared for new datasets in the maDMP match the access policy of the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-new-data-access-match-destination"
  },
  "abbreviation": {
    "@value": "data.new.feas.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "new dataset"
    },
    {
      "@language": "en",
      "@value": "data access"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "consistency"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.new.feas.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 18: New Dataset License Matches the Repository¶

Metric ID:: data.new.feas.3
Persistent URI:: https://example.org/metric/data.new.feas.3
Dimension:: Feasibility

Title¶

Repository New Data License

Narrative¶

Validates that license of the new dataset match those of the destination.

Intended Outcome¶

Determine whether the license declared for new datasets in the maDMP matches the license recorded in the destination repository (e.g., Zenodo).

Applies To¶

maDMP JSON (new dataset license information)
Destination repository metadata (e.g., Zenodo license)

Success Criterion¶

For each “new” dataset (per your policy for determining new vs reused), the maDMP license value matches the destination repository license value.

Failure Criterion¶

At least one new dataset has a license value in the maDMP that does not match the destination repository license, or required fields cannot be found.

Tests¶

Test 24: Check new data license matches destination

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.new.feas.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.new.feas.3",
  "title": {
    "@language": "en",
    "@value": "New Dataset License Matches the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the license declared for new datasets in the maDMP is consistent with the license applied by the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-new-data-license-match-destination"
  },
  "abbreviation": {
    "@value": "data.new.feas.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "new dataset"
    },
    {
      "@language": "en",
      "@value": "data license"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "consistency"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.new.feas.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 19: Dataset Type Specified¶

Metric ID:: data.info.cov.1
Persistent URI:: https://example.org/metric/data.info.cov.1
Dimension:: Coverage

Title¶

Data Type

Narrative¶

Verifies that the type of the dataset is qualitative or quantitative.

Intended Outcome¶

Determine whether each dataset in the maDMP specifies its dataset type (e.g., qualitative or quantitative), supporting clearer understanding and management of the data.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset (or at minimum for the dataset(s) in scope), the field dataset.type exists and is non-empty, and its value matches the expected controlled vocabulary (e.g., qualitative or quantitative, or your project’s equivalent terms).

Failure Criterion¶

dataset.type is missing/empty for one or more dataset entries, or uses values outside the accepted vocabulary (if validation against a vocabulary is required).

Tests¶

Test 25: Check dataset.type is specified

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.info.cov.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.info.cov.1",
  "title": {
    "@language": "en",
    "@value": "Dataset Type Specified"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the type of each dataset is declared in the maDMP, enabling users to understand what kind of data has been produced."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-type"
  },
  "abbreviation": {
    "@value": "data.info.cov.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "dataset type"
    },
    {
      "@language": "en",
      "@value": "dataset classification"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "coverage"
    },
    {
      "@language": "en",
      "@value": "data description"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.info.cov.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 20: Dataset File Format Specified¶

Metric ID:: data.info.cov.2
Persistent URI:: https://example.org/metric/data.info.cov.2
Dimension:: Coverage

Title¶

Data Format

Narrative¶

Verifies that the file format of the dataset distribution is declared in the DMP, helping users assess whether the data can be opened and processed with common tools.

Intended Outcome¶

Determine whether dataset distribution information includes an explicit format, supporting understanding of how the data can be accessed and processed.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset distribution (or at minimum for the distribution(s) in scope), distribution.format exists and is non-empty.

Failure Criterion¶

distribution.format is missing/empty for one or more distributions, or no distribution information exists where expected.

Tests¶

Test 26: Check distribution.format is specified

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.info.cov.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.info.cov.2",
  "title": {
    "@language": "en",
    "@value": "Dataset File Format Specified"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the file format of each dataset distribution is declared in the maDMP, helping users assess tool requirements."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-distribution-format"
  },
  "abbreviation": {
    "@value": "data.info.cov.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "file format"
    },
    {
      "@language": "en",
      "@value": "dataset format"
    },
    {
      "@language": "en",
      "@value": "interoperability"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "coverage"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.info.cov.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 21: Dataset Size Specified¶

Metric ID:: data.info.cov.3
Persistent URI:: https://example.org/metric/data.info.cov.3
Dimension:: Coverage

Title¶

Data Size

Narrative¶

Verifies that the size of the dataset distribution is declared in the DMP, supporting storage planning and helping users assess download and processing requirements.

Intended Outcome¶

Determine whether dataset distribution information includes an explicit size declaration, supporting storage planning and helping users assess the practical requirements for downloading and processing the data.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset distribution (or at minimum for the distribution(s) in scope), distribution.byte_size exists and is a valid non-negative number.

Failure Criterion¶

distribution.byte_size is missing, empty, non-numeric, or negative for one or more distributions, or no distribution information exists where expected.

Tests¶

Test 27: Check distribution.byte_size is specified

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.info.cov.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.info.cov.3",
  "title": {
    "@language": "en",
    "@value": "Dataset Size Specified"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the size of each dataset distribution is declared in the maDMP, supporting storage and download planning."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-distribution-byte-size"
  },
  "abbreviation": {
    "@value": "data.info.cov.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "dataset size"
    },
    {
      "@language": "en",
      "@value": "storage planning"
    },
    {
      "@language": "en",
      "@value": "distribution"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "coverage"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.info.cov.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 22: Dataset Type Matches the Repository¶

Metric ID:: data.info.feas.1
Persistent URI:: https://example.org/metric/data.info.feas.1
Dimension:: Feasibility

Title¶

Repository Data Type

Narrative¶

Validates that the type of the dataset match those of the destination.

Intended Outcome¶

Determine whether the dataset type declared in the maDMP matches the dataset type information recorded in the destination repository (e.g., Zenodo), including subtype alignment.

Applies To¶

maDMP JSON (dataset.type)
Destination repository metadata (e.g., Zenodo type and subtype)

Success Criterion¶

For each dataset in scope: 1. dataset.type in the maDMP matches the destination repository type for the corresponding record, and 2. Any declared sub-properties or subtype mappings align (maDMP dataset.type is consistent with destination subtype).

Failure Criterion¶

At least one dataset has a type or subtype mismatch between maDMP and the destination repository, or required fields cannot be retrieved.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.info.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.info.feas.1",
  "title": {
    "@language": "en",
    "@value": "Dataset Type Matches the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the dataset type declared in the maDMP matches the type classification used by the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-type-match-destination-type"
  },
  "abbreviation": {
    "@value": "data.info.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "dataset type"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "type consistency"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.info.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 23: Dataset File Format Matches the Repository¶

Metric ID:: data.info.feas.2
Persistent URI:: https://example.org/metric/data.info.feas.2
Dimension:: Feasibility

Title¶

Repository Data Format

Narrative¶

Validates that the format of the dataset match those of the destination.

Intended Outcome¶

Determine whether the dataset format declared in the maDMP matches the actual file formats stored in the destination repository (e.g., Zenodo).

Applies To¶

maDMP JSON (distribution.format)
Destination repository record (e.g., Zenodo files metadata)

Success Criterion¶

For each dataset distribution in scope, the maDMP distribution.format matches the file format(s) observed in the destination repository record (or is compatible with them under a defined mapping rule).

Failure Criterion¶

At least one distribution format declared in the maDMP does not match (or cannot be mapped to) the formats of the deposited files in the destination repository, or required repository metadata cannot be retrieved.

Tests¶

Test 30: Check final dataset format matches destination files

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.info.feas.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.info.feas.2",
  "title": {
    "@language": "en",
    "@value": "Dataset File Format Matches the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the file format declared in the maDMP matches the format of the data actually deposited in the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-format-match-destination-files"
  },
  "abbreviation": {
    "@value": "data.info.feas.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "file format"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "format consistency"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.info.feas.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 24: Dataset Size Matches the Repository¶

Metric ID:: data.info.feas.3
Persistent URI:: https://example.org/metric/data.info.feas.3
Dimension:: Feasibility

Title¶

Repository Data Size

Narrative¶

Validates that the size of the dataset match those of the destination.

Intended Outcome¶

Determine whether the dataset size declared in the maDMP matches the actual deposited size recorded in the destination repository (e.g., Zenodo).

Applies To¶

maDMP JSON (distribution.byte_size)
Destination repository metadata (e.g., Zenodo file size / total size)

Success Criterion¶

For each dataset distribution in scope, the maDMP distribution.byte_size matches the destination repository recorded size (or is within an acceptable tolerance if you define one).

Failure Criterion¶

At least one distribution has a size mismatch between maDMP and destination repository, or required repository metadata cannot be retrieved.

Tests¶

Test 31: Check final dataset size matches destination size

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.info.feas.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.info.feas.3",
  "title": {
    "@language": "en",
    "@value": "Dataset Size Matches the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the dataset size declared in the maDMP matches the actual size of the data deposited in the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-size-match-destination-size"
  },
  "abbreviation": {
    "@value": "data.info.feas.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "dataset size"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "size consistency"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.info.feas.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 25: DMP Common Standard Field Compliance¶

Metric ID:: meta.comp.1
Persistent URI:: https://example.org/metric/meta.comp.1
Dimension:: Compliance

Title¶

DMP Common Standard Field Compliance

Narrative¶

Verifies that the fields of the DMP JSON are aligned with the data types of the DMP Common Standard.

Intended Outcome¶

Determine whether a maDMP JSON instance conforms to the DMP Common Standard schema, including correct field presence, structure, and data types.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

The maDMP JSON validates successfully against the DMP Common Standard JSON Schema (no validation errors).

Failure Criterion¶

The maDMP JSON fails schema validation (one or more validation errors), including type mismatches, missing required fields, or invalid structures.

Tests¶

Test 32: Check maDMP JSON Validates Against DMP Common Standard Schema

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/meta.comp.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/meta.comp.1",
  "title": {
    "@language": "en",
    "@value": "DMP Common Standard Field Compliance"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP is a valid JSON document that conforms to the RDA DMP Common Standard schema."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dmp-cs-schema-validation"
  },
  "abbreviation": {
    "@value": "meta.comp.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "DMP Common Standard"
    },
    {
      "@language": "en",
      "@value": "schema validation"
    },
    {
      "@language": "en",
      "@value": "JSON"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "compliance"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/meta.comp.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 26: Controlled Vocabularies Used in Methodology¶

Metric ID:: meta.co.1
Persistent URI:: https://example.org/metric/meta.co.1
Dimension:: Completeness

Title¶

Controlled Vocabularies Used in Methodology

Narrative¶

Verifies that the DMP references controlled vocabularies in the description of the research methodology, promoting consistency and interoperability in how data and concepts are described.

Intended Outcome¶

Determine whether the methodology information in the maDMP references controlled vocabularies, supporting semantic consistency and making it easier for others to interpret and reuse the described methods and data.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For dataset methodology information in scope, dataset_methodology includes references to one or more controlled vocabularies, ontology terms, or externally defined vocabulary sources.

Failure Criterion¶

No controlled vocabulary usage can be identified in dataset_methodology, or methodology information is missing where expected.

Tests¶

Test 33: Check dataset_methodology for controlled vocabularies

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/meta.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/meta.co.1",
  "title": {
    "@language": "en",
    "@value": "Controlled Vocabularies Used in Methodology"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the methodology description in the maDMP references terms from a recognised controlled vocabulary."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-methodology-controlled-vocabularies"
  },
  "abbreviation": {
    "@value": "meta.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "controlled vocabulary"
    },
    {
      "@language": "en",
      "@value": "methodology"
    },
    {
      "@language": "en",
      "@value": "interoperability"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/meta.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 27: Electronic Lab Notebook Referenced as a Technical Resource¶

Metric ID:: meta.co.2
Persistent URI:: https://example.org/metric/meta.co.2
Dimension:: Completeness

Title¶

Electronic Lab Notebook Referenced as a technical resource

Narrative¶

Verifies that the reference of an electronic lab notebook is included.

Intended Outcome¶

Determine whether the maDMP includes a reference to an electronic lab notebook (ELN) as part of the declared technical resources.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one technical_resource.name value indicates an electronic lab notebook, or a technical resource is clearly identified as an ELN.

Failure Criterion¶

No technical resource references an electronic lab notebook, or technical resource information is missing where expected.

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/meta.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/meta.co.2",
  "title": {
    "@language": "en",
    "@value": "Electronic Lab Notebook Referenced as a Technical Resource"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP references an electronic lab notebook as a technical resource used in the research project."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-technical-resource-eln-reference"
  },
  "abbreviation": {
    "@value": "meta.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "electronic lab notebook"
    },
    {
      "@language": "en",
      "@value": "ELN"
    },
    {
      "@language": "en",
      "@value": "technical resource"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "completeness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/meta.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 28: ReadMe File Reference¶

Metric ID:: meta.qual.2
Persistent URI:: https://example.org/metric/meta.qual.2
Dimension:: Quality

Title¶

ReadMe File Reference

Narrative¶

Verifies that ReadMe file is mentioned.

Intended Outcome¶

Determine whether the maDMP includes a reference to a ReadMe file, supporting dataset interpretability and documentation quality.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one related identifier entry indicates a ReadMe file through its resource_type (or equivalent field), showing that a ReadMe file is included or referenced.

Failure Criterion¶

No related identifier entry indicates a ReadMe file, or related identifier information is missing where expected.

Tests¶

Test 35: Check related_identifier resource_type for ReadMe file

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/meta.qual.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/meta.qual.2",
  "title": {
    "@language": "en",
    "@value": "ReadMe File Reference"
  },
  "description": {
    "@language": "en",
    "@value": "Verifies that ReadMe file is mentioned."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-related-identifier-readme-file"
  },
  "abbreviation": {
    "@value": "meta.qual.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "template keyword"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/meta.qual.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Quality"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 29: Metadata Standards Used¶

Metric ID:: meta.stand.comp.1
Persistent URI:: https://example.org/metric/meta.stand.comp.1
Dimension:: Compliance

Title¶

Metadata Standards Used

Narrative¶

Validates if the Metadata Standard is aligned with Metadata Registries.

Intended Outcome¶

Determine whether the metadata standards referenced in the maDMP are registered in recognized metadata registries such as the RDA Metadata Standards Catalog and FAIRsharing.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format plus external metadata registry sources.

Success Criterion¶

For each metadata standard in scope, metadata_standard_id is present and can be matched to an entry in a recognized metadata registry such as the RDA Metadata Standards Catalog and/or FAIRsharing.

Failure Criterion¶

metadata_standard_id is missing, or one or more referenced metadata standards cannot be found in the target registries.

Tests¶

Test 36: Check metadata_standard_id is registered in metadata registries

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/meta.stand.comp.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/meta.stand.comp.1",
  "title": {
    "@language": "en",
    "@value": "Metadata Standards Used"
  },
  "description": {
    "@language": "en",
    "@value": "Validates if the Metadata Standard is aligned with Metadata Registries."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-metadata-standard-registered"
  },
  "abbreviation": {
    "@value": "meta.stand.comp.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "template keyword"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/meta.stand.comp.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 31: Electronic Lab Notebook Linked¶

Metric ID:: meta.doc.qual.1
Persistent URI:: https://example.org/metric/meta.doc.qual.1
Dimension:: Quality

Title¶

Electronic Lab Notebook Linked

Narrative¶

Verifies that the dataset is linked to the notebook.

Intended Outcome¶

Determine whether the dataset declared in the maDMP is linked to an electronic lab notebook (ELN), either through a related_identifier entry or through a technical_resource.name reference that associates the dataset with a notebook record.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, a related_identifier entry exists that references the electronic lab notebook dataset, or a technical_resource.name value is present that identifies an ELN and includes associated related_ids linking it to the dataset.

Failure Criterion¶

No dataset contains a related_identifier or technical_resource.name entry that can be linked to an electronic lab notebook.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/meta.doc.qual.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/meta.doc.qual.1",
  "title": {
    "@language": "en",
    "@value": "Electronic Lab Notebook Linked"
  },
  "description": {
    "@language": "en",
    "@value": "Verifies that the dataset is linked to the notebook."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-eln-dataset-linked-related-ids"
  },
  "abbreviation": {
    "@value": "meta.doc.qual.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "electronic lab notebook"
    },
    {
      "@language": "en",
      "@value": "related identifier"
    },
    {
      "@language": "en",
      "@value": "dataset linkage"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/meta.doc.qual.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Quality"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 30: Dataset Distributions Use Open File Formats¶

Metric ID:: meta.form.op.1
Persistent URI:: https://example.org/metric/meta.form.op.1
Dimension:: Openness

Title¶

Use of Open File Formats for datasets

Narrative¶

Validates that the file formats used for dataset distributions are open and non-proprietary, ensuring long-term accessibility and reducing barriers to data reuse.

Intended Outcome¶

Determine whether the dataset distributions declared in the maDMP use open file formats, supporting long-term accessibility and ensuring that the data can be read without proprietary software.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For each dataset distribution in scope, the declared distribution_format (or equivalent format field) is recognized as an open file format according to the rules or registry used by your project.

Failure Criterion¶

At least one declared dataset format is not open, cannot be classified as open, or format information is missing where expected.

Tests¶

Test 37: Check distribution format is open

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/meta.form.op.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/meta.form.op.1",
  "title": {
    "@language": "en",
    "@value": "Dataset Distributions Use Open File Formats"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the file formats declared for dataset distributions in the maDMP are open and non-proprietary."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-distribution-format-open"
  },
  "abbreviation": {
    "@value": "meta.form.op.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "open file format"
    },
    {
      "@language": "en",
      "@value": "interoperability"
    },
    {
      "@language": "en",
      "@value": "data accessibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "openness"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/meta.form.op.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Openness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 32: Existence of Dataset Documentation¶

Metric ID:: meta.feas.1
Persistent URI:: https://example.org/metric/meta.feas.1
Dimension:: Feasibility

Title¶

Existence of Dataset Documentation

Narrative¶

Validates if there is a form of accompanying documentation for the dataset.

Intended Outcome¶

Determine whether the maDMP includes at least one form of accompanying documentation for the dataset, declared through technical_resource.name or technical_resource.technical_resource_id.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, a technical_resource entry exists with a non-empty name or technical_resource_id, indicating that supporting documentation is declared.

Failure Criterion¶

No dataset contains a technical_resource entry, or all technical_resource entries are missing both name and technical_resource_id.

Tests¶

Test 39: Check technical_resource for dataset documentation

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/meta.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/meta.feas.1",
  "title": {
    "@language": "en",
    "@value": "Existence of Dataset Documentation"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP references a technical resource providing documentation for the dataset."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-technical-resource-dataset-documentation"
  },
  "abbreviation": {
    "@value": "meta.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "dataset documentation"
    },
    {
      "@language": "en",
      "@value": "technical resource"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/meta.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 33: Quality Control Methods Stated¶

Metric ID:: qc.qual.1
Persistent URI:: https://example.org/metric/qc.qual.1
Dimension:: Quality

Title¶

Quality Control Methods Stated

Narrative¶

Verifies that the DMP describes the quality control methods applied to the data, giving users and reviewers confidence in the accuracy and reliability of the dataset.

Intended Outcome¶

Determine whether the maDMP includes a statement of quality control methods for the dataset, either as free-text narrative or as controlled terms in the data_quality_assurance field.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, the data_quality_assurance field is present and non-empty, containing either a narrative description or one or more controlled terms describing the quality control methods applied.

Failure Criterion¶

No dataset contains a data_quality_assurance field, or all present values are empty or missing.

Tests¶

Test 40: Check data_quality_assurance for quality control methods

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/qc.qual.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/qc.qual.1",
  "title": {
    "@language": "en",
    "@value": "Quality Control Methods Stated"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP describes the quality control methods applied to ensure the accuracy and reliability of the data."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-data-quality-assurance"
  },
  "abbreviation": {
    "@value": "qc.qual.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "quality control"
    },
    {
      "@language": "en",
      "@value": "data quality assurance"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    },
    {
      "@language": "en",
      "@value": "quality"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/qc.qual.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Quality"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 34: Data Storage Location mentioned in the DMP¶

Metric ID:: store.cov.1
Persistent URI:: https://example.org/metric/store.cov.1
Dimension:: Coverage

Title¶

Data Storage Location mentioned in the DMP

Narrative¶

Verifies that the DMP identifies where the data will be stored during the active phase of the project, ensuring that storage responsibilities and locations are clearly documented.

Intended Outcome¶

Determine whether the maDMP includes a reference to a data storage location for the dataset, declared through host.title or host.url within a distribution entry.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, a host object is present containing a non-empty host.title or host.url, indicating that a storage location has been declared.

Failure Criterion¶

No dataset distribution contains a host object, or all present host entries are missing both title and url.

Tests¶

Test 41: Check host.title and host.url for storage location

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/store.cov.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/store.cov.1",
  "title": {
    "@language": "en",
    "@value": "Data Storage Location mentioned in the DMP"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP identifies the location where data will be stored during the active phase of the project."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-storage-location"
  },
  "abbreviation": {
    "@value": "store.cov.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "data storage"
    },
    {
      "@language": "en",
      "@value": "storage location"
    },
    {
      "@language": "en",
      "@value": "host"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/store.cov.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 35: Use of Secure Storage for the dataset in a trusted repository¶

Metric ID:: store.cov.2
Persistent URI:: https://example.org/metric/store.cov.2
Dimension:: Coverage

Title¶

Use of Secure Storage for the dataset in a trusted repository

Narrative¶

Verifies that the data are not planned to be stored in personal devices.

Intended Outcome¶

Determine whether the maDMP declares a trusted repository as the storage host for the dataset, rather than a personal device or unmanaged storage location.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the host object is present and its properties (e.g., host.title, host.url, or host.certified_with) indicate a recognized or trusted repository rather than a personal device.

Failure Criterion¶

No dataset distribution declares a host, or all declared hosts cannot be identified as a trusted repository (e.g., reference to personal storage, local device, or missing host information).

Tests¶

Test 42: Check host for trusted repository storage

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/store.cov.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/store.cov.2",
  "title": {
    "@language": "en",
    "@value": "Use of Secure Storage for the dataset in a trusted repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP specifies a trusted repository as the storage location for the dataset."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-trusted-repository"
  },
  "abbreviation": {
    "@value": "store.cov.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "trusted repository"
    },
    {
      "@language": "en",
      "@value": "secure storage"
    },
    {
      "@language": "en",
      "@value": "host"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/store.cov.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 36: Alignment of Storage and Backup with Information Sensitivity¶

Metric ID:: store.comp.1
Persistent URI:: https://example.org/metric/store.comp.1
Dimension:: Compliance

Title¶

Alignment of Storage and Backup with Information Sensitivity

Narrative¶

Verifies that the DMP declares the sensitivity or classification level of the dataset and that the planned storage and backup strategies align with this classification.

Intended Outcome¶

Determine whether the maDMP both declares a sensitivity classification for the dataset and ensures that the declared storage and backup approach is appropriate for that classification level.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope: - sensitive_data is present and explicitly set, and - the associated distribution host includes security_and_privacy and/or backup_type values that are consistent with the declared sensitivity level.

Failure Criterion¶

At least one dataset is missing sensitive_data, or the declared storage and backup properties (security_and_privacy, backup_type) are absent or inconsistent with the sensitivity classification.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/store.comp.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/store.comp.1",
  "title": {
    "@language": "en",
    "@value": "Alignment of Storage and Backup with Information Sensitivity"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the sensitivity classification and storage security measures in the maDMP are aligned."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-sensitive-data-classification"
  },
  "abbreviation": {
    "@value": "store.comp.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "sensitive data"
    },
    {
      "@language": "en",
      "@value": "storage security"
    },
    {
      "@language": "en",
      "@value": "backup"
    },
    {
      "@language": "en",
      "@value": "compliance"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/store.comp.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 37: Back up Responsibility¶

Metric ID:: store.cov.3
Persistent URI:: https://example.org/metric/store.cov.3
Dimension:: Coverage

Title¶

Back up Responsibility

Narrative¶

Verifies that there is someone responsible for back up activities.

Intended Outcome¶

Determine whether the maDMP declares at least one contributor with a role explicitly associated with backup responsibility, confirming that someone is accountable for ensuring the data is regularly and reliably backed up.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one contributor entry is present with a role value that indicates responsibility for backup activities (e.g., a backup manager, data steward, or equivalent role defined by your project’s controlled vocabulary).

Failure Criterion¶

No contributor entry exists, or no contributor has a role value that can be associated with backup responsibilities.

Tests¶

Test 45: Check contributor.role for backup responsibility

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/store.cov.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/store.cov.3",
  "title": {
    "@language": "en",
    "@value": "Back up Responsibility"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP assigns backup responsibility to at least one named contributor."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-contributor-role-backup"
  },
  "abbreviation": {
    "@value": "store.cov.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "backup responsibility"
    },
    {
      "@language": "en",
      "@value": "contributor role"
    },
    {
      "@language": "en",
      "@value": "data stewardship"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/store.cov.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 38: Back up Frequency¶

Metric ID:: store.co.1
Persistent URI:: https://example.org/metric/store.co.1
Dimension:: Completeness

Title¶

Back up Frequency

Narrative¶

Verifies that the DMP specifies how often backups of the data will be performed, helping to ensure that data can be recovered in the event of loss or corruption.

Intended Outcome¶

Determine whether the maDMP declares a backup frequency for the dataset, indicating that backup activities are planned at a defined interval.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the host.backup_frequency field is present and non-empty, indicating that a backup schedule has been declared.

Failure Criterion¶

No dataset distribution contains a host object with a backup_frequency field, or all present values are empty or missing.

Tests¶

Test 46: Check backup_frequency is declared

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/store.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/store.co.1",
  "title": {
    "@language": "en",
    "@value": "Back up Frequency"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP specifies the frequency at which data backups will be performed."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-backup-frequency"
  },
  "abbreviation": {
    "@value": "store.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "backup frequency"
    },
    {
      "@language": "en",
      "@value": "backup schedule"
    },
    {
      "@language": "en",
      "@value": "data storage"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/store.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 39: Version Control Practices for Software¶

Metric ID:: store.comp.3
Persistent URI:: https://example.org/metric/store.comp.3
Dimension:: Compliance

Title¶

Version Control Practices for Software

Narrative¶

Verifies that a description of the version control system used for developed software is included, along with information on how versioning and updates will be managed throughout the project.

Intended Outcome¶

Determine whether the maDMP includes a reference to a version control system for software developed as part of the project, and optionally declares metadata about update plans or versioning frequency.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset or technical resource in scope, the maDMP includes a mention of a version control system (e.g., via technical_resource.name, technical_resource.description, or an equivalent field), and optionally includes information on update plans or versioning frequency.

Failure Criterion¶

No mention of a version control system can be found in any technical_resource or equivalent field, or the relevant fields are absent or empty.

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/store.comp.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/store.comp.3",
  "title": {
    "@language": "en",
    "@value": "Version Control Practices for Software"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP satisfies the criterion: version control practices for software."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-version-control-system"
  },
  "abbreviation": {
    "@value": "store.comp.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "version control"
    },
    {
      "@language": "en",
      "@value": "software versioning"
    },
    {
      "@language": "en",
      "@value": "update management"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/store.comp.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 40: Stored Dataset Location Confirmed¶

Metric ID:: stor.feas.1
Persistent URI:: https://example.org/metric/stor.feas.1
Dimension:: Feasibility

Title¶

Stored Dataset Location Confirmed

Narrative¶

Validates that the storage location declared in the DMP matches the actual destination repository where the data has been deposited, confirming consistency between plan and practice.

Intended Outcome¶

Determine whether the storage location declared in the maDMP (host.id) can be confirmed to match the actual destination where the dataset has been deposited, as verified against an external repository such as Zenodo.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with a target repository (e.g., Zenodo).

Success Criterion¶

The host.id declared in the maDMP resolves to the same repository or record identifier as the dataset’s actual deposit location in the target repository (e.g., Zenodo), confirming that planned and actual storage locations are consistent.

Failure Criterion¶

The host.id in the maDMP is absent, does not resolve, or does not match the identifier of the actual deposit location in the target repository.

Tests¶

Test 47: Check host.id matches Zenodo deposit location

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/stor.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/stor.feas.1",
  "title": {
    "@language": "en",
    "@value": "Stored Dataset Location Confirmed"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the storage location declared in the maDMP matches the destination repository where the data has been deposited."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-id-matches-zenodo"
  },
  "abbreviation": {
    "@value": "stor.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "storage location"
    },
    {
      "@language": "en",
      "@value": "deposit confirmation"
    },
    {
      "@language": "en",
      "@value": "Zenodo"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/stor.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 41: Security Measures Implementation¶

Metric ID:: secur.co.1
Persistent URI:: https://example.org/metric/secur.co.1
Dimension:: Completeness

Title¶

Security Measures Implementation

Narrative¶

Verifies that secure measures are implemented to ensure data security during the project.

Intended Outcome¶

Determine whether the maDMP declares at least one security measure for the dataset, through a non-empty security_and_privacy.title entry within a distribution host.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, a security_and_privacy object is present with a non-empty title value, indicating that a named security measure has been declared.

Failure Criterion¶

No dataset distribution contains a security_and_privacy object, or all present entries are missing a title or have an empty value.

Tests¶

Test 48: Check security_and_privacy.title for security measures

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/secur.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/secur.co.1",
  "title": {
    "@language": "en",
    "@value": "Security Measures Implementation"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP includes a named security measure applied to protect the dataset."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-security-and-privacy-title"
  },
  "abbreviation": {
    "@value": "secur.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "security measures"
    },
    {
      "@language": "en",
      "@value": "data security"
    },
    {
      "@language": "en",
      "@value": "security and privacy"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/secur.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 42: Sensitive Data Protection Description¶

Metric ID:: secur.co.2
Persistent URI:: https://example.org/metric/secur.co.2
Dimension:: Completeness

Title¶

Sensitive Data Protection Description

Narrative¶

Verifies that if the data are sensitive, then there is a description which includes mention of access rights management via institutional storage.

Intended Outcome¶

Determine whether the maDMP, for any dataset flagged as sensitive, includes a security_and_privacy.description that addresses access rights management, such as through institutional storage or equivalent access control mechanisms.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset where sensitive_data is set to true (or equivalent), a security_and_privacy entry is present with a non-empty description that includes reference to access rights management (e.g., institutional storage, access controls, or authorization mechanisms).

Failure Criterion¶

A dataset is flagged as sensitive but has no security_and_privacy entry, or the description field is absent, empty, or contains no reference to access rights management.

Tests¶

Test 49: Check security_and_privacy.description for access rights management

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/secur.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/secur.co.2",
  "title": {
    "@language": "en",
    "@value": "Sensitive Data Protection Description"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP describes how access rights to the dataset are managed."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-security-and-privacy-description"
  },
  "abbreviation": {
    "@value": "secur.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "sensitive data"
    },
    {
      "@language": "en",
      "@value": "access rights management"
    },
    {
      "@language": "en",
      "@value": "data protection"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/secur.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 43: Authorised Access Control¶

Metric ID:: secur.co.3
Persistent URI:: https://example.org/metric/secur.co.3
Dimension:: Completeness

Title¶

Authorised Access Control

Narrative¶

Verifies that the DMP includes a description of access control measures for authorised users.

Intended Outcome¶

Determine whether the maDMP includes a security_and_privacy.description that explicitly describes access control measures restricting data access to authorised users only.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, a security_and_privacy entry is present with a non-empty description that references access control measures for authorised users (e.g., role-based access, authentication requirements, or user authorisation procedures).

Failure Criterion¶

No dataset distribution contains a security_and_privacy entry, or all present description values are absent, empty, or contain no reference to access control for authorised users.

Tests¶

Test 50: Check security_and_privacy.description for authorised access controls

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/secur.co.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/secur.co.3",
  "title": {
    "@language": "en",
    "@value": "Authorised Access Control"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP describes the controls used to authorise access to the dataset."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-security-and-privacy-authorised-access"
  },
  "abbreviation": {
    "@value": "secur.co.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "access control"
    },
    {
      "@language": "en",
      "@value": "authorised users"
    },
    {
      "@language": "en",
      "@value": "data security"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/secur.co.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 44: Access Control and User Management¶

Metric ID:: secur.co.4
Persistent URI:: https://example.org/metric/secur.co.4
Dimension:: Completeness

Title¶

Access Control and User Management

Narrative¶

Verifies that the DMP includes a description of access control and user permission management when sensitive data exist.

Intended Outcome¶

Determine whether the maDMP, for datasets containing sensitive data, includes a security_and_privacy.description that addresses how access to the data is controlled and whether user roles or permissions are defined.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset where sensitive data is present, a security_and_privacy entry exists with a non-empty description that references both access control mechanisms and user role or permission definitions (e.g., role-based access control, permission levels, or user group management).

Failure Criterion¶

No dataset containing sensitive data includes a security_and_privacy entry, or all present description values are absent, empty, or contain no reference to access control and user permission management.

Tests¶

Test 51: Check security_and_privacy.description for access control and user permissions

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/secur.co.4",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/secur.co.4",
  "title": {
    "@language": "en",
    "@value": "Access Control and User Management"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP describes the procedures for managing user access and permissions."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-security-and-privacy-user-management"
  },
  "abbreviation": {
    "@value": "secur.co.4-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "access control"
    },
    {
      "@language": "en",
      "@value": "user management"
    },
    {
      "@language": "en",
      "@value": "user permissions"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/secur.co.4"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 45: Required Access Procedures¶

Metric ID:: secur.co.5
Persistent URI:: https://example.org/metric/secur.co.5
Dimension:: Completeness

Title¶

Required Access Procedures

Narrative¶

Verifies whether the DMP describes the procedures required to gain access to the data.

Intended Outcome¶

Determine whether the maDMP includes a security_and_privacy.description that explicitly describes the procedures a user must follow to request or obtain access to restricted or sensitive data.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, a security_and_privacy entry is present with a non-empty description that outlines the procedures required to gain access to the data (e.g., data access request process, approval workflow, contact point for access, or equivalent procedural information).

Failure Criterion¶

No dataset contains a security_and_privacy entry, or all present description values are absent, empty, or contain no reference to access procedures for restricted or sensitive data.

Tests¶

Test 52: Check security_and_privacy.description for access procedures

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/secur.co.5",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/secur.co.5",
  "title": {
    "@language": "en",
    "@value": "Required Access Procedures"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP describes the procedures that users must follow to request access to the dataset."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-security-and-privacy-access-procedures"
  },
  "abbreviation": {
    "@value": "secur.co.5-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "access procedures"
    },
    {
      "@language": "en",
      "@value": "restricted data"
    },
    {
      "@language": "en",
      "@value": "data access request"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/secur.co.5"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 47: Final Security Measures Implementation¶

Metric ID:: secur.feas.1
Persistent URI:: https://example.org/metric/secur.feas.1
Dimension:: Feasibility

Title¶

Final Security Measures Implementation

Narrative¶

Validates that security measures have been implemented in the destination.

Intended Outcome¶

Determine whether the maDMP confirms that the security measures declared for the dataset have been implemented at the destination repository, as evidenced by a non-empty security_and_privacy.title entry.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, a security_and_privacy entry is present with a non-empty title, confirming that a named security measure has been implemented at the destination.

Failure Criterion¶

No dataset distribution contains a security_and_privacy entry with a non-empty title, indicating that no security measures have been confirmed as implemented at the destination.

Tests¶

Test 54: Check security_and_privacy.title for implemented security measures at destination

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/secur.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/secur.feas.1",
  "title": {
    "@language": "en",
    "@value": "Final Security Measures Implementation"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the security measures declared in the maDMP are reflected in the destination repository record."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-security-and-privacy-title-destination"
  },
  "abbreviation": {
    "@value": "secur.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "security measures"
    },
    {
      "@language": "en",
      "@value": "destination repository"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/secur.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 48: Sensitive Data Using Method¶

Metric ID:: sens.secure.co.1
Persistent URI:: https://example.org/metric/sens.secure.co.1
Dimension:: Completeness

Title¶

Sensitive Data Using Method

Narrative¶

Verifies that when sensitive data are involved, the DMP includes a description of the method used to protect them.

Intended Outcome¶

Determine whether the maDMP, for any dataset where sensitive_data is set to true, includes a non-empty security_and_privacy.description that describes the method used to protect the sensitive data.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset where sensitive_data is set to true (or equivalent), a security_and_privacy entry is present with a non-empty description that identifies or describes the data protection method applied.

Failure Criterion¶

A dataset is flagged as sensitive but has no security_and_privacy entry, or all present description values are absent or empty, with no data protection method described.

Tests¶

Test 55: Check security_and_privacy.description for data protection method when sensitive_data is true

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/sens.secure.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/sens.secure.co.1",
  "title": {
    "@language": "en",
    "@value": "Sensitive Data Using Method"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP describes the method used to protect sensitive data when the dataset is flagged as sensitive."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-sensitive-data-protection-method"
  },
  "abbreviation": {
    "@value": "sens.secure.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "sensitive data"
    },
    {
      "@language": "en",
      "@value": "data protection method"
    },
    {
      "@language": "en",
      "@value": "security and privacy"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/sens.secure.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 49: Provision of Anonymised Synthetic Data¶

Metric ID:: sens.secure.co.2
Persistent URI:: https://example.org/metric/sens.secure.co.2
Dimension:: Completeness

Title¶

Provision of Anonymised Synthetic Data

Narrative¶

Verifies that there is the intention to provide an anonymised synthetic version of the original data.

Intended Outcome¶

Determine whether the maDMP includes a declaration of intent to provide an anonymised or synthetic version of the dataset, as evidenced through a relevant entry in the security_and_privacy field.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, a security_and_privacy entry is present whose title or description references the provision of anonymised or synthetic data (e.g., anonymisation, pseudonymisation, synthetic data generation, or equivalent terms).

Failure Criterion¶

No dataset contains a security_and_privacy entry, or all present entries contain no reference to the provision of anonymised or synthetic data.

Tests¶

Test 56: Check security_and_privacy for anonymised synthetic data provision

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/sens.secure.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/sens.secure.co.2",
  "title": {
    "@language": "en",
    "@value": "Provision of Anonymised Synthetic Data"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares that anonymised or synthetic data will be provided as an alternative to restricted data."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-anonymised-synthetic-data"
  },
  "abbreviation": {
    "@value": "sens.secure.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "anonymisation"
    },
    {
      "@language": "en",
      "@value": "synthetic data"
    },
    {
      "@language": "en",
      "@value": "sensitive data"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/sens.secure.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 50: Statement of No Data Restrictions¶

Metric ID:: data.restrict.co.3
Persistent URI:: https://example.org/metric/data.restrict.co.3
Dimension:: Completeness

Title¶

Statement of No Data Restrictions

Narrative¶

Verifies that the DMP explicitly states that no access restrictions apply to the data, making it clear to users and reviewers that the dataset is freely available.

Intended Outcome¶

Determine whether the maDMP explicitly states that no restrictions apply to the dataset, as declared through the rights field of the distribution.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the rights field is present and its value explicitly indicates that no restrictions apply to the data (e.g., an open licence, a public domain declaration, or an equivalent unrestricted access statement).

Failure Criterion¶

No dataset distribution contains a rights field, or all present rights values indicate restrictions or are ambiguous about the absence of restrictions.

Tests¶

Test 57: Check rights for statement of no data restrictions

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.restrict.co.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.restrict.co.3",
  "title": {
    "@language": "en",
    "@value": "Statement of No Data Restrictions"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP explicitly states that no access restrictions apply to the dataset."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-rights-no-restrictions"
  },
  "abbreviation": {
    "@value": "data.restrict.co.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "data restrictions"
    },
    {
      "@language": "en",
      "@value": "access rights"
    },
    {
      "@language": "en",
      "@value": "open access"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.restrict.co.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 51: Dataset License Declared¶

Metric ID:: data.lice.co.1
Persistent URI:: https://example.org/metric/data.lice.co.1
Dimension:: Completeness

Title¶

Dataset License

Narrative¶

Verifies that the dataset has a license and which one.

Intended Outcome¶

Determine whether the maDMP declares a license for the dataset through a non-empty license reference field, confirming that users are informed of the legal terms under which the dataset may be accessed and reused.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, a license_ref field is present and non-empty, identifying the licence under which the dataset is made available.

Failure Criterion¶

No dataset distribution contains a license_ref field, or all present values are empty or missing.

Tests¶

Test 58: Check license_ref for dataset licence

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.lice.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.lice.co.1",
  "title": {
    "@language": "en",
    "@value": "Dataset License Declared"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares a license for the dataset distribution via a non-empty license reference field."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-license-ref"
  },
  "abbreviation": {
    "@value": "data.lice.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "dataset licence"
    },
    {
      "@language": "en",
      "@value": "license reference"
    },
    {
      "@language": "en",
      "@value": "open licence"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.lice.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 52: Software Dataset Has a Standardised Machine-Readable License¶

Metric ID:: soft.lice.comp.1
Persistent URI:: https://example.org/metric/soft.lice.comp.1
Dimension:: Compliance

Title¶

Software License

Narrative¶

Verifies that if the dataset is of software type, then the license matches a recognised software license.

Intended Outcome¶

Determine whether the maDMP, for any dataset where type is set to software, declares a license_ref that corresponds to a recognised software licence as listed in the SPDX licence registry at https://spdx.org/licenses/.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with the SPDX licence list at https://spdx.org/licenses/.

Success Criterion¶

For at least one dataset where type is set to software, a license_ref is present and its value matches a recognised software licence identifier from the SPDX licence registry.

Failure Criterion¶

A dataset is typed as software but has no license_ref, or the declared license_ref does not match any recognised software licence in the SPDX registry.

Tests¶

Test 59: Check license_ref against SPDX for software datasets

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/soft.lice.comp.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/soft.lice.comp.1",
  "title": {
    "@language": "en",
    "@value": "Software Dataset Has a Standardised Machine-Readable License"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares an SPDX-compliant license for software datasets."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-license-ref-spdx-software"
  },
  "abbreviation": {
    "@value": "soft.lice.comp.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "software licence"
    },
    {
      "@language": "en",
      "@value": "SPDX"
    },
    {
      "@language": "en",
      "@value": "licence compliance"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/soft.lice.comp.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 53: Data Access Agreements¶

Metric ID:: data.agree.comp.2
Persistent URI:: https://example.org/metric/data.agree.comp.2
Dimension:: Compliance

Title¶

Data Access Agreements

Narrative¶

Verifies that the DMP references any collaboration agreements or Memoranda of Understanding (MoUs) governing data access, ensuring that formal arrangements are documented and traceable.

Intended Outcome¶

Determine whether the maDMP references any data access agreements or Memoranda of Understanding (MoUs), either through the data_access field or through rights entries that indicate the existence of a formal agreement governing data access.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, the data_access field or a rights entry references a formal data access agreement or MoU (e.g., a named agreement, a link to an agreement document, or an explicit mention of collaborative access terms).

Failure Criterion¶

No dataset contains a data_access or rights entry that references a data access agreement or MoU, or all present values are absent, empty, or contain no indication of a formal agreement.

Tests¶

Test 60: Check data_access and rights for access agreements or MoUs

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.agree.comp.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.agree.comp.2",
  "title": {
    "@language": "en",
    "@value": "Data Access Agreements"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP references any collaboration agreements or Memoranda of Understanding governing data access."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-data-access-agreements"
  },
  "abbreviation": {
    "@value": "data.agree.comp.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "data access agreement"
    },
    {
      "@language": "en",
      "@value": "MoU"
    },
    {
      "@language": "en",
      "@value": "access rights"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.agree.comp.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 54: Data Ownership Role Declared¶

Metric ID:: own.co.2
Persistent URI:: https://example.org/metric/own.co.2
Dimension:: Completeness

Title¶

Data Ownership

Narrative¶

Verifies who is the owner of the data and that the field is filled in.

Intended Outcome¶

Determine whether the maDMP declares at least one contributor with a role value of owner, and that the associated contributor fields are non-empty.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one contributor entry is present with a role value of owner and non-empty identifying information (e.g., name, contributor_id, or equivalent), confirming that data ownership has been declared.

Failure Criterion¶

No contributor entry exists with a role of owner, or the ownership field is present but blank.

Tests¶

Test 61: Check contributor.role for data owner

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/own.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/own.co.2",
  "title": {
    "@language": "en",
    "@value": "Data Ownership Role Declared"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares at least one contributor with a data ownership role."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-contributor-role-owner"
  },
  "abbreviation": {
    "@value": "own.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "data ownership"
    },
    {
      "@language": "en",
      "@value": "contributor role"
    },
    {
      "@language": "en",
      "@value": "data stewardship"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/own.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 55: Software Dataset Author Declared¶

Metric ID:: soft.auth.co.3
Persistent URI:: https://example.org/metric/soft.auth.co.3
Dimension:: Completeness

Title¶

Software Author

Narrative¶

Verifies that if the dataset is of software type, then there is at least one contributor as author.

Intended Outcome¶

Determine whether the maDMP, for any dataset where type is set to software, declares at least one contributor with a role indicating authorship.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset where type is set to software, a contributor entry is present with a role value indicating authorship (e.g., author, creator, or equivalent term defined by your project’s controlled vocabulary).

Failure Criterion¶

A dataset is typed as software but has no contributor entry, or no contributor has a role indicating authorship.

Tests¶

Test 62: Check contributor for author role when dataset type is software

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/soft.auth.co.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/soft.auth.co.3",
  "title": {
    "@language": "en",
    "@value": "Software Dataset Author Declared"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares an author contributor for datasets classified as software."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-contributor-author-software"
  },
  "abbreviation": {
    "@value": "soft.auth.co.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "software authorship"
    },
    {
      "@language": "en",
      "@value": "contributor role"
    },
    {
      "@language": "en",
      "@value": "software dataset"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/soft.auth.co.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 56: Ethical Issues Status Declared¶

Metric ID:: ethics.co.1
Persistent URI:: https://example.org/metric/ethics.co.1
Dimension:: Completeness

Title¶

Ethical Issues

Narrative¶

Verifies that the DMP declares a position on whether ethical issues are present in the research, which is a required step in responsible and compliant data management.

Intended Outcome¶

Determine whether the maDMP includes an explicit declaration of whether ethical issues exist, through the ethical_issues_exist field set to a recognised value (yes, no, or unknown).

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

The ethical_issues_exist field is present and contains one of the accepted values: yes, no, or unknown, confirming that the ethical issues status has been explicitly addressed in the DMP.

Failure Criterion¶

The ethical_issues_exist field is absent, empty, or contains a value outside the accepted set of yes, no, or unknown.

Tests¶

Test 63: Check ethical_issues_exist for valid value

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/ethics.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/ethics.co.1",
  "title": {
    "@language": "en",
    "@value": "Ethical Issues Status Declared"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares a position on the existence of ethical issues in the research."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-ethical-issues-exist"
  },
  "abbreviation": {
    "@value": "ethics.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "ethical issues"
    },
    {
      "@language": "en",
      "@value": "ethics declaration"
    },
    {
      "@language": "en",
      "@value": "research ethics"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/ethics.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 57: Ethical Issues and Review¶

Metric ID:: ethics.co.2
Persistent URI:: https://example.org/metric/ethics.co.2
Dimension:: Completeness

Title¶

Ethical Issues and Review

Narrative¶

Verifies that if there are any ethical issues, an ethical review is required and included.

Intended Outcome¶

Determine whether the maDMP, when ethical_issues_exist is set to yes, includes a non-empty ethical_issues_report field referencing the corresponding ethical review.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

If ethical_issues_exist is set to yes, the ethical_issues_report field is present and non-empty, confirming that an ethical review has been conducted and referenced.

Failure Criterion¶

ethical_issues_exist is set to yes but the ethical_issues_report field is absent or empty.

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/ethics.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/ethics.co.2",
  "title": {
    "@language": "en",
    "@value": "Ethical Issues and Review"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP satisfies the criterion: ethical issues and review."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-ethical-issues-report"
  },
  "abbreviation": {
    "@value": "ethics.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "ethical issues"
    },
    {
      "@language": "en",
      "@value": "ethical review"
    },
    {
      "@language": "en",
      "@value": "ethics report"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/ethics.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 58: Justification for Absence of Ethical Issues¶

Metric ID:: ethics.co.3
Persistent URI:: https://example.org/metric/ethics.co.3
Dimension:: Completeness

Title¶

Justification for Absence of Ethical Issues

Narrative¶

Verifies that if there are no ethical issues, then there is a justification.

Intended Outcome¶

Determine whether the maDMP, when ethical_issues_exist is set to no, includes a non-empty ethical_issues_description field providing a justification for the absence of ethical issues.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

If ethical_issues_exist is set to no, the ethical_issues_description field is present and non-empty, providing a justification for why no ethical issues apply.

Failure Criterion¶

ethical_issues_exist is set to no but the ethical_issues_description field is absent or empty, with no justification provided.

Tests¶

Test 64: Check ethical_issues_description is present when ethical_issues_exist is no

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/ethics.co.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/ethics.co.3",
  "title": {
    "@language": "en",
    "@value": "Justification for Absence of Ethical Issues"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP provides a description of ethical issues when the ethical issues field is set to no."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-ethical-issues-description-no"
  },
  "abbreviation": {
    "@value": "ethics.co.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "ethical issues"
    },
    {
      "@language": "en",
      "@value": "ethics justification"
    },
    {
      "@language": "en",
      "@value": "ethics description"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/ethics.co.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 59: Data Access Status Open for the Dataset¶

Metric ID:: data.shar.op.1
Persistent URI:: https://example.org/metric/data.shar.op.1
Dimension:: Openness

Title¶

Data Access Status Open for the Dataset

Narrative¶

Verifies that the access conditions of the data are open.

Intended Outcome¶

Determine whether the maDMP declares the dataset’s access status as open, through a data_access field set to the value open.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, the data_access field is present and set to open, confirming that the data is openly accessible.

Failure Criterion¶

No dataset contains a data_access field, or all present values are set to shared, closed, or any value other than open.

Tests¶

Test 65: Check data_access for open status

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.op.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.op.1",
  "title": {
    "@language": "en",
    "@value": "Data Access Status Open for the Dataset"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares at least one dataset with an open access status."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-data-access-open"
  },
  "abbreviation": {
    "@value": "data.shar.op.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "open access"
    },
    {
      "@language": "en",
      "@value": "data access status"
    },
    {
      "@language": "en",
      "@value": "openness"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.op.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Openness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 60: Data License is Present¶

Metric ID:: data.shar.co.1
Persistent URI:: https://example.org/metric/data.shar.co.1
Dimension:: Completeness

Title¶

Data License is Present

Narrative¶

Verifies that the DMP includes a license declaration for the dataset distribution, confirming that users are informed of the legal terms under which the data may be accessed and reused.

Intended Outcome¶

Determine whether the maDMP includes a distribution entry for the dataset and that the distribution declares a licence through a non-empty license_ref field.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, a distribution entry is present and contains a non-empty license_ref field, confirming that a licence has been declared for the distributed data.

Failure Criterion¶

No dataset contains a distribution entry, or all present distributions lack a license_ref field or contain an empty value.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.co.1",
  "title": {
    "@language": "en",
    "@value": "Data License is Present"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP includes a license declaration for the dataset distribution."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": [
    {
      "@id": "https://example.org/test/T-DCSC-distribution-present"
    },
    {
      "@id": "https://example.org/test/T-DCSC-distribution-license-ref"
    }
  ],
  "abbreviation": {
    "@value": "data.shar.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "data licence"
    },
    {
      "@language": "en",
      "@value": "distribution"
    },
    {
      "@language": "en",
      "@value": "license reference"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 61: Data Restrictions Reference¶

Metric ID:: data.shar.co.2
Persistent URI:: https://example.org/metric/data.shar.co.2
Dimension:: Completeness

Title¶

Data Restrictions Reference

Narrative¶

Verifies that the DMP references any restrictions that apply to data access or sharing, ensuring that limitations on data availability are clearly communicated to users and reviewers.

Intended Outcome¶

Determine whether the maDMP includes a reference to data restrictions through a non-empty rights field, confirming that any limitations on data access or sharing are explicitly documented in the plan.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, a rights field is present and non-empty, confirming that data restrictions or access rights have been referenced.

Failure Criterion¶

No dataset distribution contains a rights field, or all present values are absent or empty.

Tests¶

Test 68: Check rights for data restrictions reference

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.co.2",
  "title": {
    "@language": "en",
    "@value": "Data Restrictions Reference"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP references any restrictions applying to data access or sharing."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-rights-restrictions-reference"
  },
  "abbreviation": {
    "@value": "data.shar.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "data restrictions"
    },
    {
      "@language": "en",
      "@value": "access rights"
    },
    {
      "@language": "en",
      "@value": "distribution"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 62: Dataset License Complies with Funder Requirements¶

Metric ID:: data.shar.comp.1
Persistent URI:: https://example.org/metric/data.shar.comp.1
Dimension:: Compliance

Title¶

Funder’s Data License

Narrative¶

Verifies that the data license is aligned with the funder’s license.

Intended Outcome¶

Determine whether the maDMP declares a dataset distribution licence that complies with Horizon Europe RDM requirements, specifically that license_ref resolves to a CC-BY licence or equivalent.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with Horizon Europe RDM licence requirements.

Success Criterion¶

For at least one dataset distribution in scope, the license_ref field is present and its value corresponds to a CC-BY licence (e.g., https://creativecommons.org/licenses/by/4.0/ or an equivalent CC-BY variant), in alignment with Horizon Europe RDM requirements.

Failure Criterion¶

No dataset distribution contains a license_ref field, or all present license_ref values do not correspond to a CC-BY licence as required by Horizon Europe RDM guidelines.

Tests¶

Test 69: Check distribution license_ref for Horizon Europe CC-BY compliance

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.comp.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.comp.1",
  "title": {
    "@language": "en",
    "@value": "Dataset License Complies with Funder Requirements"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the dataset license declared in the maDMP is compliant with the Horizon Europe CC-BY requirement."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-distribution-license-cc-by"
  },
  "abbreviation": {
    "@value": "data.shar.comp.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "funder licence"
    },
    {
      "@language": "en",
      "@value": "Horizon Europe"
    },
    {
      "@language": "en",
      "@value": "CC-BY"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.comp.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 63: Repository Access Rights Consistency Aligned¶

Metric ID:: data.shar.feas.1
Persistent URI:: https://example.org/metric/data.shar.feas.1
Dimension:: Feasibility

Title¶

Repository Access Rights Consistency Aligned

Narrative¶

Validates that the data has the same access rights with the destination.

Intended Outcome¶

Determine whether the access rights declared for the dataset in the maDMP are consistent with the access policy of the destination repository, confirming that the declared data_access value aligns with the access conditions supported by the destination host.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, the data_access value at dataset level is consistent with the access rights or access policy indicated by the destination host entry in the associated distribution, confirming alignment between declared access and repository capabilities.

Failure Criterion¶

The data_access value at dataset level conflicts with or is not supported by the access policy of the declared destination host, or the relevant fields are absent or empty.

Tests¶

Test 70: Check data_access matches destination host access policy

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.feas.1",
  "title": {
    "@language": "en",
    "@value": "Repository Access Rights Consistency Aligned"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the data access declared in the maDMP matches the access policy of the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-data-access-host-consistency"
  },
  "abbreviation": {
    "@value": "data.shar.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "access rights"
    },
    {
      "@language": "en",
      "@value": "repository consistency"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 64: Repository Data License Aligned with the DMP¶

Metric ID:: data.shar.feas.2
Persistent URI:: https://example.org/metric/data.shar.feas.2
Dimension:: Feasibility

Title¶

Repository Data License Aligned with the DMP

Narrative¶

Validates that the data has the same license with the destination.

Intended Outcome¶

Determine whether the licence declared for the dataset distribution in the maDMP is consistent with the licence supported or required by the destination repository, confirming alignment between distribution.license.license_ref and the destination host’s licence policy.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the license_ref value is present and consistent with the licence policy of the declared destination host, confirming that the data licence and repository licence requirements are aligned.

Failure Criterion¶

The license_ref value is absent, empty, or inconsistent with the licence policy of the declared destination host, indicating a mismatch between the declared data licence and the repository’s requirements.

Tests¶

Test 71: Check distribution license_ref matches destination host licence policy

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.feas.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.feas.2",
  "title": {
    "@language": "en",
    "@value": "Repository Data License Aligned with the DMP"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the license declared in the maDMP matches the license policy of the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-distribution-license-host-alignment"
  },
  "abbreviation": {
    "@value": "data.shar.feas.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "data licence"
    },
    {
      "@language": "en",
      "@value": "repository alignment"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.feas.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 65: Embargo Implementation Alignment¶

Metric ID:: data.shar.feas.3
Persistent URI:: https://example.org/metric/data.shar.feas.3
Dimension:: Feasibility

Title¶

Embargo Implementation Alignment

Narrative¶

Validates that the embargo date of the data matches with that of the destination.

Intended Outcome¶

Determine whether the embargo date declared in the maDMP via distribution.license.start_date is consistent with the embargo policy or availability date supported by the destination repository, confirming alignment between the planned embargo and the destination’s capabilities.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the license.start_date field is present and its value is consistent with the embargo period or availability date supported by the declared destination host.

Failure Criterion¶

The license.start_date field is absent or empty, or its value is inconsistent with the embargo policy of the declared destination host, indicating a mismatch between the planned embargo date and the repository’s supported availability window.

Tests¶

Test 72: Check distribution license.start_date matches destination embargo policy

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.feas.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.feas.3",
  "title": {
    "@language": "en",
    "@value": "Embargo Implementation Alignment"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the embargo period declared in the maDMP is consistent with the embargo policy of the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-distribution-license-start-date-embargo"
  },
  "abbreviation": {
    "@value": "data.shar.feas.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "embargo"
    },
    {
      "@language": "en",
      "@value": "availability date"
    },
    {
      "@language": "en",
      "@value": "repository alignment"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.feas.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 66: Repository Data Restrictions¶

Metric ID:: data.shar.feas.4
Persistent URI:: https://example.org/metric/data.shar.feas.4
Dimension:: Feasibility

Title¶

Repository Data Restrictions

Narrative¶

Validates that the data restrictions match those of the destination.

Intended Outcome¶

Determine whether the data restrictions declared in the maDMP via the rights field are consistent with the restriction policy of the destination repository, confirming alignment between the declared access rights and what the destination host supports.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the rights field is present and its value is consistent with the restriction policy of the declared destination host, confirming that the declared data restrictions are supported by the destination repository.

Failure Criterion¶

The rights field is absent or empty, or its value is inconsistent with the restriction policy of the declared destination host, indicating a mismatch between the declared data restrictions and the repository’s supported access conditions.

Tests¶

Test 73: Check rights matches destination host restriction policy

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.feas.4",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.feas.4",
  "title": {
    "@language": "en",
    "@value": "Repository Data Restrictions"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the access restrictions declared in the maDMP are consistent with the restriction policy of the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-rights-destination-restriction-alignment"
  },
  "abbreviation": {
    "@value": "data.shar.feas.4-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "data restrictions"
    },
    {
      "@language": "en",
      "@value": "access rights"
    },
    {
      "@language": "en",
      "@value": "repository alignment"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.feas.4"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 67: Embargo Declared in the DMP or Repository¶

Metric ID:: data.shar.comp.2
Persistent URI:: https://example.org/metric/data.shar.comp.2
Dimension:: Compliance

Title¶

Embargo License

Narrative¶

Validates that the embargo is not violated against the funder’s policy.

Intended Outcome¶

Determine whether the embargo declared in the maDMP complies with Horizon Europe embargo policy, verified through two checks: that no embargo date exists in the repository host entry, and that distribution.license.start_date is absent or not set in the maDMP, confirming that no non-compliant embargo has been applied.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with Horizon Europe RDM embargo policy.

Success Criterion¶

Both of the following conditions are met: (1) no embargo date field is present in the destination repository host entry, and (2) distribution.license.start_date is absent or not set in the maDMP, confirming that no embargo has been applied in violation of Horizon Europe policy.

Failure Criterion¶

An embargo date is present in the repository host entry, or distribution.license.start_date is set in the maDMP, indicating a potential violation of Horizon Europe embargo policy.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.shar.comp.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.shar.comp.2",
  "title": {
    "@language": "en",
    "@value": "Embargo Declared in the DMP or Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether neither the maDMP nor the destination repository declares an embargo for the dataset."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": [
    {
      "@id": "https://example.org/test/T-DCSC-host-embargo-date-absent"
    },
    {
      "@id": "https://example.org/test/T-DCSC-distribution-license-start-date-absent"
    }
  ],
  "abbreviation": {
    "@value": "data.shar.comp.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "embargo"
    },
    {
      "@language": "en",
      "@value": "Horizon Europe"
    },
    {
      "@language": "en",
      "@value": "licence compliance"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.shar.comp.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 68: Thematic Data Repositories Referenced¶

Metric ID:: repo.co.3
Persistent URI:: https://example.org/metric/repo.co.3
Dimension:: Completeness

Title¶

Thematic Data Repositories Referenced

Narrative¶

Verifies that the repository of each data referenced is thematic.

Intended Outcome¶

Determine whether the maDMP references a thematic repository for each dataset, by matching host.title or host.url against known thematic repositories listed in the OpenAIRE Graph repositories API or another SKG API repository registry.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with the OpenAIRE Graph repositories API or equivalent SKG API repository registry.

Success Criterion¶

For at least one dataset distribution in scope, the host.title or host.url value matches a thematic repository entry in the OpenAIRE Graph repositories API or an equivalent SKG API repository registry, confirming that a domain-specific repository has been designated.

Failure Criterion¶

No dataset distribution contains a host.title or host.url value that matches a thematic repository in the OpenAIRE Graph repositories API or equivalent SKG API registry, or the relevant fields are absent or empty.

Tests¶

Test 76: Check host.title and host.url against thematic repository registries

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.co.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.co.3",
  "title": {
    "@language": "en",
    "@value": "Thematic Data Repositories Referenced"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the repository declared in the maDMP is listed in a recognised thematic repository registry."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-thematic-registry-match"
  },
  "abbreviation": {
    "@value": "repo.co.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "thematic repository"
    },
    {
      "@language": "en",
      "@value": "OpenAIRE"
    },
    {
      "@language": "en",
      "@value": "repository registry"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.co.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 69: Repository Conforms with FAIR Data Principles¶

Metric ID:: repo.comp.2
Persistent URI:: https://example.org/metric/repo.comp.2
Dimension:: Compliance

Title¶

Repository FAIRness Conformation

Narrative¶

Validates that the repository selected for data deposition conforms with FAIR data principles, as verified through recognised registries such as OpenAIRE or FAIRsharing.

Intended Outcome¶

Determine whether the destination repository declared in the maDMP via host is aligned with FAIR data principles, by cross-referencing host.title or host.url against FAIR benchmarks available through OpenAIRE and FAIRsharing.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with OpenAIRE repository benchmarks and the FAIRsharing registry.

Success Criterion¶

For at least one dataset distribution in scope, the host.title or host.url matches a repository entry in OpenAIRE or FAIRsharing that is assessed as conforming with or endorsing FAIR data principles.

Failure Criterion¶

No dataset distribution contains a host.title or host.url that matches a FAIR-assessed repository in OpenAIRE or FAIRsharing, or the relevant fields are absent or empty.

Tests¶

Test 77: Check host against OpenAIRE and FAIRsharing FAIR benchmarks

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.comp.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.comp.2",
  "title": {
    "@language": "en",
    "@value": "Repository Conforms with FAIR Data Principles"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the repository declared in the maDMP conforms with FAIR data principles as verified through recognised registries."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-fair-benchmark"
  },
  "abbreviation": {
    "@value": "repo.comp.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "FAIR data principles"
    },
    {
      "@language": "en",
      "@value": "FAIRsharing"
    },
    {
      "@language": "en",
      "@value": "OpenAIRE"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.comp.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 70: Trusted Repository is Used¶

Metric ID:: repo.comp.3
Persistent URI:: https://example.org/metric/repo.comp.3
Dimension:: Compliance

Title¶

Trusted Repository is Used

Narrative¶

Validates that the repository where data will be deposited is recognised as a trusted repository, as verified through established registry benchmarks.

Intended Outcome¶

Determine whether the destination repository declared in the maDMP via host is included in a recognised trusted repository registry or benchmark, confirming that data will be deposited in a repository meeting established trust criteria.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with a trusted repository registry benchmark.

Success Criterion¶

For at least one dataset distribution in scope, the host.title or host.url matches an entry in a recognised trusted repository registry (e.g., CoreTrustSeal, CLARIN, DINI, or an equivalent trusted repository benchmark), confirming use of a trusted repository.

Failure Criterion¶

No dataset distribution contains a host.title or host.url that matches an entry in a recognised trusted repository registry, or the relevant fields are absent or empty.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.comp.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.comp.3",
  "title": {
    "@language": "en",
    "@value": "Trusted Repository is Used"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the repository declared in the maDMP is recognised as a trusted repository in an established registry."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-trusted-registry"
  },
  "abbreviation": {
    "@value": "repo.comp.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "trusted repository"
    },
    {
      "@language": "en",
      "@value": "CoreTrustSeal"
    },
    {
      "@language": "en",
      "@value": "repository certification"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.comp.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 71: Verification of Back-up Strategy¶

Metric ID:: repo.co.4
Persistent URI:: https://example.org/metric/repo.co.4
Dimension:: Completeness

Title¶

Verification of Back-up Strategy

Narrative¶

Verifies that the repository declared in the DMP has a documented backup strategy, ensuring that data held in the repository is protected against loss.

Intended Outcome¶

Determine whether the maDMP declares a back-up strategy for the destination repository through the host.backup_frequency and host.backup_type fields, confirming that a repository-level back-up plan has been documented.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the host entry contains both a non-empty backup_frequency and a non-empty backup_type field, confirming that a back-up strategy has been declared for the destination repository.

Failure Criterion¶

No dataset distribution contains a host entry with both backup_frequency and backup_type fields present and non-empty, indicating that no back-up strategy has been documented.

Tests¶

Test 79: Check host.backup_frequency and host.backup_type for back-up strategy

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.co.4",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.co.4",
  "title": {
    "@language": "en",
    "@value": "Verification of Back-up Strategy"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the repository declared in the maDMP has a documented backup strategy."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-backup-strategy"
  },
  "abbreviation": {
    "@value": "repo.co.4-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "back-up strategy"
    },
    {
      "@language": "en",
      "@value": "backup frequency"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.co.4"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 72: Certification of Repository¶

Metric ID:: repo.co.5
Persistent URI:: https://example.org/metric/repo.co.5
Dimension:: Completeness

Title¶

Certification of Repository

Narrative¶

Verifies that the repository declared in the DMP holds a recognised certification, such as CoreTrustSeal, confirming that it meets established standards for trustworthy data repositories.

Intended Outcome¶

Determine whether the maDMP declares a certification for the destination repository through a non-empty certified_with field within the host entry, confirming that the repository holds a recognised certification.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the host entry contains a non-empty certified_with field, confirming that a repository certification has been declared.

Failure Criterion¶

No dataset distribution contains a host entry with a certified_with field present and non-empty, indicating that no repository certification has been documented.

Tests¶

Test 80: Check certified_with exists in host

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.co.5",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.co.5",
  "title": {
    "@language": "en",
    "@value": "Certification of Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the repository declared in the maDMP holds a recognised certification such as CoreTrustSeal."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-certified-with"
  },
  "abbreviation": {
    "@value": "repo.co.5-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "repository certification"
    },
    {
      "@language": "en",
      "@value": "certified_with"
    },
    {
      "@language": "en",
      "@value": "repository"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.co.5"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 73: Used Resources for Preservation¶

Metric ID:: repo.co.7
Persistent URI:: https://example.org/metric/repo.co.7
Dimension:: Completeness

Title¶

Used Resources for Preservation

Narrative¶

Verifies that there are resources which accomplish the long-term preservation.

Intended Outcome¶

Determine whether the maDMP includes at least one cost entry whose title or description references long-term preservation, confirming that dedicated resources have been allocated for preservation activities.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one cost entry is present with non-empty currency_code, value, and either a title or description that references preservation, confirming that resources for long-term preservation have been budgeted and described.

Failure Criterion¶

No cost entry is present, or no present cost entry contains a title or description referencing preservation, indicating that no resources for long-term preservation have been declared.

Tests¶

Test 81: Check cost title or description for preservation reference

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.co.7",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.co.7",
  "title": {
    "@language": "en",
    "@value": "Used Resources for Preservation"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP references preservation costs associated with long-term storage in the declared repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-cost-preservation-reference"
  },
  "abbreviation": {
    "@value": "repo.co.7-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "long-term preservation"
    },
    {
      "@language": "en",
      "@value": "cost"
    },
    {
      "@language": "en",
      "@value": "resources"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.co.7"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 74: Repository Policy is Present¶

Metric ID:: repo.co.6
Persistent URI:: https://example.org/metric/repo.co.6
Dimension:: Completeness

Title¶

Repository Policy is Present

Narrative¶

Validates that the repository selected for data deposition has documented policies, as verified through FAIRsharing, ensuring that the repository operates under transparent and accountable governance.

Intended Outcome¶

Determine whether the destination repository declared in the maDMP has associated policies, by extracting the repository identifier from host_id.identifier and host_id.type and cross-referencing against policy records in the FAIRsharing registry.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with the FAIRsharing registry policy records.

Success Criterion¶

For at least one dataset distribution in scope, the host_id.identifier and host_id.type values resolve to a repository entry in FAIRsharing that has one or more associated policies declared, confirming that the selected repository has a documented policy.

Failure Criterion¶

No dataset distribution contains a host_id.identifier or host_id.type that resolves to a FAIRsharing repository entry with associated policies, or the relevant fields are absent or empty.

Tests¶

Test 82: Check host_id against FAIRsharing for repository policy

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.co.6",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.co.6",
  "title": {
    "@language": "en",
    "@value": "Repository Policy is Present"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the repository declared in the maDMP has documented policies as verified through FAIRsharing."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-id-fairsharing-policy"
  },
  "abbreviation": {
    "@value": "repo.co.6-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "repository policy"
    },
    {
      "@language": "en",
      "@value": "FAIRsharing"
    },
    {
      "@language": "en",
      "@value": "host identifier"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.co.6"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 75: Repository Identifier Accuracy¶

Metric ID:: repo.feas.1
Persistent URI:: https://example.org/metric/repo.feas.1
Dimension:: Feasibility

Title¶

Repository Identifier Accuracy

Narrative¶

Validates that the repository matches the destination of the dataset.

Intended Outcome¶

Determine whether the dataset identifier declared in the maDMP via dataset_id resolves to the same repository as the declared destination, by cross-referencing the identifier against its DOI URL to confirm that the dataset is registered at the intended destination repository.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced against DOI URL resolution.

Success Criterion¶

For at least one dataset in scope, the dataset_id value resolves via its DOI URL to the declared destination repository, confirming that the identifier and destination are consistent.

Failure Criterion¶

The dataset_id value is absent or empty, does not resolve via DOI URL, or resolves to a repository other than the declared destination, indicating a mismatch between the dataset identifier and its intended destination.

Tests¶

Test 83: Check dataset_id resolves to declared destination via DOI URL

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.feas.1",
  "title": {
    "@language": "en",
    "@value": "Repository Identifier Accuracy"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the dataset identifier declared in the maDMP resolves to the correct record in the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-id-doi-destination"
  },
  "abbreviation": {
    "@value": "repo.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "dataset identifier"
    },
    {
      "@language": "en",
      "@value": "DOI"
    },
    {
      "@language": "en",
      "@value": "repository destination"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 76: Long-Term Preservation Dataset¶

Metric ID:: repo.feas.2
Persistent URI:: https://example.org/metric/repo.feas.2
Dimension:: Feasibility

Title¶

Long-Term Preservation Dataset

Narrative¶

Validates if there is an intention that the dataset is stored in a long-term storage system.

Intended Outcome¶

Determine whether the maDMP expresses an intention to archive the dataset in a long-term storage system, by verifying that a preservation_statement is declared and that a destination host is identified for the associated distribution.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, a non-empty preservation_statement is present and a destination host entry is declared, confirming that there is an expressed intention to archive the dataset in a long-term storage repository.

Failure Criterion¶

No dataset distribution contains both a non-empty preservation_statement and a declared host entry, indicating that no intention to store the dataset in a long-term storage system has been documented.

Tests¶

Test 84: Check preservation_statement and host for long-term storage intention

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.feas.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.feas.2",
  "title": {
    "@language": "en",
    "@value": "Long-Term Preservation Dataset"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares an intention to preserve the dataset long-term in a suitable repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-preservation-statement-host"
  },
  "abbreviation": {
    "@value": "repo.feas.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "long-term preservation"
    },
    {
      "@language": "en",
      "@value": "preservation statement"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.feas.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 77: Dataset Characteristics Are Compatible with the Repository¶

Metric ID:: repo.feas.4
Persistent URI:: https://example.org/metric/repo.feas.4
Dimension:: Feasibility

Title¶

Repository Specificities

Narrative¶

Validates if the selected repository is appropriate for the characteristics and intended use of the dataset.

Intended Outcome¶

Determine whether the destination repository declared in the maDMP is appropriate for the dataset, by verifying that the dataset’s keyword and language values are compatible with the characteristics and scope supported by the destination repository, cross-referenced against Zenodo metadata.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with Zenodo repository metadata.

Success Criterion¶

For at least one dataset in scope, both dataset.keyword values match keywords supported or indexed in Zenodo, and dataset.language matches a language supported by Zenodo, confirming that the repository is appropriate for the dataset’s characteristics.

Failure Criterion¶

No dataset contains keyword or language values that match the characteristics supported by the declared destination repository in Zenodo, or the relevant fields are absent or empty.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/repo.feas.4",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/repo.feas.4",
  "title": {
    "@language": "en",
    "@value": "Dataset Characteristics Are Compatible with the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the dataset characteristics declared in the maDMP are compatible with the specific requirements of the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": [
    {
      "@id": "https://example.org/test/T-DCSC-dataset-keyword-zenodo"
    },
    {
      "@id": "https://example.org/test/T-DCSC-dataset-language-zenodo"
    }
  ],
  "abbreviation": {
    "@value": "repo.feas.4-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "repository appropriateness"
    },
    {
      "@language": "en",
      "@value": "Zenodo"
    },
    {
      "@language": "en",
      "@value": "dataset characteristics"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/repo.feas.4"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 78: Data External Resources Included in the DMP¶

Metric ID:: data.exteresource.co.1
Persistent URI:: https://example.org/metric/data.exteresource.co.1
Dimension:: Completeness

Title¶

Data External Resources Included in the DMP

Narrative¶

Verifies that the DMP includes the used external resources of the data.

Intended Outcome¶

Determine whether the maDMP references external resources associated with the data through the related_identifier.identifier field, confirming that any external resources used by or related to the dataset have been declared in the DMP.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, a related_identifier entry is present containing a non-empty identifier field, confirming that external resources have been referenced in the DMP.

Failure Criterion¶

No dataset contains a related_identifier entry with a non-empty identifier field, indicating that no external resources have been declared in the DMP.

Tests¶

Test 88: Check related_identifier.identifier for external resources

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.exteresource.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.exteresource.co.1",
  "title": {
    "@language": "en",
    "@value": "Data External Resources Included in the DMP"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP references external datasets or resources via related identifiers."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-related-identifier-external-resources"
  },
  "abbreviation": {
    "@value": "data.exteresource.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "external resources"
    },
    {
      "@language": "en",
      "@value": "related identifier"
    },
    {
      "@language": "en",
      "@value": "completeness"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.exteresource.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 79: Metadata Standard Specified in the DMP¶

Metric ID:: data.exteresource.co.2
Persistent URI:: https://example.org/metric/data.exteresource.co.2
Dimension:: Completeness

Title¶

Metadata Standard Specified in the DMP

Narrative¶

Verifies that a specific metadata standard or format is mentioned for documenting the dataset.

Intended Outcome¶

Determine whether the maDMP declares a metadata standard or format for the dataset through the related_identifier.metadata_scheme, related_identifier.scheme_type, and related_identifier.scheme_uri fields, confirming that the documentation standard applied to the dataset has been identified.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset in scope, a related_identifier entry is present containing non-empty values for metadata_scheme, scheme_type, and scheme_uri, confirming that a metadata standard or format has been specified in the DMP.

Failure Criterion¶

No dataset contains a related_identifier entry with non-empty metadata_scheme, scheme_type, and scheme_uri fields, indicating that no metadata standard or format has been declared in the DMP.

Tests¶

Test 89: Check related_identifier for metadata standard fields

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.exteresource.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.exteresource.co.2",
  "title": {
    "@language": "en",
    "@value": "Metadata Standard Specified in the DMP"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP references external metadata standards via related identifiers."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-related-identifier-metadata-standard"
  },
  "abbreviation": {
    "@value": "data.exteresource.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "metadata standard"
    },
    {
      "@language": "en",
      "@value": "metadata scheme"
    },
    {
      "@language": "en",
      "@value": "completeness"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.exteresource.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 80: Resolvable External Resources¶

Metric ID:: data.exteresource.feas.1
Persistent URI:: https://example.org/metric/data.exteresource.feas.1
Dimension:: Feasibility

Title¶

Resolvable External Resources

Narrative¶

Validates that all included external URLs are valid and resolvable.

Intended Outcome¶

Determine whether the external URLs declared in the maDMP are valid and resolvable, confirming that referenced external resources are accessible and that the links included in the DMP are functional.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one URL present in the maDMP, the URL is syntactically valid and resolves successfully to an accessible resource, confirming that at least one external resource link is functional.

Failure Criterion¶

All URLs present in the maDMP are either syntactically invalid, unreachable, or return error responses, indicating that no declared external resource link is resolvable.

Tests¶

Test 90: Check URLs in maDMP are valid and resolvable

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.exteresource.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.exteresource.feas.1",
  "title": {
    "@language": "en",
    "@value": "Resolvable External Resources"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the URLs declared as related identifiers in the maDMP are valid and resolvable."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-url-resolvable"
  },
  "abbreviation": {
    "@value": "data.exteresource.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "resolvable URLs"
    },
    {
      "@language": "en",
      "@value": "external resources"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.exteresource.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 81: OpenAIRE Mentioned Dataset Validation¶

Metric ID:: data.exteresource.feas.2
Persistent URI:: https://example.org/metric/data.exteresource.feas.2
Dimension:: Feasibility

Title¶

OpenAIRE Mentioned Dataset Validation

Narrative¶

Validates that datasets mentioned in the DMP are found in OpenAIRE via the skg-if endpoint.

Intended Outcome¶

Determine whether the datasets referenced in the maDMP can be located in OpenAIRE through the SKG-IF API, by cross-referencing dataset_id.identifier, dataset_id.type, dataset.title, and dataset.type against OpenAIRE records, confirming that the mentioned datasets are registered and discoverable.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with the OpenAIRE SKG-IF API.

Success Criterion¶

For at least one dataset in scope, the combination of dataset_id.identifier, dataset_id.type, dataset.title, and dataset.type resolves to a matching record in the OpenAIRE SKG-IF API, confirming that the dataset is registered and findable in OpenAIRE.

Failure Criterion¶

No dataset in scope produces a matching record in the OpenAIRE SKG-IF API using the declared dataset_id.identifier, dataset_id.type, dataset.title, or dataset.type, or the relevant fields are absent or empty.

Tests¶

Test 91: Check dataset fields against OpenAIRE SKG-IF API

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.exteresource.feas.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.exteresource.feas.2",
  "title": {
    "@language": "en",
    "@value": "OpenAIRE Mentioned Dataset Validation"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the datasets referenced in the maDMP can be found and validated through the OpenAIRE API."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-openaire-skg-if"
  },
  "abbreviation": {
    "@value": "data.exteresource.feas.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "OpenAIRE"
    },
    {
      "@language": "en",
      "@value": "SKG-IF"
    },
    {
      "@language": "en",
      "@value": "dataset validation"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.exteresource.feas.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 82: Contributor Roles Follow CRediT Taxonomy¶

Metric ID:: data.exteresource.feas.3
Persistent URI:: https://example.org/metric/data.exteresource.feas.3
Dimension:: Feasibility

Title¶

Used Taxonomy

Narrative¶

Validates that the published dataset acknowledges contributors using the CRediT taxonomy.

Intended Outcome¶

Determine whether the maDMP declares contributor roles using the CRediT (Contributor Roles Taxonomy) taxonomy, by cross-referencing the contributor field values against recognised CRediT role terms, confirming that contributor acknowledgement follows a standardised taxonomy.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with the CRediT taxonomy.

Success Criterion¶

For at least one dataset in scope, a contributor entry is present whose role value matches a recognised term from the CRediT taxonomy, confirming that contributor roles have been declared using the standardised taxonomy.

Failure Criterion¶

No dataset contains a contributor entry whose role value matches a CRediT taxonomy term, or the contributor field is absent or empty.

Tests¶

Test 92: Check contributor roles against CRediT taxonomy

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.exteresource.feas.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.exteresource.feas.3",
  "title": {
    "@language": "en",
    "@value": "Contributor Roles Follow CRediT Taxonomy"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the contributor roles declared in the maDMP are terms from the CRediT taxonomy."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-contributor-credit-taxonomy"
  },
  "abbreviation": {
    "@value": "data.exteresource.feas.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "CRediT taxonomy"
    },
    {
      "@language": "en",
      "@value": "contributor roles"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.exteresource.feas.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 83: Repository Supports Persistent Identifiers for Datasets¶

Metric ID:: data.pid.cov.1
Persistent URI:: https://example.org/metric/data.pid.cov.1
Dimension:: Coverage

Title¶

Dataset PID

Narrative¶

Verifies that the destination repository declared in the DMP supports a persistent identifier system, ensuring that the dataset will receive a stable and citable identifier upon deposit.

Intended Outcome¶

Determine whether the maDMP declares a persistent identifier system for the dataset’s destination repository through the host.pid_system field, confirming that a PID system is in place to ensure persistent identification of the dataset.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

For at least one dataset distribution in scope, the host entry contains a non-empty pid_system field, confirming that a persistent identifier system has been declared for the destination repository.

Failure Criterion¶

No dataset distribution contains a host entry with a non-empty pid_system field, indicating that no persistent identifier system has been declared.

Tests¶

Test 93: Check host.pid_system for PID declaration

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.pid.cov.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.pid.cov.1",
  "title": {
    "@language": "en",
    "@value": "Repository Supports Persistent Identifiers for Datasets"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the destination repository declared in the maDMP supports a persistent identifier system."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-pid-system"
  },
  "abbreviation": {
    "@value": "data.pid.cov.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "persistent identifier"
    },
    {
      "@language": "en",
      "@value": "PID"
    },
    {
      "@language": "en",
      "@value": "coverage"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.pid.cov.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 84: Trusted Repository Referenced¶

Metric ID:: data.pid.cov.2
Persistent URI:: https://example.org/metric/data.pid.cov.2
Dimension:: Coverage

Title¶

Trusted Repository Referenced

Narrative¶

Verifies that the repository where the data will be deposited is listed in a trusted registry and a valid link to the repository is provided in the DMP.

Intended Outcome¶

Determine whether the maDMP references a trusted repository for data deposition, verified through two checks: that the repository is listed in a trusted registry via the certified_with field, and that a valid resolvable link to the repository is provided via host_id.identifier and host_id.type.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

Both of the following conditions are met: (1) at least one distribution’s host entry contains a non-empty certified_with field matching a trusted registry, and (2) at least one distribution’s host_id.identifier and host_id.type values provide a valid and resolvable link to the repository.

Failure Criterion¶

Either the certified_with field is absent or does not match a trusted registry, or host_id.identifier and host_id.type are absent, empty, or do not resolve to a valid repository link.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.pid.cov.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.pid.cov.2",
  "title": {
    "@language": "en",
    "@value": "Trusted Repository Referenced"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the repository referenced in the maDMP is listed in a trusted repository registry with a valid resolvable link."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": [
    {
      "@id": "https://example.org/test/T-DCSC-certified-with-trusted-registry"
    },
    {
      "@id": "https://example.org/test/T-DCSC-host-id-valid-link"
    }
  ],
  "abbreviation": {
    "@value": "data.pid.cov.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "trusted repository"
    },
    {
      "@language": "en",
      "@value": "repository link"
    },
    {
      "@language": "en",
      "@value": "coverage"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.pid.cov.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Coverage"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 85: Dataset PID System in the DMP Matches the Repository¶

Metric ID:: data.pid.feas.1
Persistent URI:: https://example.org/metric/data.pid.feas.1
Dimension:: Feasibility

Title¶

Repository PID

Narrative¶

Validates that the persistent identifier system declared for the destination repository in the DMP matches the identifier system actually provided by that repository, confirming that PIDs will be issued as expected.

Intended Outcome¶

Determine whether the PID system declared for the destination repository in the maDMP via host.pid_system is consistent with the PID system provided by the repository, cross-referenced against Zenodo’s DOI assignment, confirming that the declared PID system is actually supported by the destination.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with Zenodo DOI metadata.

Success Criterion¶

For at least one dataset distribution in scope, the host.pid_system value matches the PID system supported by the declared destination repository as verified in Zenodo (e.g., DOI assignment), confirming that the repository provides the declared PID type.

Failure Criterion¶

The host.pid_system value is absent, empty, or does not match the PID system supported by the declared destination repository in Zenodo, indicating a mismatch between the declared and actual PID provision.

Tests¶

Test 96: Check host.pid_system matches destination PID system in Zenodo

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.pid.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.pid.feas.1",
  "title": {
    "@language": "en",
    "@value": "Dataset PID System in the DMP Matches the Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the PID system declared in the maDMP matches the identifier system provided by the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-host-pid-system-zenodo"
  },
  "abbreviation": {
    "@value": "data.pid.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "persistent identifier"
    },
    {
      "@language": "en",
      "@value": "Zenodo"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.pid.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 86: Dataset Persistent Identifier Resolves Successfully¶

Metric ID:: data.pid.feas.3
Persistent URI:: https://example.org/metric/data.pid.feas.3
Dimension:: Feasibility

Title¶

PIDs can be Resolved

Narrative¶

Validates that the PID in the repository is valid and resolvable.

Intended Outcome¶

Determine whether the persistent identifier declared for the dataset in the maDMP via dataset_id.identifier and dataset_id.type is valid and resolvable, by cross-referencing the identifier against its DOI URL in Zenodo, confirming that the PID leads to an accessible and valid resource.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with Zenodo DOI URL resolution.

Success Criterion¶

For at least one dataset in scope, the dataset_id.identifier value of type DOI resolves successfully via its DOI URL in Zenodo to an accessible resource, confirming that the PID is valid and resolvable.

Failure Criterion¶

The dataset_id.identifier value is absent, empty, not of a resolvable type, or fails to resolve via its DOI URL in Zenodo, indicating that the declared PID is invalid or not resolvable.

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/data.pid.feas.3",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/data.pid.feas.3",
  "title": {
    "@language": "en",
    "@value": "Dataset Persistent Identifier Resolves Successfully"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the dataset identifier declared in the maDMP resolves successfully via its DOI URL."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-dataset-id-doi-zenodo-resolve"
  },
  "abbreviation": {
    "@value": "data.pid.feas.3-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "persistent identifier"
    },
    {
      "@language": "en",
      "@value": "DOI resolution"
    },
    {
      "@language": "en",
      "@value": "Zenodo"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/data.pid.feas.3"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 87: Research Data Management Roles Declared¶

Metric ID:: role.co.1
Persistent URI:: https://example.org/metric/role.co.1
Dimension:: Completeness

Title¶

RDM Roles

Narrative¶

Verifies that the DMP identifies all contributors involved in research data management, including their names, roles, and contact information, ensuring clear accountability throughout the project.

Intended Outcome¶

Determine whether the maDMP declares contributor information including name, role, and contact details through the dmp.contributor.name, dmp.contributor.role, and dmp.contributor.contact fields, confirming that the roles and identities of all contributors to the data management plan have been documented.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one contributor entry is present at DMP level containing non-empty values for name, role, and contact, confirming that contributor roles have been fully declared in the DMP.

Failure Criterion¶

No contributor entry is present at DMP level, or no present entry contains non-empty values for all three of name, role, and contact, indicating that contributor role information is incomplete or absent.

Tests¶

Test 97: Check dmp.contributor name, role, and contact

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/role.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/role.co.1",
  "title": {
    "@language": "en",
    "@value": "Research Data Management Roles Declared"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP declares all contributors with their names, roles, and contact information."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-contributor-name-role-contact"
  },
  "abbreviation": {
    "@value": "role.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "contributor roles"
    },
    {
      "@language": "en",
      "@value": "RDM roles"
    },
    {
      "@language": "en",
      "@value": "completeness"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/role.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 88: DMP Validation by Data Steward¶

Metric ID:: dmp.valid.co.2
Persistent URI:: https://example.org/metric/dmp.valid.co.2
Dimension:: Completeness

Title¶

DMP Validation by Data Steward

Narrative¶

Verifies that the DMP has been reviewed and approved by at least one Data Steward, confirming that a qualified professional has validated the data management plan.

Intended Outcome¶

Determine whether the maDMP includes at least one contributor whose role is declared as Data Steward, confirming that a qualified Data Steward has been assigned to and is accountable for the DMP.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one contributor entry is present at DMP level with a role value equal to Data Steward, confirming that DMP validation by a Data Steward has been declared.

Failure Criterion¶

No contributor entry is present with a role value of Data Steward, indicating that no Data Steward has been assigned to validate the DMP.

Tests¶

Test 98: Check dmp.contributor.role for Data Steward

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/dmp.valid.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/dmp.valid.co.2",
  "title": {
    "@language": "en",
    "@value": "DMP Validation by Data Steward"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether at least one contributor in the maDMP holds the role of Data Steward."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-contributor-role-data-steward"
  },
  "abbreviation": {
    "@value": "dmp.valid.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "Data Steward"
    },
    {
      "@language": "en",
      "@value": "DMP validation"
    },
    {
      "@language": "en",
      "@value": "completeness"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/dmp.valid.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 89: Contributors and Organisations PIDs¶

Metric ID:: role.pid.co.1
Persistent URI:: https://example.org/metric/role.pid.co.1
Dimension:: Completeness

Title¶

Contributors and Organisations PIDs

Narrative¶

Verifies that the DMP includes the contributors and their affiliation PIDs.

Intended Outcome¶

Determine whether the maDMP declares persistent identifiers for both contributors and their affiliated organisations through the contributor.contributor_id and contributor.affiliation.affiliation_id fields, confirming that all contributors and their institutional affiliations are persistently identified.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one contributor entry is present containing both a non-empty contributor_id and a non-empty affiliation.affiliation_id, confirming that persistent identifiers for contributors and their organisations have been declared in the DMP.

Failure Criterion¶

No contributor entry contains both a non-empty contributor_id and a non-empty affiliation.affiliation_id, indicating that contributor and/or organisational PIDs are absent or incomplete.

Tests¶

Test 99: Check contributor_id and affiliation.affiliation_id for PIDs

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/role.pid.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/role.pid.co.1",
  "title": {
    "@language": "en",
    "@value": "Contributors and Organisations PIDs"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP includes persistent identifiers for contributors and their affiliated organisations."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-contributor-id-affiliation-id"
  },
  "abbreviation": {
    "@value": "role.pid.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "contributor PID"
    },
    {
      "@language": "en",
      "@value": "affiliation PID"
    },
    {
      "@language": "en",
      "@value": "completeness"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/role.pid.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 90: Referenced RDM Roles¶

Metric ID:: role.feas.1
Persistent URI:: https://example.org/metric/role.feas.1
Dimension:: Feasibility

Title¶

Referenced RDM Roles

Narrative¶

Validates that the contributors and their roles are included in the destination.

Intended Outcome¶

Determine whether the contributors and their roles declared in the maDMP via dmp.contributor.name, dmp.contributor.role, and dmp.contributor.contact are reflected in the destination, by cross-referencing against the destination’s contributors.name and contributors.type fields, confirming that contributor information is consistently represented across the DMP and its destination.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with destination contributor metadata.

Success Criterion¶

For at least one contributor declared in the maDMP, the dmp.contributor.name, dmp.contributor.role, and dmp.contributor.contact values are matched by corresponding contributors.name and contributors.type entries in the destination, confirming that contributor roles are consistently referenced.

Failure Criterion¶

No contributor declared in the maDMP via dmp.contributor.name, dmp.contributor.role, and dmp.contributor.contact can be matched against contributors.name and contributors.type in the destination, or the relevant fields are absent or empty in either source.

Tests¶

Test 100: Check dmp.contributor fields against destination contributors

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/role.feas.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/role.feas.1",
  "title": {
    "@language": "en",
    "@value": "Referenced RDM Roles"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the contributor roles declared in the maDMP are reflected in the destination repository record."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-contributor-fields-destination"
  },
  "abbreviation": {
    "@value": "role.feas.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "contributor roles"
    },
    {
      "@language": "en",
      "@value": "RDM roles"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/role.feas.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 91: Data Steward Contribution Reflected in the Destination Repository¶

Metric ID:: role.feas.2
Persistent URI:: https://example.org/metric/role.feas.2
Dimension:: Feasibility

Title¶

Final Data Steward Validation

Narrative¶

Validates that the DMP is approved in the destination by Data Stewards.

Intended Outcome¶

Determine whether the Data Steward role declared in the maDMP via dmp.contributor.role is reflected in the destination through a corresponding contributors.type value of Other, confirming that the Data Steward’s contribution has been carried through to the destination record.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with destination contributor metadata.

Success Criterion¶

At least one contributor in the maDMP has a role value of Data Steward, and a corresponding entry with contributors.type equal to Other is present in the destination, confirming that the Data Steward’s contribution is referenced in the destination.

Failure Criterion¶

No contributor in the maDMP has a role value of Data Steward, or no corresponding contributors.type of Other is present in the destination, indicating that the Data Steward validation is not reflected in the destination record.

Tests¶

Test 101: Check Data Steward role in maDMP against contributors.type Other in destination

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/role.feas.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/role.feas.2",
  "title": {
    "@language": "en",
    "@value": "Data Steward Contribution Reflected in the Destination Repository"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the Data Steward contribution declared in the maDMP is referenced in the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-data-steward-role-destination-other"
  },
  "abbreviation": {
    "@value": "role.feas.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "Data Steward"
    },
    {
      "@language": "en",
      "@value": "DMP validation"
    },
    {
      "@language": "en",
      "@value": "feasibility"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/role.feas.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Feasibility"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 92: Contributor and Organisation PIDs Match the Destination Repository¶

Metric ID:: cost.comp.1
Persistent URI:: https://example.org/metric/cost.comp.1
Dimension:: Compliance

Title¶

Repository Cost

Narrative¶

Verifies that the costs declared in the DMP for the destination repository are consistent with the actual pricing of that repository, ensuring that the budget is accurate and realistic.

Intended Outcome¶

Determine whether the cost declared in the maDMP for the destination repository is consistent with the actual cost of the repository, confirming that the budgeted repository cost accurately reflects the repository’s pricing.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format, cross-referenced with repository cost information.

Success Criterion¶

At least one cost entry is present in the maDMP whose declared values are consistent with the actual cost associated with the destination repository, confirming that the repository cost has been accurately represented in the DMP.

Failure Criterion¶

No cost entry is present in the maDMP, or the declared cost values do not match the actual cost of the destination repository, indicating a discrepancy between the budgeted and actual repository cost.

Tests¶

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/cost.comp.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/cost.comp.1",
  "title": {
    "@language": "en",
    "@value": "Repository Cost Verified Against Actual Pricing"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the repository cost declared in the maDMP is consistent with the actual pricing of the destination repository."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-cost-repository"
  },
  "abbreviation": {
    "@value": "cost.comp.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "repository cost"
    },
    {
      "@language": "en",
      "@value": "cost"
    },
    {
      "@language": "en",
      "@value": "compliance"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/cost.comp.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Compliance"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 93: DMP Includes a Budget for Personnel and Monetary Resources¶

Metric ID:: cost.co.1
Persistent URI:: https://example.org/metric/cost.co.1
Dimension:: Completeness

Title¶

DMP Budget Specifications

Narrative¶

Verifies that the DMP includes the budget for PMs and monetary resources.

Intended Outcome¶

Determine whether the maDMP declares budget information covering both personnel months and monetary resources through the cost field, confirming that the financial planning for the data management activities has been documented in the DMP.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

At least one cost entry is present at DMP level containing non-empty values for currency_code, value, title, and description, confirming that budget specifications for the DMP have been declared.

Failure Criterion¶

No cost entry is present at DMP level, or no present entry contains the required non-empty fields, indicating that budget information for the DMP is absent or incomplete.

Tests¶

Test 104: Check cost fields for budget specification

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/cost.co.1",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/cost.co.1",
  "title": {
    "@language": "en",
    "@value": "DMP Includes a Budget for Personnel and Monetary Resources"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP includes a budget declaration covering both personnel and monetary resources."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-cost-budget-specification"
  },
  "abbreviation": {
    "@value": "cost.co.1-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "budget"
    },
    {
      "@language": "en",
      "@value": "cost"
    },
    {
      "@language": "en",
      "@value": "completeness"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/cost.co.1"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}

Metric 94: DMP States No Additional RDM Resources Are Required¶

Metric ID:: cost.co.2
Persistent URI:: https://example.org/metric/cost.co.2
Dimension:: Completeness

Title¶

No Extra RDM Costs

Narrative¶

Verifies that the DMP states that no additional resources are needed.

Intended Outcome¶

Determine whether the maDMP explicitly declares that no additional resources beyond those already budgeted are required for data management activities, confirming that the absence of extra RDM costs has been documented in the DMP.

Applies To¶

Machine-actionable Data Management Plan (maDMP) in JSON format.

Success Criterion¶

The cost field in the maDMP is present and its content explicitly states that no additional resources are needed, or the cost entries collectively confirm that all required resources have been accounted for with no outstanding budget gaps declared.

Failure Criterion¶

The cost field is absent, empty, or does not contain any indication that no additional resources are required, indicating that the DMP does not address the absence of extra RDM costs.

Tests¶

Test 105: Check cost in maDMP for no additional resources statement

JSON-LD¶

{
  "@context": "https://w3id.org/ftr/context",
  "@id": "https://example.org/metric/cost.co.2",
  "@type": "dqv:Metric",
  "identifier": "https://example.org/metric/cost.co.2",
  "title": {
    "@language": "en",
    "@value": "DMP States No Additional RDM Resources Are Required"
  },
  "description": {
    "@language": "en",
    "@value": "Checks whether the maDMP explicitly states that no additional resources beyond those already budgeted are required."
  },
  "license": {
    "@id": "http://creativecommons.org/licenses/by/4.0/"
  },
  "dcterms:creator": [
    {
      "@id": "https://example.org/organization"
    }
  ],
  "dcterms:publisher": {
    "@id": "https://example.org/organization"
  },
  "hasImplementation": {
    "@id": "https://example.org/test/T-DCSC-cost-no-additional-resources"
  },
  "abbreviation": {
    "@value": "cost.co.2-M"
  },
  "contactPoint": {
    "@id": "https://example.org/contact"
  },
  "keyword": [
    {
      "@language": "en",
      "@value": "no additional resources"
    },
    {
      "@language": "en",
      "@value": "RDM costs"
    },
    {
      "@language": "en",
      "@value": "completeness"
    },
    {
      "@language": "en",
      "@value": "maDMP"
    }
  ],
  "landingPage": {
    "@id": "https://example.org/metric/cost.co.2"
  },
  "version": {
    "@value": "0.0.1"
  },
  "inDimension": {
    "@value": "Completeness"
  },
  "isApplicableFor": {
    "@id": "https://schema.org/Dataset"
  },
  "hasBenchmark": {
    "@id": "https://example.org/benchmark/default"
  },
  "status": {
    "@language": "en",
    "@value": "Draft"
  },
  "supportedBy": {
    "@id": "https://example.org/project"
  }
}