CLEX Code Collection
You can now publish the code you use for your research with the new CLEX Code Collection on Zenodo (CCC). More publishers are now requiring code to be published alongside data. We hope the Zenodo community will also serve as a way to share our codes in a user-friendly way. So even if you are not required to publish your code you can see this collection as an opportunity to share your work with others.
Zenodo is an initiative funded by CERN that allows anyone to share their research outputs and attach to them a DOI. Zenodo is funded for at least the next 20 years and so it offers a good long-term solution, as well as been widely used internationally.
We will curate the Collection for the duration of CLEX, but the records will be still available and visible well past CLEX termination.
How to publish
Publishing your code is easy and quick as long as your code is reasonably organised and has a detailed Readme file.
- Create a Zenodo account, you can use your ORCID to login if you have one.
- Create a Zenodo record for your code, uploading the relevant files. We prepared a step-by-step guide on how to do this, which also cover the kind of information you should include.
- Choose the CLEX Code Collection as community. We will get a notification of your request. Remember your code can be listed in more than one community.
- We will receive your request to join the CCC and check that you code is well described and in line with the Collection policies. If any changes are needed, we will contact you.
- A code can have several authors, they all should agree to the code publication and to list the record in the CLEX Code Collection. All authors should have made a significant contribution to the code, you can refer to the CCC authorship policy if in doubt.
- Having your code on a version control repository (and possibly github) is highly recommended but it is not a requirement to publish on Zenodo, you can still publish your code without one.
- If you have your code in a github repository you can give Zenodo access to your repository and every time you create a new release you Zenodo record will be updated automatically. <link>
- Every time you change files you have to create a new version of the record and a new DOI will be minted. Any other field can be updated at any time without need for the record to be republished.
- If you do not want to create your own Zenodo account we can create a record for you. In that case, let us know that you want to publish via the helpdesk. If your code is well documented, it might take as little as 20 minutes for us to add your repository to the Zenodo community. Please note that having your own Zenodo account will give you more control on your code. It is especially recommended if you are likely to release new versions in the future, as we might not be able to set up automatic updates as the owner of the record might be different from the GitHub repository owner.
We set up policies covering the use and contribution to the Collection. These are shown if full on theZenodo community page, but can also be downloaded here.
- The CCC scope: outlining the scope of the collection and the main requirements for a code to be accepted.
- The Authorship policy: this is based on the Australian Code for the Responsible Conduct of Research (2018) and covers who can be considered and author or a collaborator.
- Contributors guidelines: more in depth guidelines on how to contribute code to the Collection.
- Retention and Retraction policy: defining the few cases in which we might retract a record and the procedure we will follow.
Because we are using the Zenodo platform also any policy set by Zenodo has to be honoured.
We are not checking the quality of your code, as long as the Collection policies are satisfied and your code is in line with the Collection scope it will be accepted. The only requirement currently is for your description of the code to be reasonably comprehensive. However, if you would like some advice and feedback on a code, we are happy to help you. As usual you can contact us via the CWS helpdesk.