Hi Even, This seems like a good idea, as there are many academic users who will cite.
Not volunteering to take this on, but setting up a DOI is relatively easy with Zenodo and Github integration: https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content <https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content>. You’ll have a persistent DOI (points to latest), and then automatically generated DOIs for each release. I agree with Kurt about archiving files, but since these are a direct mirror of the files from the Github release, I don’t see the harm (storage on Zenodo is free). There may also be a way to configure Zenodo-Github integration to avoid storing a copy. Hopefully someone with admin on the GDAL Github repo can set this up pretty quickly. -David > On Jan 12, 2022, at 9:18 AM, Kurt Schwehr <schw...@gmail.com> wrote: > > I don't see a reason not to, but the question is what to point to. > > The GRASS link points to an RC, which doesn't feel right. It appears that > we'd be wanting to do a new doi for each release. Is that really what the > community wants? Does Zenodo want to be storing a tar for each release for > all time? This would make Zenodo yet another package distribution system, > which seems cra > > I would think it would be better to have simple doi entry with no attached > files that is updated with each release to mention the release with links and > hashes of the tar? > > I'm overloaded, so I can't take the lead on this. I do have this gist of me > playing with the doi system just over a year ago, if anyone is interested in > seeing how the API side of DOIs work. It uses absl.app, but that is easy to > replace. > > https://gist.github.com/schwehr/22ce6080eb9e730ef04fccfa25072e3a > <https://gist.github.com/schwehr/22ce6080eb9e730ef04fccfa25072e3a> > > On Wed, Jan 12, 2022 at 8:56 AM Even Rouault <even.roua...@spatialys.com > <mailto:even.roua...@spatialys.com>> wrote: > Hi, > > see below. Do we want to do that ? I'm not seeing any obvious disadvantage, > but I've never worked with DOI before. If so, anyone who want to take the > lead on that ? > > Even > > -------- Message transféré -------- > Sujet : DOI for the GDAL project / Springer Handbook of Geoinformatics > Date : Wed, 12 Jan 2022 17:23:40 +0100 > De : Peter Löwe <peter.lo...@gmx.de> <mailto:peter.lo...@gmx.de> > Pour : even.roua...@spatialys.com <mailto:even.roua...@spatialys.com> > > Hello Even, > > I'm writing to you as OSgeo Vice President for GDAL concerning an opportunity > for the GDAL project. Could you please forward the following message to the > GDAL PSC - or please tell me about a better way to contact the PSC directly ? > > Dear GDAL Project Steering Committee, > > I'm reaching out to you because of an opportunity for the PROJ community, > which surfaced recently: > The upcoming second edition of the Springer Handbook of Geoinformatics will > cover the GDAL project. The Handbook project has been delayed due to the > Pandemic, but will be completed in a few weeks. I am serving as the editor of > the Handbook chapter about Open Source Geoinformatics. > > Recently, new workflows for scientific citation of software projects have > emerged and are becoming state of the art. This includes references by > persistent digital object identifiers (DOI) to software projects instead of > URLs. DOI-based references allow to give due credit to the whole project > team, including first authors, developers, but also maintainers and people in > other roles. > > The OSGeo projects GRASS GIS, GMT, MapServer, MOSS and rasdaman have already > registered their own DOI, OSGeoLive, pygeoapi and pycsw will follow soon. > As an example, this is the DOI for GRASS GIS: > https://doi.org/10.5281/zenodo.5810537 > <https://doi.org/10.5281/zenodo.5810537> > Hands on information how to register a DOI for a OSGeo project are available > here: https://wiki.osgeo.org/wiki/Persistent_identifiers(pid) > <https://wiki.osgeo.org/wiki/Persistent_identifiers(pid)>. > > The Editors of the Springer Handbook agree that including DOI references for > Open Source projects is a win-win-scenario for the upcoming book and also the > OSGeo project communities. They have extended the production deadline until > January 20 to give additional software projects the opportunity to register a > DOI to be included in the book chapter. > > If the GDAL project reserves or registers a DOI (takes only a few minutes) > before the deadline of January 20, I would gladly include it in the Open > Source Geoinformatics chapter reference section. > > > Please let me know if you have any questions. > > Best, > Peter > > https://wiki.osgeo.org/wiki/User:Peter_Loewe > <https://wiki.osgeo.org/wiki/User:Peter_Loewe> > > <peter.lo...@gmx.de> <mailto:peter.lo...@gmx.de> > > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org <mailto:gdal-dev@lists.osgeo.org> > https://lists.osgeo.org/mailman/listinfo/gdal-dev > <https://lists.osgeo.org/mailman/listinfo/gdal-dev> > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
