Every paper must include a public data availability statement and a public code availability statement. The statements must distinguish materials that are public, restricted, available by request, not shareable, not created, or not applicable.
Acceptable statement models
Authors should adapt one or more of these models and name the relevant repository, rights holder, or restriction:
- Public data and code: Data and code are publicly available at [named repository and persistent URL].
- Public code; restricted data: Code is publicly available at [location], but the underlying data are restricted under [legal, contractual, licensing, privacy, or ethics basis].
- Controlled request: Materials are available from [author or data custodian] subject to [legal or contractual] restrictions.
- Cannot be shared: Data cannot be shared because of [confidentiality, privacy, licensing, legal, contractual, or ethics restriction].
- No original materials: No original data or code were created for this paper.
- Not applicable: Data and code availability is not applicable to this paper because [brief reason].
“Available upon request” must identify who controls access and any known conditions. It is not a guarantee that every request will be granted.
Public materials
When materials are public, authors should prefer a stable institutional or discipline-appropriate repository and provide a persistent identifier or durable URL when available. The record should identify the files, software or runtime information needed to interpret them, and any license or access conditions.
Passwords, API keys, access tokens, personal information, licensed source data, and other secrets must not be included in a public package.
Restricted materials
Restrictions must be stated honestly and specifically without exposing protected information. A paper may be considered when underlying materials cannot be public, provided that the authors had authority to use them, the manuscript itself can be published lawfully and ethically, and the availability statement accurately describes the limitation.
The Editorial Board may request private evidence of data authority or analytical support during screening. Private review does not authorize the Series to redistribute the materials.
Repository boundary
The Series does not promise that OAsis hosts datasets, code, or replication packages. Unless UNLV University Libraries approves a supplement workflow for a specific record, the OAsis relationship described on this site concerns the paper’s item record and deposited full text.
What screening does not certify
An availability statement and editorial check do not establish that the analysis has been independently replicated, that every public file is complete, or that a third-party repository will remain unchanged. Authors remain responsible for the accuracy, documentation, permissions, and security of the materials they identify.
If availability changes after publication, the author should contact the Series. A broken link or non-substantive location update may be corrected administratively; a change that affects interpretation or reproducibility may require a correction or new version under Corrections, Revisions & Versioning.