DataverseNL Metadata Compliance Dashboard 📊

This dashboard monitors compliance with selected metadata requirements derived from the UM DataverseNL Operational Guidelines, using the metadata items available in Dataverse records.

✨ Access the DataverseNL Metadata Compliance Dashboard ✨

How the metadata requirements are assessed ✅

1. CC-BY licence for non restricted data → Based on guideline point 12.1. For the current implementation, this requirement is assessed by checking that the dataset has a non-empty licence other than CC0-1.0.
2. Custom terms for restricted data → Based on guideline points 12.2–12.3.
3. UM service contact is present → Based on guideline point 12.5. Because the crawler export does not expose dataset contact emails, this requirement is assessed from approved service-contact labels in the dataset contact metadata. Current labels are: Data Management Law, Data steward SBE, Datamanagement FPN, Dataverse Support Contact, DataverseNL Team, DataverseNL UM contact, DataverseNL UM-UL team, Faculty Data Manager, Faculty Data Manager FPN, FASoS Data Steward, ICIS office, Law and Tech Lab, Law Faculty Data Management Services, LAW RDM support, RDM Services, RDM Sevices, RDM support FASoS, RDM support LAW, rdm-roa, rdm-sbe, SBE Faculty Data Steward, SBE RDM, SBE Research Data Management, SBE Research Data Management (Maastricht University), Shedata, UB Dataverse, UB Dataverse support, UM Admin, UM Dataverse Admin, UM Dataverse Support, and UM DataverseNL.
4. At least one author has an ORCID → It is required for discoverability and be programmatically linked to the CRIS system for research outputs at UM.
5. Description is present → Based on section 9 of the guidelines.
6. Keywords are present → Based on section 9 of the guidelines.

View the UM DataverseNL Operational Guidelines

Data source and architecture 🧩

• The browser app does not query Dataverse live. It reads the latest normalized dashboard import prepared by the background metadata workflow.
• The metadata import is gathered from the DataverseNL instance using scholarsportal/dataverse-metadata-crawler.
• The crawler exports can be placed in the local, git-ignored data/raw/ directory, and the transformation scripts in scripts/ convert that output into dashboard-ready JSON for the dashboard import.
• There is a service-contact allowlist audit that can be exported locally. The generated CSV is in the git-ignored data/ directory.

python3 scripts/export_service_contact_audit.py data/datasets.json data/service_contact_allowlist_audit.csv

The workflow is kept separate:

Dataverse API / crawler export
        ↓
raw metadata in data/raw/
        ↓
scripts/transform_crawler_output.py
        ↓
normalized data/datasets.json
        ↓
static dashboard on GitHub Pages

Running locally 🚀

Clone the repository and serve it as a small static site:

git clone https://github.com/MaastrichtU-Library/dataverse-compliance-dashboard.git
cd dataverse-compliance-dashboard
python -m http.server 8000

Then open http://localhost:8000.
Note: If you run it from localhost or 127.0.0.1, the app falls back to data/datasets.json for local development.

Citation 📚

If you use this software in research, please cite the repository metadata in CITATION.cff.

Hernandez Serrano, P. V. (2026). DataverseNL Metadata Compliance Dashboard (v26.05). Maastricht University Library. doi.org/10.5281/zenodo.20052424

Acknowledgements 🙌

There is great inspirational work related to metadata monitoring, for instance the Biodiversity Dataverse dashboard that monitors compliance with cg core metadata from Bioversity International. Or the classic Dashboard metrics from the dataverse project.

Eventhough there are great clients for metadata extraction, we found a very neat one scholarsportal/dataverse-metadata-crawler, maintained by Scholars Portal, a service of the Ontario Council of University Libraries, and developed by Ken Lui 👍🏼.

DataverseNL is a consortium service supported by DANS. This dashboard is developed independently by Maastricht University Library and does not imply endorsement by DANS or the other projects acknowledged above.

Maintenance

Maintainer / author: Pedro V Hernandez Serrano
Contact UM Dataverse: ub-dataverse@maastrichtuniversity.nl
Released under MIT License
© 2026 Maastricht University Library | UM Disclaimer