Availability Statement Examples

Authors are expected to provide an Availability Statement in their article immediately following the Acknowledgments section that details where data, software, and other research objects are available, and how they can be accessed and reused (listing specific restrictions, if any). If the research objects underlying the article cannot be made available or reused, the Availability Statement should describe as completely as possible the process needed to replicate the results of the study, including a link to detailed documentation and contact information of the responsible digital resource manager (see the sixth set of examples below).

Examples of some common types of availability statements, including software statements derived from Fox et al. (2021), are included below. Please refer to Data and Software Archiving Guidance for additional information about identifying an appropriate repository if needed. Use the AMS Data and Software Reference and Citation Examples page to ensure your data and software citations follow AMS style when finalizing your manuscript.

  1. Datasets available from a funder-mandated or public (institutional, general, or subject-specific) repository that assigns persistent identifiers to datasets:
    • All sea ice concentration data created or used during this study are openly available from the NASA National Snow and Ice Data Center Distributed Active Archive Center at https://doi.org/10.5067/8GQ8LZQVL0VL as cited in Cavalieri et al. (1996).
  2. Datasets published in the literature:
  3. Datasets derived from public resources and made available with the article:
    • Data analyzed in this study were a re-analysis of existing data, which are openly available at locations cited in the reference section. Further documentation about data processing is available at [repository name] at [insert DOI here].
    • Datasets analyzed during the current study are available in the [repository name] [identifying doi or persistent URL] [Reference number]. These datasets were derived from the following public domain resources: [list resources and their URLs].
  4. Data sharing not applicable (e.g., for Comments, Replies, Review articles, or theory-based articles):
    • No datasets were generated or analyzed during the current study.
  5. Datasets that are restricted and not publicly available: 
    • Due to its proprietary nature <or ethical concerns>, supporting data cannot be made openly available. Further information about the data and conditions for access are available at the [repository name] at [insert DOI here].
    • Due to confidentiality agreements, supporting data can only be made available to bona fide researchers subject to a non-disclosure agreement. Details of the data and how to request access are available from [digital resource manager contact info] at [institution where data reside].
    • Due to privacy and ethical concerns, neither the data nor the source of the data can be made available.
  6. No valid data repositories exist. In rare cases where no valid data repositories are identified after reviewing all resources, including information specified on the Data and Software Archiving Guidance page, authors must provide a transparent process for making the data available to others:
    • The dataset on which this paper is based is too large to be retained or publicly archived with available resources. Documentation and methods used to support this study are available from [digital resource manager contact info] at [institution].
    •  The authors were unable to find a valid data repository for the data used in this study. These data are available from [digital resource manager contact info] at [host institution].
    •  The numerical model simulations upon which this study is based are too large to archive or to transfer.  Instead, we provide all the information needed to replicate the simulations; we used model version [V#.#].  The model code, compilation script, initial and boundary condition files, data preprocessing codes, postprocessing codes and the namelist settings are available at [DOI or permanent URL].
  7. Software archived in a repository, which must be findable and accessible (e.g. via URLs):
    • Software for this research is available in these in-text data citation references: Smith et al. (2019),[with this license, and these access restrictions if any], Jones et al. (2017) [with this license, and these access restrictions if any].
  8. Software published in the literature as supplementary information:
    • Software for this research is included in [citation for paper] (and its supplementary information files)..
  9. Software not publicly available, but available to researchers with appropriate credentials:
    • Software for this research is not publicly available due to [give reasons]. Software is stored in this in-text citation reference: Smith et al. (2019), [with this license, and these access restrictions if any].
  10. Software that is restricted by commercial, industry, patent, government policies, regulations or laws:
    • Software supporting this research is available in [cite in-text citation reference from third-party source], with [these restrictions that include information concerning required NDA, licensing, agreements], and is not accessible to the public or research community. <The alternative to the preceding statement is to provide a process for how other researchers can gain access>.
  11. Software sharing not applicable (e.g., for review articles or theory-based articles):
    • Software (other than for typesetting) was not used for this research.

Two good sources for more examples of data and software availability statements can be found at the University of Bath Research Data Archive and from Fox et al. (2021), which documents the guidance provided to AGU authors.