Total Published Datasets
-
Compliance Overview
Total Published Datasets reflects unique published datasets within the UM DataverseNL hierarchy.
Most Frequent Missing Requirement
-
Most Requirements Met
Share of datasets meeting most requirements (5/6 and 6/6).
Some Requirements Met
Share of datasets meeting half of the requirements.
What is the average number of metadata items meeting the requirements? (out of 6)
How many datasets are meeting the requirements across metadata items?
Datasets Overview
| Title | Faculty | Subdataverse | Publication Date | Requirements Met | Missing Metadata Requirements | Link |
|---|
How the metadata requirements are assessed?
The requirements are derived from the UM DataverseNL Operational Guidelines. Each requirement is operationalised as a metadata check and the required information is checked from available metadata items.
Licence requirement
- The dashboard checks whether the dataset has a non-empty licence other than CC0-1.0.
- This operationalises the local expectation that datasets use CC-BY derivatives unless another permitted condition applies. CC0 are not ideal because does not require the end user to attribute the authors.
- Based on guideline point 12.1.
Restricted data requirement
- The dashboard checks whether custom terms or access conditions are present when at least one file has restricted access.
- Restricted data require clear access conditions so that users and curators understand how access is governed. This is important for cases where (pseudo)anonymized data is shared.
- Based on guideline points 12.2 and 12.3.
UM service contact requirement
- The dashboard checks whether at least one UM service contact (email) is present among the dataset contacts.
- Important: Do not confuse "contact(s)" with "author(s)". Authors might be listed as contacts, but not necessarily.
- This supports continuity of responsibility when individual depositors are no longer available. Examples: "RDM support FASoS", "UM Dataverse Admin", and "faculty data manager FPN", "SHE data", etc.
- Based on guideline point 12.5.
ORCID requirement
- The dashboard checks whether at least one author has an ORCID.
- This supports discoverability, attribution, and programmatic linking to the UM CRIS system (Pure) for research outputs.
Description requirement
- The dashboard checks whether a dataset description is present.
- A description helps users understand the content, context, and purpose of the data publicationm which sometimes is different from the scientific article.
- Based on section 9 of the guidelines.
Keywords requirement
- The dashboard checks whether at least one keyword is present.
- Keywords support discovery, indexing, and reuse of the data publication.
- Based on section 9 of the guidelines.
- Ideally keywords are based on controlled vocabularies. RDM from KU Leuven has a good explanation of how to use them.
UM DataverseNL Operational Guidelines Download
About this dashboard
Note: This dashboard is not based on live data, it uses a static metadata import (which is refreshed monthly). More info contact ub-dataverse@maastrichtuniversity.nl
The current metadata scope considers the Maastricht University DataverseNL instance . More information about the UM Dataverse is available at DataverseNL support , as well as the Terms of Use and Operational Guidelines . More requirements or checks can be considered in the future. However only metadata checks that can reasonably be assessed from available Dataverse attributes can be included.
This dashboard supports curator monitoring and service improvement, in line with the Research Data Management Code of Conduct . It does not replace legal assessment, privacy review, ethical assessment, or disciplinary data stewardship judgement.
If you are a researcher, please visit the My Research Information Profile application to curate your research outputs and datasets.
This software is released under the MIT License. Repository: MaastrichtU-Library/dataverse-compliance-dashboard . Issues can be submitted via GitHub issues .