Difference between revisions of "GitHub-Zenodo linkage"

From GRASS-Wiki
Jump to: navigation, search
m
m (How to integrate previous releases of GRASS GIS into Zenodo)
Line 39: Line 39:
 
==== How to integrate previous releases of GRASS GIS into Zenodo ====
 
==== How to integrate previous releases of GRASS GIS into Zenodo ====
  
Q: ''"The code base of GRASS GIS has been maintained in CVS/SVN since the late  1990s, I would be grateful for additional advice on how to proceed to avoid DOI-related blunders:''
+
'''Q:''' ''If possible, all GRASS releases should be made available for scientific  citation via Zenodo (overview over all releases here:  
 
 
''If possible, all GRASS releases should be made available for scientific  citation via Zenodo (overview over all releases here:  
 
 
* ''https://grass.osgeo.org/home/history/releases/''  
 
* ''https://grass.osgeo.org/home/history/releases/''  
 
* ''https://trac.osgeo.org/grass/wiki/Release ).''  
 
* ''https://trac.osgeo.org/grass/wiki/Release ).''  
Line 48: Line 46:
 
''So to be able to get a DOI for each major version of GRASS, as advised in  your previous response, can you please recommend an approach how to feed the sequence of previous major GRASS releases via GitHub into Zenodo, so  the DOI for the releases are in the proper sequence (DOI for GRASS 5.X referencing to the newer releases of GRASS6.x, 7.x, etc.) ?  
 
''So to be able to get a DOI for each major version of GRASS, as advised in  your previous response, can you please recommend an approach how to feed the sequence of previous major GRASS releases via GitHub into Zenodo, so  the DOI for the releases are in the proper sequence (DOI for GRASS 5.X referencing to the newer releases of GRASS6.x, 7.x, etc.) ?  
 
"''
 
"''
 +
 +
'''Answer:''' ''If you want to keep the history of releases in order, I would suggest you upload them in order of the release date (starting with the oldest one). Nevertheless, please notice that Zenodo sorts the releases by upload date and not by a version number. This means that any future release (e.g. minor versions of previous releases) will be simply the next one in the list by DateTime.... I hope I manage to explain it :) ''
  
 
== Options for future extensions ==
 
== Options for future extensions ==

Revision as of 03:36, 18 May 2019

GitHub - Zenodo Integration for GRASS GIS

Scope

This wiki-page provides information about the linkage between the GRASS GIS repository on GitHub and the data archive Zenodo. This includes the motivation why this is relevant for the GRASS GIS community, hands on advice from the Zenodo helpdesk how to do the task and strategic information about future development paths, as this is partially work in progress (scientific grade automated software citation by persistent identifiers).

Introducing Zenodo

Zenodo is a general-purpose open-access repository. It is developed under the European OpenAIRE program (a network of Open Access repositories, archives and journals that support Open Access policies) and operated by CERN. The services provided by Zenodo are based on an Open Source software stack. To users, including the GRASS GIS developer team, Zenodo provides long term archiving of digital content, including software.

Benefits for the GRASS GIS community

Long term archiving

Scientific citation by DOI

GitHub - Zenodo Integration

Generic Documentation

GRASS GIS specific Information

The following feedback was provided by the Zenodo helpdesk in Q1/Q2 2019 in advance of the GRASS github migration:

Many DOI for individual GRASS modules or rather a DOI for the GRASS GIS software framework ?

"Yes, in principle it's possible to issue DOIs for all modules, but I'm I don't think this is useful. You mention e.g. that it would be nice to cite both the overall system as well as individual modules. This will essentially "dilute" the citations over many DOIs and thus the citation count for GRASS will seem a lot lower than it actually is. Thus for getting credit, it's better to have one DOI per major version of the grass (where each version can have an updated author list). Also, having many DOIs makes it very difficult for discovery systems to track the citations automatically. Essentially Zenodo is the first system, where we can actually aggregate citations for all versions and a specific version of software."

"If you want to give credit to individual modules, I think it's better to then simply mention it. For instance, the journal text could mention it used module X, and the landing page of DOI for GRASS, could simply have a description detailing who did which module."

"We have now collected some 5000 citations to software in Zenodo, and what we can see for the top cited packages is that if the project provides a "citation recommendation" then people actually follow it. Example:"

How to integrate previous releases of GRASS GIS into Zenodo

Q: If possible, all GRASS releases should be made available for scientific citation via Zenodo (overview over all releases here:

The oldest GRASS release, which has been preserved as a tarball predates software versioning (GRASS 4.3. from 1999) All later releases are currently available in the current SVN repo ( https://trac.osgeo.org/grass/browser/grass/#branches)

So to be able to get a DOI for each major version of GRASS, as advised in your previous response, can you please recommend an approach how to feed the sequence of previous major GRASS releases via GitHub into Zenodo, so the DOI for the releases are in the proper sequence (DOI for GRASS 5.X referencing to the newer releases of GRASS6.x, 7.x, etc.) ? "

Answer: If you want to keep the history of releases in order, I would suggest you upload them in order of the release date (starting with the oldest one). Nevertheless, please notice that Zenodo sorts the releases by upload date and not by a version number. This means that any future release (e.g. minor versions of previous releases) will be simply the next one in the list by DateTime.... I hope I manage to explain it :)

Options for future extensions