Data, code, and reproducibility
A claim that rests on data or code is only as checkable as the data and code behind it.
Availability statement
Every manuscript reporting empirical or computational results must carry a data availability statement before the works-cited list. It says where the data and code are, under what licence, and what a reader must do to obtain them. "Available on request" is accepted only with a stated reason -- participant confidentiality, third-party licence, or legal restriction -- and a named contact.
What to deposit
- Analysis data in a form that reproduces the reported results, or a documented synthetic substitute where the real data cannot be shared.
- Code sufficient to run the analysis, with dependencies pinned.
- Model artefacts, prompts, seeds, and configuration where results depend on them.
- A README naming which file produces which table or figure.
Human-subject and sensitive data
Do not deposit personal data. Report the ethics approval and consent basis in the methods section. Where a dataset concerns a community, state how that community was involved and what risks the release carries. Withholding data to protect participants is legitimate; withholding it to protect a result is not.
Citing data
Datasets and software are cited in the works-cited list like any other source, with version and persistent identifier. See the MLA style guide.