Create Zenodo account/storage area for the project

[harisood]

Summary of issue

To share resources effectively, we're going to use Zenodo. We need to make sure this is set up properly to make it easy to share resources for the duration of the project.

this links into #1

What needs to be done?

• [x] Understand how Zenodo works
• [ ] Set up a Zenodo for the project
• [ ] Test it by sharing slides from kick-off sessions

Who can help?

• @drchriscole
• @cianodonovan

Issue checklist

• [X] I have assigned the appropriate work package label to this issue, and added any other relevant labels
• [X] I have added this to the SATRE backlog (public) project board
• [X] I have assigned this issue to at least one person on the SATRE team

[cianodonovan]

Thanks for the run-through @harisood

[drchriscole]

To use Zenodo I would recommend the following:

• sign-in with your github - will aid linking github releases with zenodo DOIs (more later)
• Uploads require a lot of detail and can a little while. Doesn't need to be done all once
  • Important any published upload cannot be deleted or modified
  • Metadata can be updated after publishing however
• Uploads are versioned so updates to content can be made, thereby generating a new DOI
  • all versions can be references by a single DOI or you can refer to a specific version with it's own DOI. Nice feature.

Github releases

This is a really useful feature to automatically create DOIs for specific releases of code. This will be equally relevant for different versions of the specification. Read this brief documentation, first.

Gotchas that aren't mentioned:

• only public repositories are visible to Zenodo
• link gh to zenodo before making the first release
• The "authors" of a github release are by default all the gh contributors. This can be edited and updated.
• as per above a release can't be deleted in Zenodo, but metadata can be.

[drchriscole]

• [x] Add SATRE org to zenodo