DOI for versioned releases

[ns-rse]

Currently we use a GitHub Action that adds tagged releases to University of Sheffield's Figshare Instance ORDA.

This has a major short-coming in so much as new releases are added to the existing entry and tagged/versioned releases do not have their own unique Digital Object Identifier (DOI).

An alternative solution as described here is to use Zenodo instead. However, a quick search reveals there are several GitHub Actions on the marketplace that are deprecated as of 2023 where Zenodo made some major changes which broke things.

A cursory search suggests the zenodo-upload action might still work though, but its not clear whether this mints a new DOI on each tag.

Some further research is required but ultimately

[MaxGamill-Sheffield]

We like this idea and using the DOIs internally for our releases so we know the versions etc, but the push is to get external authors to cite the papers for university metrics.