Skip to content
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

Closed
d70-t opened this issue Feb 6, 2024 · 8 comments · Fixed by #40
Closed

archive on Zenodo? #35

d70-t opened this issue Feb 6, 2024 · 8 comments · Fixed by #40

Comments

@d70-t
Copy link
Contributor

d70-t commented Feb 6, 2024

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.

@trackow
Copy link
Contributor

trackow commented Feb 6, 2024

I would say yes, as I would like to cite your work somehow in the nextGEMS paper, and is easiest with a DOI :)

@lkluft
Copy link
Contributor

lkluft commented Feb 6, 2024

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.

@trackow
Copy link
Contributor

trackow commented Feb 6, 2024

@d70-t
Copy link
Contributor Author

d70-t commented Feb 6, 2024

What about this semi-automatic way?
https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content

Sure, if anything than that one.

@lkluft
Copy link
Contributor

lkluft commented Feb 6, 2024

We do have a CITATION.cff file at the top level or our repo. The Zenodo FAQs state that, if this file is present, they "make a best-effort attempt at parsing Zenodo-compatible metadata from it". So I would suggest that we update the file (@d70-t ORCiD is missing, @trackow needs to add himself) and setup a pipeline; and whatever metadata finds its way is there (authors and ORCiDs are amongst them).

@d70-t
Copy link
Contributor Author

d70-t commented Feb 6, 2024

I've added my ORCID to the draft PR #37, and cleaned up the file a bit. Open questions left:

  • do we want author's affiliations?
  • are we happy with the abstract (currently "Build indices and datasets from GRIB files.")
  • we should add the DOI (I'd go for the collection DOI only) to CITATION.cff, but we can only to that once we've got a first release out at Zenodo.

I've enabled this repository in Zenodo, so as soon as we've got a new Release here, it should also appear on Zenodo.

@d70-t
Copy link
Contributor Author

d70-t commented Feb 6, 2024

With #38 we should now also get the version correct upon a release...

@d70-t
Copy link
Contributor Author

d70-t commented Feb 6, 2024

DOI

@d70-t d70-t mentioned this issue Feb 6, 2024
@d70-t d70-t closed this as completed in #40 Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants