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

Detect and display DOIs that are generated by Zenodo's integration with GitHub #5745

Open
kathy-t opened this issue Nov 16, 2023 · 3 comments
Assignees
Milestone

Comments

@kathy-t
Copy link
Contributor

kathy-t commented Nov 16, 2023

Is your feature request related to a problem? Please describe.
Zenodo is able to generate a DOI for each release of a GitHub repository. There are details about it here. These releases may be workflow versions that exist on Dockstore.

Describe the solution you'd like
Investigate if Dockstore is able to detect DOIs that are generated from this Zenodo/GitHub integration. If we're able to detect them, we should save and display them in the UI.

Describe alternatives you've considered
n/a

Additional context
n/a

┆Issue is synchronized with this Jira Story
┆Fix Versions: Dockstore 1.16
┆Issue Number: DOCK-2493
┆Sprint: 136 - Izmir
┆Issue Type: Story

@coverbeck
Copy link
Contributor

Some observations:

  • When Zenodo creates a DOI for a GitHub release, the DOI has a reference to the GitHub repo, but not vice-versa. We will need to query Zenodo to figure this out.
  • It looks like Zenodo creates versions for the different branches, under one "concept" DOI. Which I think is what Dockstore does when creating DOIs as well.
  • It looks like we can use the Zenodo search API. Still figuring out details about how to construct the query. So far, just using curl, I can do it anonymously. Not sure if I'll run into rate limits though.

@coverbeck
Copy link
Contributor

@unito-bot
Copy link

➤ Charles Overbeck commented:

Consider done for one-time harvesting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants