Nature Data
Make the data path concrete and verifiable.
- Inventory datasets, derived data, code, models, images, protocols, identifiers, licenses, restrictions, and responsible owners.
- Separate publicly available, controlled-access, embargoed, and unavailable material. Explain the reason and access route for each exception.
- Draft a Data Availability statement that names the repository, accession or persistent identifier, version, and what exactly is deposited.
- Draft a Code Availability statement when analysis code or software is needed for reproduction; record environment and license where known.
- Check FAIR basics: findable identifiers and metadata, accessible route, interoperable formats, reusable documentation, provenance, and contact or governance path.
Never invent accession numbers, repository deposits, permissions, licenses, or release dates. If a deposit has not happened, write a clearly marked placeholder and an actionable checklist.
This is a ScanSci adaptation of the nature-data workflow from Yuan1z0825/nature-skills.
1---2name: nature-data3description: Data Availability statement, repository plan, metadata checklist, and FAIR-readiness review for scientific manuscripts. Use for data sharing plans, accession information, code availability, repository selection, or FAIR metadata.4---56# Nature Data78Make the data path concrete and verifiable.9101. Inventory datasets, derived data, code, models, images, protocols, identifiers, licenses, restrictions, and responsible owners.112. Separate publicly available, controlled-access, embargoed, and unavailable material. Explain the reason and access route for each exception.123. Draft a Data Availability statement that names the repository, accession or persistent identifier, version, and what exactly is deposited.134. Draft a Code Availability statement when analysis code or software is needed for reproduction; record environment and license where known.145. Check FAIR basics: findable identifiers and metadata, accessible route, interoperable formats, reusable documentation, provenance, and contact or governance path.1516Never invent accession numbers, repository deposits, permissions, licenses, or release dates. If a deposit has not happened, write a clearly marked placeholder and an actionable checklist.1718This is a ScanSci adaptation of the `nature-data` workflow from Yuan1z0825/nature-skills.
Rimagination