Hi Vaclav, all,
 
it's great to hear that the GRASS project is about to embrace DOI and long term archiving by Zenodo.
 
The MOSS project minted its first DOI as a proof concept in the process of becoming a OSGeo heritage project (https://zenodo.org/record/4719685#.YKzpGKgzaUk). For this, we used stakeholders roles according to MARC21 like the R project does: https://journal.r-project.org/archive/2012-1/RJournal_2012-1_Hornik~et~al.pdf
 
BTW, ways to retro-provide DOI versioning for previous GRASS releases would be an rewarding topic to discuss with Data Cite (the DOI infrastructure community). DOI for software versioning is is still a developing topic. Feedback from the GRASS community would be valuable to push this forward.
 
Best,
Peter
 
<peter.lo...@gmx.de>
 
 
Gesendet: Montag, 24. Mai 2021 um 04:08 Uhr
Von: "Vaclav Petras" <wenzesl...@gmail.com>
An: "grass-dev@lists.osgeo.org" <grass-dev@lists.osgeo.org>
Cc: "Peter Löwe" <peter.lo...@gmx.de>
Betreff: [release planning] Enable Zenodo before 7.8.6 and 8.0.0
Hi all,
 
Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get DOIs and Zenodo records.
 
Solving the whole DOI linking and Zenodo archiving for the old versions may be complex [1], but enabling the link between GitHub and Zenodo is trivial (one click) and every newly created GitHub release (we do those) will be automatically registered and receive DOI.
 
Zenodo uses a system of DOI versions and a main DOI (Concept DOI). Whether it is an ideal system, that's a question, but it is currently the expected one since it is the same for everything on Zenodo. It is used automatically when using the GitHub-Zenodo integration.
 
It seems I have the permissions to enable it for GRASS GIS. The one who enables that becomes a maintainer of it. I'm fine with that, but I won't be uploading any older versions. The maintainer can be changed later by contacting Zenodo support [2].
 
Although there are things to figure out in terms of next steps, I don't see much risk in enabling it. There are no choices available in the setup or in terms of alternatives. DOI and some kind of registration are expected more and more.
 
Thoughts?
 
Vaclav
 
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to