Skip to content

Data Management Plan (DMP)

A Data Management Plan documents how every dataset consumed, generated, transformed, or published during a project will be handled across its full lifecycle — from creation and storage through sharing, preservation, and eventual retirement. Machine-actionable DMPs (UC3/DMPTool 2026) connect the plan to the actual outputs it describes, closing the gap between intent and execution. Produce this artifact during the Find phase of any FCC cycle that creates, reuses, or redistributes structured data.

Template

Section 1: Plan Metadata

Instructions: Assign a stable DMP ID, link it to the related preregistration and Innovation IDs, and keep status monotonic: Draft → Active → Archived → Superseded.

Field Value
DMP ID [FILL — e.g. DMP-2026-001]
Project / Experiment [FILL]
Authors [FILL]
Date created [FILL]
Status [Draft / Active / Archived / Superseded]
Related Preregistration [FILL — OPEN-SCI-001 link]

Section 2: Data Description

Instructions: Enumerate datasets generated and reused separately. For each dataset, link to its Dataset Card (OPEN-SCI-004b) or mark "to be created". Declare any data not collected and why.

  • Datasets generated: [FILL]
  • Datasets reused: [FILL]
  • Data deliberately not collected: [FILL]

Section 3: Metadata & Documentation

Instructions: Declare metadata standards and controlled vocabularies. FAIR² requires machine-actionable metadata; schema.org is the default vocabulary unless a domain ontology is warranted.

  • Metadata standard(s): [FILL — FAIR², schema.org, DCAT, domain-specific]
  • Controlled vocabularies: [FILL]
  • Provenance tracking approach: [FILL — experiment tracker, Git, lineage]

Section 4: Storage & Security

Instructions: Specify primary storage, backup strategy, encryption, access control, and PII handling. Sensitive datasets require a DPIA reference and a documented anonymisation procedure.

  • Primary storage: [FILL]
  • Backup strategy: [FILL]
  • Encryption at rest / in transit: [FILL]
  • Access roles and levels: [FILL]
  • PII present? handling: [FILL]

Section 5: Sharing, Preservation, and Retirement

Instructions: Describe who can access each dataset, via which service endpoint, under which license. Document retention period, archive location, migration plan, and deletion procedure.

  • Consumers and access method: [FILL]
  • License: [FILL]
  • Retention period: [FILL]
  • Archive location / format: [FILL]
  • Migration + deletion plan: [FILL]

Section 6: Responsibilities & Review

Instructions: Name the data steward, technical contact, and IP contact. Set a review cadence (quarterly minimum for active datasets).

  • Data steward: [FILL]
  • Technical contact: [FILL]
  • IP / licensing contact: [FILL]
  • Review cadence: [FILL]

Adoption Checklist

  • All required sections completed
  • Artifact peer-reviewed by at least one R.I.S.C.E.A.R. peer
  • Stored in the project's designated docs location
  • Linked from README or equivalent index
  • Versioned + date-stamped, with review cadence scheduled

References

  • PHOENIX v4.0.0 — docs/resources/templates/open-science/dmp.md
  • UC3 / DMPTool (2026) — Machine-actionable DMP specification
  • FAIR² Open Specification (October 2025)
  • RDMkit — Research Data Management Toolkit (ELIXIR)
  • Center for Open Science — Lifecycle Open Science 2026-2028

FCC integration

This template is referenced from the Forensic Auditor persona (src/fcc/data/personas/forensic_auditor.yaml) as part of the Critique-phase evidence set — the auditor verifies that every dataset touched by a workflow is covered by a current DMP. See also the open-science gates in src/fcc/data/governance/open_science_gates.yaml and related quality gates in src/fcc/data/governance/quality_gates.yaml.