Applicants and grantees funded by the Polish National Science Centre (NCN).

• DMP is mandatory: Since June 2019, NCN requires applicants to prepare a Data Management Plan (DMP) at the proposal stage (completed in the application system using NCN’s question set).
• The DMP should be completed in English; for MINIATURA calls, the DMP must be completed in Polish only.
• Living document: Treat the DMP as a plan you update during the project and reflect in reports.
• Data linked to publications: Share in trusted open repositories under clear licenses (CC0/CC BY 4.0 or equivalent openness), unless justified legal/ethical/commercial restrictions apply.
• Retention: Keep data and/or essential documentation for a substantial period (typically up to ~10 years, per repository/policy recommendations).

• At application: Fill in the NCN DMP section in the application system, following NCN’s guidance.
• During the grant: Update your DMP internally when things change; report what was planned vs. delivered in annual/final reports.
• At/after publication: Deposit the dataset and metadata in an open, trustworthy repository and link it to the publication.

1. New data and reuse of existing data
   Describe the types, sources, and volume of data you will create or reuse; note formats, collection/creation methods, and any third-party data (including access conditions).
2. Metadata, organisation, and quality control
   Explain how data will be named, structured, and versioned; which metadata/discipline standards you’ll follow; and the quality assurance steps (e.g., calibration, validation, review).
3. Storage and backups during the project
   Specify where data will be stored (systems/locations), who has access (roles/permissions), how you will maintain confidentiality/integrity, and your backup approach (regular, independent copies and restore testing).
4. Legal and ethical requirements
   Identify GDPR/RODO, ethics, consent, IP/rights and any licenses/agreements governing your data; outline how you will anonymise/pseudonymise and manage restricted data.
5. Sharing and long-term preservation
   State what will be shared, where (repository choice and why), when (embargo, if any), under which license, and how you will ensure findability (e.g., DOI) and long-term availability.
6. Responsibilities and resources
   Assign roles (who does what), list infrastructure/services you’ll use, and indicate costs/time for storage, curation, and preservation (and how they’re covered).

• Share datasets underpinning publications, unless a clear, documented restriction applies (“as open as possible, as closed as necessary”).
• Use repositories that support FAIR (rich metadata, persistent identifiers, clear access terms) and long-term availability.
• Prefer CC0 or CC BY 4.0 (or equivalent) for data; choose appropriate open-source licenses for code.

Pick a repository that:

• allows public/open access (unless justified restrictions apply),
• supports FAIR and rich metadata,
• provides long-term preservation (≈10 years),
• assigns persistent identifiers (e.g., DOI/Handle/URN),
• is listed in re3data/OpenDOAR (recommended).

Where to deposit:

• PWr collection in RepOD: our recommended default when no disciplinary repository fits.
• Registry of repositories: re3data.org (to find a disciplinary repository).

• In annual reports: describe data sharing linked to outputs (if applicable).
• In the final report: state what was actually done vs. planned in the DMP; list datasets shared with identifiers/metadata.

• NCN – Guidelines for completing the Data Management Plan (PL)
• NCN – Open Access/Open Science updates (incl. data-sharing duty)
• NCN – Director’s Order No. 39/2025 (data sharing & licensing)