Closed tchaddad closed 1 year ago
cc @ploewe
We might want to consider linking to https://doi.org/10.5281/zenodo.7976084 instead of '85 since zenodo claims '84 represents all versions.
We should probably also update/add the badge to:
Any others I missed?
I see geomoose-website was already updated.
I have added it to the wiki list.
you're absolutely correct @klassenjs we should always use the persistent DOI, 7976084 (I've updated the wiki)
I can login to the OSGeo Wordpress, but I can't find where to edit the project info to add the DOI.
Dear Jeff, dear Jim, dear geomoose community,
congratulations to minting a persistent software DOI for the geomoose project !
Maybe of interest: If members of the development team should have registered an ORCID (a persistent ID for persons), these personal IDs can be linked by the DOI to the software releases for automated updates (and due credit), whenever there's a new software release. PROJ picked up this practice using this earlier this year. Latest info here: https://doi.org/10.5281/zenodo.7889326 (slide 10).
Best,
Peter
@.***>
Gesendet: Samstag, 27. Mai 2023 um 14:32 Uhr Von: "Jeff McKenna" @.> An: "geomoose/gm3" @.> Cc: "Peter Löwe" @.>, "Mention" @.> Betreff: Re: [geomoose/gm3] Adding a DOI badge to the README.md (PR #836)
cc @ploewe
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
@jmckenna @ploewe Do you know how we can add the DOI badge to our OSGeo Project page? (slide 8) I can't find the right spot to edit that on the OSGeo Wordpress. When I try to edit the project I see the checklists, but where it looks like the project text should go is blank.
great, thanks @tchaddad !