-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add DOI badge #362
Add DOI badge #362
Conversation
Looks goot me to.
Not sure what you refer to? |
content/about/license.md
Outdated
@@ -56,7 +58,8 @@ scientific work written in LaTeX.</p> | |||
organization = {Open Source Geospatial Foundation}, | |||
address = {USA}, | |||
year = {2022}, | |||
url = {https://grass.osgeo.org} | |||
url = {https://grass.osgeo.org}, | |||
doi = {10.5281/zenodo.7764250} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
think this could be passed to a variable. That way it is going to be easier to maintain. Please check out the grass.json
file. Can add something like: grass_doi:10.5281/zenodo.7764250
. Then in the file you can use an inline shortcode (dont fully remember if that is how they call it in Hugo), something like what happens in manuals.md
:
first time you use it in the file would be like:
{{< grassDoi.inline >}}{{- .Site.Data.grass.grass_doi -}}{{</grassDoi.inline >}}
and later only {{< grassDoi.inline />}}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @nobeeakon, I'll have a look at this and try... But this sounds what I wanted indeed, so when a new version is released and gets a new doi, we only update the variable...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can use the stable DOI https://doi.org/10.5281/zenodo.5176030 that points to the latest release (the last release done, not release with highest version number). So there shouldn't be any reason to change that, unless we want for the DOI to always refer to the release with highest revision number.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! I was searching for this one originally, now I see I didn't see the fine print... eheh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
self review :P
I have added the DOI badge for 8.2.1 in the Licence page and also included the doi in the bibtex string. Would be nice to somehow automate it though