<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Hi Even,</span><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">This seems like a good idea, as there are many academic users who will cite.</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Not volunteering to take this on, but setting up a DOI is relatively easy with Zenodo and Github integration: <a href="https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content" class="">https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content</a>. You’ll have a persistent DOI (points to latest), and then automatically generated DOIs for each release.</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">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.</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Hopefully someone with admin on the GDAL Github repo can set this up pretty quickly.</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">-David</div><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 12, 2022, at 9:18 AM, Kurt Schwehr <<a href="mailto:schwehr@gmail.com" class="">schwehr@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I don't see a reason not to, but the question is what to point to. <div class=""><br class=""></div><div class="">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<div class=""><br class=""></div><div class="">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?<br class=""><div class=""><br class=""></div><div class="">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.</div></div></div><div class=""><br class=""></div><div class=""><a href="https://gist.github.com/schwehr/22ce6080eb9e730ef04fccfa25072e3a" class="">https://gist.github.com/schwehr/22ce6080eb9e730ef04fccfa25072e3a</a><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 12, 2022 at 8:56 AM Even Rouault <<a href="mailto:even.rouault@spatialys.com" class="">even.rouault@spatialys.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><p class="">Hi,<br class="">
</p>
<div class="">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 ?<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Even</div>
<div class=""><br class="">
</div>
<div class="">-------- Message transféré
--------
<table cellspacing="0" cellpadding="0" border="0" class="">
<tbody class="">
<tr class="">
<th valign="BASELINE" nowrap="" align="RIGHT" class="">Sujet :
</th>
<td class="">DOI for the GDAL project / Springer Handbook of
Geoinformatics</td>
</tr>
<tr class="">
<th valign="BASELINE" nowrap="" align="RIGHT" class="">Date : </th>
<td class="">Wed, 12 Jan 2022 17:23:40 +0100</td>
</tr>
<tr class="">
<th valign="BASELINE" nowrap="" align="RIGHT" class="">De : </th>
<td class="">Peter Löwe <a href="mailto:peter.loewe@gmx.de" target="_blank" class=""><peter.loewe@gmx.de></a></td>
</tr>
<tr class="">
<th valign="BASELINE" nowrap="" align="RIGHT" class="">Pour : </th>
<td class=""><a href="mailto:even.rouault@spatialys.com" target="_blank" class="">even.rouault@spatialys.com</a></td>
</tr>
</tbody>
</table>
<br class="">
<br class="">
Hello Even,<br class="">
<br class="">
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 ?<br class="">
<br class="">
Dear GDAL Project Steering Committee,<br class="">
<br class="">
I'm reaching out to you because of an opportunity for the PROJ
community, which surfaced recently:<br class="">
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.<br class="">
<br class="">
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.<br class="">
<br class="">
The OSGeo projects GRASS GIS, GMT, MapServer, MOSS and rasdaman
have already registered their own DOI, OSGeoLive, pygeoapi and
pycsw will follow soon.<br class="">
As an example, this is the DOI for GRASS GIS:
<a href="https://doi.org/10.5281/zenodo.5810537" target="_blank" class="">https://doi.org/10.5281/zenodo.5810537</a><br class="">
Hands on information how to register a DOI for a OSGeo project are
available here:
<a href="https://wiki.osgeo.org/wiki/Persistent_identifiers(pid)" target="_blank" class="">https://wiki.osgeo.org/wiki/Persistent_identifiers(pid)</a>.<br class="">
<br class="">
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.<br class="">
<br class="">
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.<br class="">
<br class="">
<br class="">
Please let me know if you have any questions.<br class="">
<br class="">
Best,<br class="">
Peter<br class="">
<br class="">
<a href="https://wiki.osgeo.org/wiki/User:Peter_Loewe" target="_blank" class="">https://wiki.osgeo.org/wiki/User:Peter_Loewe</a><br class="">
<br class="">
<a href="mailto:peter.loewe@gmx.de" target="_blank" class=""><peter.loewe@gmx.de></a><br class="">
<br class="">
<br class="">
</div>
</div>
_______________________________________________<br class="">
gdal-dev mailing list<br class="">
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank" class="">gdal-dev@lists.osgeo.org</a><br class="">
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank" class="">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br class="">
</blockquote></div>
_______________________________________________<br class="">gdal-dev mailing list<br class=""><a href="mailto:gdal-dev@lists.osgeo.org" class="">gdal-dev@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/gdal-dev<br class=""></div></blockquote></div><br class=""></body></html>