Use when preparing the data-availability statement and reproducibility materials for a Demography (PAA / Duke University Press) manuscript. Demography requires a data availability statement at acceptance with persistent identifiers and encourages reproducible, commented code; it hosts no repository, so authors deposit in a FAIR repository. Covers restricted-data exemptions. Prepares the materials; it does not waive requirements.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill demog-data-and-reproducibility --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Demog Data And Reproducibility?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-demog-data-and-reproducibility)More formats (shields.io, HTML) on the badges page.
---
name: demog-data-and-reproducibility
description: Use when preparing the data-availability statement and reproducibility materials for a Demography (PAA / Duke University Press) manuscript. Demography requires a data availability statement at acceptance with persistent identifiers and encourages reproducible, commented code; it hosts no repository, so authors deposit in a FAIR repository. Covers restricted-data exemptions. Prepares the materials; it does not waive requirements.
---
# Data & Reproducibility (demog-data-and-reproducibility)
Demography asks every **accepted** manuscript for a **data availability statement** and **encourages
reproducible code**. The journal **does not maintain its own repository** — *you* choose a FAIR
repository and provide persistent identifiers. Build the materials as you go so acceptance does not
stall.
## When to trigger
- Building the reproducibility/replication materials and the data availability statement
- A manuscript reached acceptance and you must finalize the statement and deposit
- Data cannot be fully shared (privacy, confidentiality, proprietary/provider restrictions) and you
need the exemption language
- Choosing a repository and persistent identifier
## What Demography requires (verify current wording on the ethics/disclosures page)
1. **Data availability statement.** Accepted manuscripts must include a statement confirming **whether
and how** the data have been shared. For publicly available data, describe the access method with
a **persistent identifier** (DOI or accession number).
2. **Persistent identifiers + FAIR repository.** Because Demography hosts no repository, deposit data
and materials in a **FAIR-aligned repository** (e.g., ICPSR/openICPSR, Harvard Dataverse, Zenodo,
OSF) and cite it with a permanent link — not a personal website or generic cloud folder. Find one
via FAIRsharing.org or re3data.org.
3. **Reproducible code (encouraged).** Provide code that regenerates the results, with **software
versions recorded** and **informative comments** explaining each step. Treat this as expected, not
optional, for a quantitative demographic paper.
4. **Restricted data.** Where access is limited to protect confidential or proprietary information,
**describe the conditions limiting access** and how others may obtain the data, while still aligning
with FAIR principles as far as possible.
## Build-as-you-go checklist
- [ ] **Data availability statement** drafted (public / restricted / on request) with persistent IDs
- [ ] Data + materials deposited in a **FAIR repository** with a DOI/accession number
- [ ] One **master script** regenerates every table, figure, life table, and decomposition
- [ ] **README** documents data provenance/vintage, construction of rates/exposure, and how to reproduce each exhibit
- [ ] **Code commented** and **software/package versions recorded** (`renv.lock` / `requirements.txt` / installs)
- [ ] **Seeds** set and reported for bootstrap, simulation, microsimulation
- [ ] Exhibit numbers in the manuscript **match** the deposited output exactly
- [ ] Restricted data: exemption note + access conditions + synthetic data where feasible
## Anti-patterns
- Treating the data statement as a last-minute formality at acceptance
- A personal URL or generic cloud link instead of a persistent identifier in a FAIR repository
- Undocumented, un-seeded, uncommented code that "works on my machine"
- Claiming data are restricted without describing the access conditions
- Calling the $1,000 editorial-management fee an "open-access" or "data" charge (it is neither)
## Output format
```
【Data statement】public / restricted / on request — drafted with persistent ID? [Y/N]
【Repository】FAIR repo + DOI/accession (not personal URL)? [Y/N]
【Reproducible code】master script + comments + recorded versions + seeds? [Y/N]
【Exhibits match deposit?】[Y/N]
【Restricted data?】access conditions described + synthetic data where feasible?
【Next】demog-review-process
```
## Supplementary resources
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — FAIR repositories and reproducibility tooling
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — Demography data-availability and reproducible-code policy
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!