DOI-Zenodo badge broken? #862
Replies: 1 comment 3 replies
-
@Julian-Hochhaus Thanks -- I had not noticed that, but I see that too. That is, it is not just you ;) That badge should be pointing to https://zenodo.org/record/7810964, which sort of makes it look like everything is OK at Zenodo, but something is missing at doi.org. I reported that as an error at doi.org. Both https://zenodo.org/record/598352 (and so also https://doi.org/10.5281/zenodo.598352) redirect to https://zenodo.org/record/7810964. I don't really understand that - I thought each release was supposed to have a unique key. I guess we could update the badges to the 598352 badges, but that seems weird.... I think maybe more investigation is needed. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
For me, the doi bagde does not work, most interestingly, even on zenodo, the version number of the newest version 1.2.0 is not correctly resolved.
So the specific link to v.1.2.0 seems broken:
.. image:: https://zenodo.org/badge/4185/lmfit/lmfit-py.svg
:target: https://doi.org/10.5281/zenodo.7810964
in Markdown:
However, changing the target to the concept doi, which is always resolved to the latest version, works fine:
.. image:: https://zenodo.org/badge/4185/lmfit/lmfit-py.svg
:target: https://doi.org/10.5281/zenodo.598352
Markdown:
The version in the Readme:
.. image:: https://zenodo.org/badge/4185/lmfit/lmfit-py.svg
:target: https://zenodo.org/badge/latestdoi/4185/lmfit/lmfit-py
Markdown:
does not work for me either.
Maybe there is something wrong on my side, however I can't find out, whats wrong here.
Beta Was this translation helpful? Give feedback.
All reactions