-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
archive on Zenodo? #35
Comments
I would say yes, as I would like to cite your work somehow in the nextGEMS paper, and is easiest with a DOI :) |
I would argue that it is easiest with a commit id 😉 But I agree that scientists have a hard time to accept that, which might justify the creation of a DOI to prevent tedious discussions during reviews. |
What about this semi-automatic way? |
Sure, if anything than that one. |
We do have a |
I've added my ORCID to the draft PR #37, and cleaned up the file a bit. Open questions left:
I've enabled this repository in Zenodo, so as soon as we've got a new Release here, it should also appear on Zenodo. |
With #38 we should now also get the version correct upon a release... |
Do we want to archive
gribscan
on Zenodo? - We'd be able to get a DOI for this project then, but do we want this?If we do, we could do this similar to eurec4a/eurec4a-intake#147, where the details for filling out the required forms are stored in
.zenodo.json
.Currently, the contributors are @lkluft, @trackow and @d70-t. In case we do want to publish this on Zenodo, everyone would have to fill out their information in the
creators
object. See docs here.The text was updated successfully, but these errors were encountered: