Data policy

The output of research is not only journal articles but also data sets, model codes, samples, etc. Only the entire network of interconnected information can guarantee integrity, transparency, reuse, and reproducibility of scientific findings. Moreover, all of these resources provide great additional value in their own right. Hence, it is particularly important that data and other information underpinning the research findings are "findable, accessible, interoperable, and reusable" (FAIR) not only for humans but also for machines.

Therefore, Copernicus Publications requests depositing data that correspond to journal articles in reliable (public) data repositories, assigning digital object identifiers, and properly citing data sets as individual contributions. Please find your appropriate data repository in the registry for research data repositories: A data citation in a publication resembles a bibliographic citation and needs to be included in the publication's reference list. To foster the accessibility as well as the proper citation of data, Copernicus Publications requires all authors to provide a statement on the availability of underlying data as the last paragraph of each article (see section data availability). In addition, data sets, model code, video supplements, video abstracts, and other digital assets should be linked to the article through DOIs in the assets tab.

Best practice following the Joint Declaration of Data Citation Principles initiated by FORCE 11:

Statement on the availability of underlying data

Authors are required to provide a statement on how their underlying research data can be accessed. This must be placed as the section "Data availability" at the end of the manuscript before the acknowledgements. Please see the manuscript preparation guidelines for authors for the correct sequence. If the data are not publicly accessible, a clear explanation of why this is the case is required. The best way to provide access to data is by depositing them (as well as related metadata) in FAIR-aligned reliable public data repositories, assigning digital object identifiers, and properly citing data sets as individual contributions. If different data sets are deposited in different repositories, this needs to be indicated in the data availability section. If data from a third party were used, this needs to be explained (including a reference to these data). Data Cite recommends the following elements for a data citation:

creators: title, publisher/repository, identifier, publication year (e.g. Loew, A., Bennartz, R., Fell, F., Lattanzio, A., Doutriaux-Boucher, M., and Schulz, J.: Surface Albedo Validation Sites, EUMETSAT [data set],, 2015).

Other underlying material

Data do not comprise the only information which is important in the context of reproducibility. Therefore, Copernicus Publications encourages authors to also deposit software, algorithms, model codes, video supplements, video abstracts, and other underlying material on suitable FAIR-aligned repositories/archives whenever possible. These materials should be referenced in the article and cited via a persistent identifier such as a DOI.

With regard to software citation, please refer to the FORCE11 Software Citation Principles.

Guidance on supporting information

All measures should be taken by the authors to ensure that their work can be independently reproduced. This includes providing access to electronic data such as pulse sequences and software where appropriate.

  • Supporting information shall contain only complementary information but no scientific interpretations or findings that go beyond the contents of the manuscript.
  • Where the electronic data accompanying the manuscript is <50 MB, this should be uploaded with the manuscript as supplemental data.
  • For raw data (e.g. NMR spectra) and where the size of the electronic data is >50 MB, authors are asked to deposit their data in a separate repository and to insert a persistent identifier, ideally a DOI, in the manuscript. Options include:
    • Standard and citable data repositories appropriate to the field (e.g. BMRB for NMR data).
    • Institutional repositories (e.g. library resources where these provide a DOI).
    • General data repositories, such as figshare, Dryad, Open Science Framework or Zenodo.
  • Software code should be provided via a version-controlled platform such as GitHub.
  • Although this is not a requirement for publication, for software we additionally encourage the authors to provide either a containerised version of their software (using data repositories outlined above) or that they implement their software in a publicly available and version controlled VM. The latter can be done using the NMRbox solution, where the authors may seek additional assistance from the NMRbox administrators for software implementation.