Eleventh Press International Publishing™
Official guide · EP-G-05
Data & Code Availability Guide
Writing a data availability statement, choosing a repository, licensing and citing datasets and software, and handling sensitive data, the FAIR way.
- Version
- 2.0
- Effective
- 6 November 2026
- Next review
- 6 November 2027
- Licence
- CC BY 4.0
ISSN 2945-1138 · Publisher DOI prefix 10.52011 · Philippines · editorial@eleventhpress.com
Purpose
To explain how to make the data and code underlying a published article findable, accessible, interoperable and reusable: writing the data availability statement, choosing a repository, licensing, citation and the handling of sensitive data.
Scope
Applies to all research articles. Every submission requires a data availability statement; open sharing is required where a funder mandates it and strongly encouraged everywhere else.
Audience
Authors of research that produces or uses data, code, models or other research materials.
At a glance: ten key requirements
- Every submission needs a data availability statement; “not applicable” is valid only where no data were generated or analysed.
- Share data in a trusted repository that issues persistent identifiers, ideally a discipline-specific one.
- Zenodo records can be linked directly to your article and give the dataset its own citable DOI.
- Follow the FAIR principles: rich metadata, persistent identifiers, open formats and a clear licence.
- Cite datasets and software in the reference list, with version and DOI.
- Release data under CC0 or CC BY, and code under an OSI-approved licence.
- Archive the exact version of the code used, with its dependencies, and give it a DOI.
- Sensitive data may be shared under controlled access; explain the conditions in the statement.
- Respect Indigenous data sovereignty following the CARE principles.
- Keep links current: broken data links are among the most common post-publication correction requests.
Benchmarked standards and basis
This guide is benchmarked against the external standards below. “Aligned with” describes the standard each requirement follows; it is not a claim of membership in, or certification by, the issuing body.
| Standard and issuing body | Edition | How this guide applies it |
|---|---|---|
| FAIR Guiding PrinciplesWilkinson et al., Scientific Data | Edition: 2016 | Findable, Accessible, Interoperable and Reusable: the overall standard for shared data and code. |
| Joint Declaration of Data Citation PrinciplesFORCE11 | Edition: 2014 | Data are cited in the reference list with persistent identifiers, like any other scholarly output. |
| Software Citation PrinciplesFORCE11 (Smith, Katz & Niemeyer) | Edition: 2016 | Research software is cited by version and identifier, and its authors credited. |
| Transparency and Openness Promotion (TOP) GuidelinesCenter for Open Science | Edition: Current | Data, code and materials transparency, and citation standards for journals. |
| CARE Principles for Indigenous Data GovernanceGlobal Indigenous Data Alliance | Edition: 2019 | Collective benefit, authority to control, responsibility and ethics for data about Indigenous peoples. |
| Data Privacy Act of 2012 (Republic Act No. 10173)National Privacy Commission, Philippines | Edition: Current | Lawful processing, anonymisation and controlled sharing of personal data. |
01Why data and code availability matters
Readers can only evaluate, reproduce and build on research if they can access what it rests on. Shared data and code make errors easier to find and correct, allow results to be combined in syntheses, and give credit to the people who created them. Funders increasingly require sharing, and articles with available data are easier to trust.
For these reasons every submission to Eleventh Press includes a data availability statement. Linking open data is required where a funder mandate specifies it and strongly encouraged everywhere else.
03Writing the data availability statement
The statement tells readers where the data and code are and how to access them. Adapt one of these templates:
- Publicly available: “The data and code supporting this study are openly available in [repository] at https://doi.org/[DOI], under a [licence] licence.”
- Controlled access: “The data are available from [repository or body] under controlled access, subject to [conditions], because they contain [reason]. Code is openly available at https://doi.org/[DOI].”
- Third-party data: “The data were obtained from [provider] under licence and are available from them at [URL] subject to their terms.”
- On request (only where justified): “The data are available from the corresponding author on reasonable request, because [specific reason].”
- Not applicable: “No data were generated or analysed in this study.”
“Available on request” is a last resort, because such requests often go unanswered. Where it is used, the reason must be stated.
04Choosing a repository
Use a trusted repository that issues persistent identifiers such as DOIs, commits to long-term preservation and supports rich metadata. Discipline-specific repositories are preferred where they exist, because their communities know how to find and reuse the data. Generalist repositories are a good alternative.
Eleventh Press supports linking Zenodo records directly to your submission as a dataset link. Zenodo, operated by CERN, gives the dataset its own citable DOI alongside the article's, supports versioning, and can archive GitHub releases automatically. Whatever repository you choose, enter the identifier in the submission form and in the statement.
05Licensing data and code
Release data under CC0 (a public-domain dedication that removes legal barriers to reuse) or CC BY 4.0. Release code under a licence approved by the Open Source Initiative, such as MIT, BSD-3-Clause or Apache 2.0, or a copyleft licence such as GPL-3.0 if you want derivatives to stay open. Creative Commons licences are not designed for software.
Make sure you have the right to share: data obtained from third parties, or collected under consent forms that limit reuse, may need different arrangements.
06Citing data and software
Cite datasets and software in the reference list, as you would articles, following the Joint Declaration of Data Citation Principles and the Software Citation Principles. A citation should include the creators, year, title, version, repository or publisher, and persistent identifier, for example: Author, A. A. (2026). Title of dataset (Version 1.2) [Data set]. Zenodo. https://doi.org/10.5281/zenodo.xxxxxxx.
Cite the specific version you used. For code, archive the exact release that produced your results, record its dependencies (for example with a requirements, environment or lock file) and give it a DOI.
07Sensitive, personal and Indigenous data
Not all data can be fully open. Personal data must be processed lawfully, which for a journal based in the Philippines means in line with the Data Privacy Act of 2012 (Republic Act No. 10173) as well as the law that applies where the data were collected, such as the GDPR for data about people in Europe. Anonymise data where possible, remembering that combinations of variables can re-identify people. Where anonymisation would destroy the data's value, share through a controlled-access repository or data enclave and describe the access conditions.
Data about Indigenous peoples should follow the CARE Principles for Indigenous Data Governance — collective benefit, authority to control, responsibility and ethics — alongside FAIR. Data that could cause harm if released, such as the locations of endangered species or security-sensitive information, may also justify restrictions. Explain any restriction in the statement.
08Keeping links current
Update the dataset link if your repository record moves or a new version is released. Broken data links are among the most common post-publication correction requests we receive. Persistent identifiers such as DOIs resolve even when the underlying URL changes, which is one more reason to prefer them over plain web addresses.
Compliance checklist
Frequently asked questions
Is sharing data mandatory?
A data availability statement is mandatory for every submission. Open sharing is required where your funder mandates it and strongly encouraged in all other cases.
Can I link a Zenodo dataset to my article?
Yes. Zenodo records can be linked directly at submission and give the dataset its own citable DOI alongside the article's.
Which licence should I use for my data?
CC0 or CC BY 4.0 for data, and an OSI-approved licence such as MIT or Apache 2.0 for code.
My data contain personal information. What should I do?
Anonymise the data if possible; otherwise share them through a controlled-access repository and explain the access conditions in the statement.
How to cite this guide
Eleventh Press International Publishing™. (2026). Data & Code Availability Guide (EP-G-05, Version 2.0). https://eleventhpress.com/resources/guides/data-and-code-availability-guide
Related guides
This online edition is authoritative and is updated whenever the guide is revised; the PDF is its printable edition. Questions about this guide: editorial@eleventhpress.com.