Releasing a Lesson#

Making regular releases of your lesson gives you and your contributors an opportunity to celebrate the improvements that have been made, and make it easier for them to receive credit and recognition for the work they have put in. It is particularly important to release the lesson when it reaches key milestones in its development, e.g. before beta pilot workshops or when it reaches a stable state.

If you publish the lesson on Zenodo when you release it, you will receive a Digital Object Identifier that you and others can use to refer to the lesson and/or a particular version. Publishing the lesson makes it more findable by other people, and – if you include your ORCID iD identifier in the information about its authors – helps you list the project on your public profile.

Preparing for a release#

Updating citation information#

Lesson repositories can contain citation information in Citation File Format. The Collaborative Lesson Development Training curriculum includes some discussion of why you should include this file in your lesson repository. The Carpentries Workbench documentation describes in more detail how the file can be included in the repository and gives an example.

We recommend that you keep citation information updated as you progress with lesson development and maintenance. At the very least, you should ensure that the information in your CITATION.cff is current before releasing a new version of your lesson because this will simplify the process of releasing it to Zenodo.

Publishing the lesson on Zenodo#

  • First, create a Zenodo account if you do not already have one, linked to your GitHub credentials

  • Log into Zenodo and select ‘GitHub’ from the dropdown menu at the top-right

  • On that page, find the name of your lesson repository in the listing and turn the switch ‘On’ to activate the Zenodo/GitHub integration

  • Make a release of your lesson from its GitHub repository

  • This will create a Zenodo record from that release. Zenodo will update this record with a new version every time you make another release from your lesson repository.

  • Edit the Zenodo entry to adjust anything that is not right. For example, the presence of a CITATION.cff file in your repository will make Zenodo think this is a record describing software. You can correct this to ‘Lesson’ in the Resource Type field.

  • Add the DOI for your record to the README.md and CITATION.cff files in your lesson repository. The record created from your release will include two DOIs: one for the specific version released this time, and a second ‘top level’ DOI that will always resolve to the latest version of the lesson released. We recommend that you add the ‘top-level’ DOI to the files in your lesson repository. Zenodo gives you Markdown code to display a ‘badge’ icon e.g. DOI on your repository README. Look for the DOI field in the Details box on the right of the record page to find your badge.