DMP Guide: CNPq for History & Archaeology
Learn how to design a fully compliant Data Management Plan (DMP) that satisfies Conselho Nacional de Desenvolvimento Científico e Tecnológico 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, Conselho Nacional de Desenvolvimento Científico e Tecnológico 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
The **Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq)** open-science policy expects research data in **History & Archaeology** to be managed, documented, and archived in public repositories supporting persistent identifiers. Plans must be submitted through the **Plataforma Lattes** portal.
Verified Funder Open-Science Portfolio
Based on independent, open-science bibliometric data from OpenAlex, the Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq) oversees a massive scholarly ecosystem with over 472,207 published research outputs under their funding catalog, accumulating over 9,674,359 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 Plataforma Lattes 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 **CNPq** 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 CNPq 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
A compliant data management plan dmp for research projects in History & Archaeology must detail the specific data collection methods and the precise data curation standards that govern the project. By configuring customizable dmptool workflows, research teams can seamlessly align their files with Conselho Nacional de Desenvolvimento Científico e Tecnológico's schemas. Adhering to CNPq requirements means detailing how raw files undergo data cleaning, how researchers verify ongoing data integrity, and which tools handle automated data wrangling. Additionally, a standardized data dictionary must be compiled to guarantee metadata clarity. From a storage perspective, researchers must evaluate storing datasets in a highly indexed data warehouse versus a scalable data lake, analyzing the trade-offs of a data lake vs data warehouse architecture for downstream data analysis and exploratory data analysis inside the Plataforma Lattes workspace. To ensure permanent access, datasets will be deposited in the dryad data repository, hosted as figshare datasets, or archived via a secure zenodo data upload, enabling inclusion in the data citation index and fulfilling standard nsf data management plan and local CNPq requirements. We will enforce structured data versioning protocols using the open science framework osf to streamline reproducible data sharing that is fully compliant with fair data principles examples. Additionally, all collaborative research must respect the care data principles and uphold indigenous data sovereignty care policies, keeping community interest central to the data lifecycle. This explicit lifecycle structure meets the standard pre-requisites issued under CNPq project management guidelines.
4. Frequently Asked Questions
Are we required to share all raw data from our research?
No, CNPq 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, CNPq 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.







