-
Notifications
You must be signed in to change notification settings - Fork 6
Description
What happened:
Clicking on the DOI badge link of several rendered cookbooks in the gallery returns "DOI not found". For instance: https://projectpythia.org/cesm-lens-aws-cookbook/ (and many others)
What is interesting is that this doesn't happen in the repositories' README DOI links. Investigating the URLs of the DOI badges:
This is what I get from the rendered cookbook: https://doi.org/10.5281/zenodo.509240024
This is what is coming from the repo: https://zenodo.org/badge/latestdoi/509240024
Zenodo now provides DOI links for projects slightly differently, and it can definitely be applied to all of our cookbooks, but rather than going that route first, figuring out why the badge link is changing throughout rendering might be better.
@jukent @dcamron any thoughts?
See this comment below for the current status of the problem.
The ESGF Cookbook was spared because it's been hard-coded. The core issue is that our only method of automatically generating badge links before first release depends on pulling out the unique GitHub API repository ID and the convenient and poorly documented/supported zenodo latestdoi redirect based on this ID.
I do not believe there is currently any other way to automatically guess a valid Zenodo DOI link before cutting a release (which is kind of the point.) There are multiple solutions to use DOIs as they're intended to be used, but that's less simple to automate and must be edited after release.
No, there has not been any motion on MyST's part in mangling the latestdoi redirect links …
Metadata
Metadata
Assignees
Labels
Type
Projects
Status