Supplementary Material Statement in Papers

For supplementary materials, we use a standardized statement -- unless the publishers force us to use a different one. We proceed in the following way. First, in the Materials and Methods part of our papers, we typically add a section Implementation in the Methods section of the paper, where we describe how everything is implemented. Here, we can also mention that the code and the data are available, where they are curated, and where they are shared. Second, we add before the bibliography a section that is not numbered, which contains explicit information on where the data and code can be found. This section is typically called Supplementary Material. The content can for example look as follows:

All data and code underlying this study are available from the supplementary material accompanying this paper. They are curated on GitHub (https://github.com/example/example, Version 1.0) and archived with Zenodo (https://doi.org/zenodo-doi.

Note that we use an explicit version for data and code. This means, that you must create a tag or a release on GitHub for the repository. The content of this release is then archived with Zenodo. This can be done automatically, but for the time being, Zenodo's new API has several issues with too many accesses by users, so it basically does not work for us.

In this context, please note that we ALWAYS need to have a version on GitHub (or in any GIT repository you create), and that you can instead of Zenodo also submit the data to another archive (like OSF). But you must a) provide a version (in GIT, this is a tag, in GitHub, this is a release, that fixes the data at the point of publication), and in Zenodo you archive only the data corresponding to that release, never all the GIT repository with its internal history.