# Publications # Funding Statement for the ERC ProduSemy Grant Please use the following standardized paragraph in your work to indicate the ERC as our funder for all research published in the context of the ProduSemy project. > This project was supported by the ERC Consolidator Grant ProduSemy (PI Johann-Mattis List, Grant No. 101044282, see [https://doi.org/10.3030/101044282](https://doi.org/10.3030/101044282)). Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union or the European Research Council Executive Agency (nor any other funding agencies involved). Neither the European Union nor the granting authority can be held responsible for them. # 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](https://github.com/example/example), Version 1.0) and archived with Zenodo ([https://doi.org/zenodo-doi](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](https://osf.io)). 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. # Preprint Servers There are different preprint servers where articles can be submitted. We basically use the following providers: - [arXiv](https://arxiv.org) requires submissions in `pdflatex`, as a result, we only use submit our preprints to arXiv when we have written articles in `pdflatex`, which is typically done in the context of the typical conferences organized by the Association for Computational Linguistics (ACL). - [Humanities Commons](https://hcommons.org) is something like an all-purpose preprint server that we use for most articles. Disadvantage is that updates are only possible within one day of submission, and past attempts to modify content have not been successful, since we did not receive any reply on our emails. Additionaly preprint providers are [bioRxiv](https://www.biorxiv.org/) and [PsyArXiv](https://osf.io/preprints/psyarxiv). Both can be used, but bioRxiv tends to reject content not really relatd to biology. Nature and Science now also offer their own preprint services. They are not recommended, since they are bad in many regards (e.g. no Unicode handling in Word Documents). If needed, one can still use them, of course, e.g., because the journal requires ist, but rather stick to the two mentioned above plus \[Psy # Supplementary Material Statement in Drafts When submitting a draft, you typically upload all supplementary material to a repository with the [Open Science Framework](https://osf.io), which can also be linked through GitHub. You should use the same statement as we use for papers to be published (see [Supplementary Material Statement in Papers](https://wiki.calclab.org/books/publications/page/supplementary-material-statement-in-papers)), but you do not mention GitHub (since it is not anonymous) and you only refer to the Open Science Framework. Here, you provide an anonymous share link for review, that you can create through the OSF interface. > All data and code underlying this study are available from the supplementary material accompanying this paper. They are curated accessible via the Open Science Framework ([https://osf.io/example](https://osf.io/example)) and will be officially released and archived in case this study is published. # Archiving Data for Camera-Ready Papers Once your manuscript is accepted for publication, convert the previously anonymized repository or OSF project into a public one, including version control. After doing this, download all included figures, data, and code as a .zip file and upload them to Zenodo. This archives your data and provides a stable DOI from Zenodo. Make sure to update the supplementary statement with the new information and links. #### Step 1: Make your repository/OSF project public Unless you already have a public repository, create a new public one on [Codeberg within the CALC project](https://codeberg.org/calc). Upload your data, figures and code manually (or `git push` directly from the terminal). Make sure to include a `README.md` file in which you list all the necessary information about your study, such as its title, name and affiliations of the authors as well as the correct citation. #### Step 2: Create a tag for version control The easiest way to do this on Codeberg is to click on the last commit in your repository (Here: "Adding All Code"). [![](https://wiki.calclab.org/uploads/images/gallery/2026-01/scaled-1680-/image-1767882702847-31-36-pm.png)](https://wiki.calclab.org/uploads/images/gallery/2026-01/image-1767882702847-31-36-pm.png) Once the new window opens, click on "Operations", select "Create Tag" in the dropdown menu and type in your version number (If this is the first version, v1.0). [![](https://wiki.calclab.org/uploads/images/gallery/2026-01/scaled-1680-/image-1767883258578-40-53-pm.png)](https://wiki.calclab.org/uploads/images/gallery/2026-01/image-1767883258578-40-53-pm.png) If everything went well, you should now see your version under tags on the main page of your repository! [![](https://wiki.calclab.org/uploads/images/gallery/2026-01/scaled-1680-/image-1767883586997-46-06-pm.png)](https://wiki.calclab.org/uploads/images/gallery/2026-01/image-1767883586997-46-06-pm.png) #### Step 3: Archive your current version on Zenodo Create a [Zenodo](https://zenodo.org) account if you don't have one. Click the + next to your profile icon and select "New upload". Upload your zipped files, fill in all required metadata (including funding details and a URL to your Codeberg repository), then under "Basic Information > Digital Object Identifier", select "No, I need one" to generate a unique DOI (It is created immediately, but takes a little while to activate). #### Step 4: Update the information in your manuscript The last step is to update your supplementary material statement in your manuscript and link both the Codeberg repository and the archived Zenodo files. You may use the statement provided under [Supplementary Material Statement in Papers](https://wiki.calclab.org/books/publications/page/supplementary-material-statement-in-papers).