TuringDataStories
TuringDataStories copied to clipboard
alan-turing-institute
Mint a DOI per story for referencing
Summary
Create a DOI for each story, likely using Zenodo. This elevates the status of the story as more of an artefact and make a reference, citable output.
What needs to be done?
- [ ] Select a DOI service, e.g. Zenodo
- [ ] Work out how it works
- [ ] Do it
Who can help?
- @crangelsmith seems to be in the know ;)
Updates
Zenodo generates a DOI per repository (release). So it does not seem possible to get a DOI per page/file within a repository. I only did a quick search but it is not obvious to me that there are alternatives. A workaround is if each TDS is it's own repo that is then added to this main repo as a submodule. This also links to a separate discussion in #160 where this structure has been suggested as a solution to the scalability issue by @lukehare .
It might also be possible to become a member of an organisation such as CrossRef (it is not completely clear we would qualify but for example JOSS does this)- there seems to be an annual membership fee of $275 and then it costs $1 per DOI (https://www.crossref.org/fees/#content-registration-fees)