Ok, I went ahead with a manual upload of GDAL 3.4.1:
https://zenodo.org/record/5884352 , with concept DOI being
https://zenodo.org/record/5884351
Can you ask the zenodo help desk to link the later with the github
releases of https://github.com/OSGeo/GDAL ?
Same for PROJ 8.2.1: https://zenodo.org/record/5884395, with concept DOI
being https://zenodo.org/record/5884394, to be associated with
https://github.com/OSGeo/PROJ
Even
Le 20/01/2022 à 15:37, Peter Löwe a écrit :
Hi,
FYI here's the confirmation by Zenodo about the combined use of manual and
automated software versioning:
"It is possible to link manual releases to the GitHub integration automated
workflow.
You can go ahead and publish the two manual releases and share them here.
We will then link them to the equivalent GitHub repositories so that when you
activate the integration new versions will continue under the same Concept DOIs of
the manual releases"
-> the two repos being referred to are PROJ and GDAL.
I will not be ablé to act on this as I do not have admin access to neither the
GDAL nor the PROJ repo.
Best,
Peter
<peter.lo...@gmx.de>
Gesendet: Donnerstag, 20. Januar 2022 um 10:16 Uhr
Von: "Peter Löwe" <peter.lo...@gmx.de>
An: gdal-dev@lists.osgeo.org
Betreff: [gdal-dev] Fwd: DOI for the GDAL project / Springer Handbook of
Geoinformatics
Hello gdal-dev-list,
regarding the current discussion on how to register DOI for GDAL, I've
contacted the helpdesks of Zenodo and DataCite. DataCite is the organisation
providing the global DOI-infrastructure. Zenodo is an open access repository
where a growing number of OSGeo projects already have registered DOI for their
codebases.
The question is whether once a DOI for GDAL has been registered
manually/retrospectively for the current release (GDAL 3.4.1) it will be
feasible to switch to automated DOI versioning for all future GDAL releases.
The DataCite helpdesk confirms, this approach from their infrastructure perspective:
"From the DataCite side I don't see anything that would mean the manual workflow
could not change to an automated one, but this is something that Zenodo would need to
confirm."
The Zenodo helpdesk confirmed this approach last night: "We can actually connect this record
to a "virtual" release on our side as if it was actually part of the Github repo. Could
you give us more details, for example, the records in question and the GitHub repos?".
-> I have told them that this applies to GDAL (among other projects). No
response yet.
Maybe someone of the project community is interested and able to contact the
Zenodo help desk directly on this (i...@zenodo.org) ?
The deadline to include a DOI for the GDAL project to the Open Source Chapter
of the Springer Handbook on Geographic Information is today end of business
Pacific Time.
By now, ten OSGeo projects will have their DOI referenced in the Chapter (more
to come in the next hours). It would be awesome if GDAL could be included, too.
Best,
Peter
<peter.lo...@gmx.de>
_______________________________________________
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
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
