DMP Guide: MSCA for History & Archaeology
Learn how to design a fully compliant Data Management Plan (DMP) that satisfies Marie Skłodowska-Curie Actions open-data policies. Explore optimal file formats, metadata mapping, and repository selection for History & Archaeology research data.
1. Funder Policy & Open Data Compliance
In alignment with international open-science mandates, Marie Skłodowska-Curie Actions requires all principal investigators to submit a comprehensive Data Management Plan (DMP) with their grant application. A robust DMP details how research data will be collected, processed, documented, stored, shared, and preserved both during and after the project.
Funder-Specific Mandate Directive
Under guidelines set by the **Marie Skłodowska-Curie Actions (MSCA)**, a formal DMP must be compiled and submitted for the **History & Archaeology** project by Month 6. Research data must follow European open-science protocols, complying with the core doctrine of being "as open as possible, as closed as necessary" to secure proprietary discoveries.
Verified Funder Open-Science Portfolio
Based on independent, open-science bibliometric data from OpenAlex, the Marie Skłodowska-Curie Actions (MSCA) oversees a massive scholarly ecosystem with over 43,842 published research outputs under their funding catalog, accumulating over 1,202,144 citations across the global scientific record. To protect the public's investment in this massive knowledge corpus, the funder strictly enforces FAIR data management and open repository deposits, making compliance with this DMP protocol mandatory for all awarded grants.
For projects in the field of History & Archaeology, managing data correctly is essential not only for compliance, but also to support peer-review validation and reproducibility. All DMPs must be submitted through the Funding & Tenders Portal portal, using standard institutional guidelines.
2. Data Types, Formats, and Metadata Standards
A high-quality DMP must explicitly identify the types of data that will be generated and specify open, non-proprietary file formats to ensure long-term usability. For History & Archaeology, datasets typically range from raw observational measurements to curated computational models.
For qualitative and archival files in **History & Archaeology**, data plans focus on digitised materials, text corpora, and spreadsheets. To ensure durability, the DMP mandates saving all documents in non-proprietary formats, satisfying standard **MSCA** digital preservation criteria.
To guarantee discoverability, datasets should be documented using standardised metadata schemas that map to the History branch of scholarly vocabularies. This ensures indexers and crawlers can crawl and identify research outputs accurately.
| DMP Component | Custom Target Value for History & Archaeology |
|---|---|
| Preferred File Formats | TXT (transcribed archives), OBJ/PLY (3D scans), GeoTIFF (excavation grids), PDF/A (facsimiles) |
| Metadata Schema Standard | CIDOC-CRM, Dublin Core Metadata standard |
| Target Scientific Repositories | Archaeology Data Service (ADS), Zenodo, Figshare, and directory servers mapped in Historical Abstracts & Scopus |
3. Step-by-Step DMP Construction Protocol
When preparing your DMP for a MSCA proposal, structure your document around these core sections:
- Data Collection and Generation:
Describe the methodology, instrumentation, or software used to collect or generate new data. Detail quality assurance and quality control measures implemented at your facility. - Documentation and Metadata:
Explain how the data will be documented, including accompanying read-me files, data dictionaries, and laboratory notebooks. Specify the metadata standards to be utilized (using CIDOC-CRM, Dublin Core Metadata standard as standard). - Ethics, Intellectual Property, and Consent:
Address how sensitive or confidential datasets will be handled. Detail anonymisation processes, access controls, and compliance with institutional ethics boards. - Storage, Backups, and Security:
State where data will be stored during active research. Detail automated backup schedules, server redundancies, and access authorisation protocols. - Long-Term Preservation and Archiving:
Select the digital repository for post-project archiving (such as Archaeology Data Service (ADS), Zenodo, Figshare, and directory servers mapped in Historical Abstracts & Scopus). Confirm that the repository supports persistent identifiers (handles/DOIs) and provides secure preservation.
Open Science Workflows, Data Curation & Repositories
When drafting a data management plan dmp to satisfy MSCA guidelines, defining systematic data collection methods and formal data curation standards is vital. Utilizing institutional dmptool workflows ensures that these administrative requirements are built-in from the outset of the study. Investigators must outline procedures for post-collection data cleaning, strict audits of data integrity, and programmatic data wrangling to transform raw outputs into clean models. Furthermore, a descriptive data dictionary must be provided to define the database schema. Architecturally, teams can configure either a secure relational data warehouse or a cost-effective cloud-based data lake, evaluating how this data lake vs data warehouse setup supports formal data analysis and immediate exploratory data analysis under MSCA guidelines. Upon completion, data will be submitted to the dryad data repository, published as figshare datasets, or preserved via a zenodo data upload to be registered in the global data citation index and satisfy nsf data management plan guidelines and regional MSCA open-science rules. The study will document clear data versioning protocols hosted on the open science framework osf to enable reproducible data sharing matching top fair data principles examples. Furthermore, any community-engaged data must respect the care data principles and support indigenous data sovereignty care standards to ensure local governance of shared knowledge under MSCA audits. Implementing this storage layout satisfies compliance protocols overseen by the MSCA data audit team.
4. Frequently Asked Questions
Are we required to share all raw data from our research?
No, MSCA policies generally recognise that some data cannot be shared publicly due to privacy, security, intellectual property, or commercialisation constraints. In such cases, your DMP must justify why certain datasets are restricted and describe how metadata will still be made discoverable.
Who owns the research data generated under this grant?
Data ownership is typically held by the host institution, subject to co-ownership clauses in collaborative projects. However, MSCA guidelines require that data be made as openly available as possible under open licensing, such as Creative Commons or Open Data Commons.
DMP Specifications
FAIR Principles
Your plan must align with the FAIR Principles:
- Findable: Rich metadata and persistent DOIs.
- Accessible: Free retrieval via standard protocols.
- Interoperable: Open formats and vocabulary alignment (such as CIDOC-CRM, Dublin Core Metadata standard).
- Reusable: Clear data licensing and reuse guidelines.







