Workflow to generate releases and DOIs at ZENODO #326
cofinoa
started this conversation in
Comments and ideas for changing CF
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Topic for discussion
Dear @cf-convention/info-mgmt
With the new adoption of minting DOIs at Zenodo (cf-convention/cf-conventions#513), I think, we need to discuss how the releases and DOI depositions at Zenodo should be handled.
Because file depositions are curated and, no changes on them are possible after being published, then a manual review step should be available, just before publishing definitely into Zenodo. Github releases are more flexible, and they can be removed, renamed, etc .... but Zenodo publication it's not like that, and IMO extra care should be taken to avoid Zenodo versions pollution. To this purpose, the Github action which is being fired when a new release is published, at GH, a step can be added to deposit the release at Zenodo, as draft, for later review and publish, if review is being passed. This step, also can add to the deposit, the HTML and PDF, rendered documents and not just the SOURCE. This draft, step, also has an advantage, and it is that a temporal DOI it's provided, and therefore it can be used and included in the different documents rendered.
We need also to have a more community driven Zenodo's publication process, where more than one individual has permissions to update the version of the deposit, and publish the draft. To this purpose I have created, with testing purposes, a Zenodo community:
https://zenodo.org/communities/cfconventions
If you want the full details on Zenodo communities have a look at its doc:
https://help.zenodo.org/docs/communities/
With Zenodo communities we can have multiple users, with different roles (Reader, Curator, Manager, Owner):
https://help.zenodo.org/docs/communities/about-communities/
(@ethanrd I have invited your Zenodo's user to become owner of the community)
and have a review process for submissions to the community:
https://help.zenodo.org/docs/communities/review-submissions/
Please, let me know your thoughts and if it worth it to draft a preliminary Github action and check the community.
Note: To test purposo, Zenodo has a sandbox endpoint, to test and play with deposits:
Beta Was this translation helpful? Give feedback.
All reactions