DMP Guide: NIH for History & Archaeology
Learn how to design a fully compliant Data Management Plan (DMP) that satisfies National Institutes of Health 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, National Institutes of Health 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 **National Institutes of Health (NIH)** mandates a formal Data Management Plan (DMP) submitted via **eRA Commons** for all **History & Archaeology** proposals. Under the active federal data access policies, scientific data must be preserved and made openly available no later than the date of associated publication or project end.
Verified Funder Open-Science Portfolio
Based on independent, open-science bibliometric data from OpenAlex, the National Institutes of Health (NIH) oversees a massive scholarly ecosystem with over 1,762,091 published research outputs under their funding catalog, accumulating over 106,474,500 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 eRA Commons 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.
Data outputs in **History & Archaeology** typically consist of historical records, gridded data, or structured text documents. DMPs must outline plans to archive these files in open, non-proprietary formats to avoid software lock-in under **NIH** projects.
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 NIH 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
To secure approval from National Institutes of Health, the investigator's data management plan dmp must clearly justify chosen data collection methods and adhere to active data curation standards. Integrating digital dmptool workflows helps automate compliance reporting via the eRA Commons portal. This includes describing protocols for data cleaning, validating data integrity via checksums, and conducting secure data wrangling on raw source files. Each output dataset must be documented with an explanatory data dictionary mapping key metadata fields. The DMP must justify whether files are catalogued in a structured data warehouse or kept as raw files in a flexible data lake, discussing how a data lake vs data warehouse decision impacts subsequent data analysis and programmatic exploratory data analysis for History & Archaeology. PIs will facilitate public sharing by leveraging the dryad data repository, creating searchable figshare datasets, or completing a zenodo data upload, ensuring tracking through the data citation index in compliance with nsf data management plan protocols and National Institutes of Health targets. Researchers are required to publish systematic data versioning protocols through the open science framework osf to facilitate long-term reproducible data sharing in line with fair data principles examples. If data is collected from specialized regions, the plan must comply with the care data principles and respect indigenous data sovereignty care rights to meet National Institutes of Health ethical benchmarks. Aligning the archiving schedule directly with NIH open-access metrics protects the project's funding cycles.
4. Frequently Asked Questions
Are we required to share all raw data from our research?
No, NIH 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, NIH 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.







