On Thu, Nov 17, 2016 at 6:04 AM, Markus Neteler <[email protected]> wrote:
> The question for me is: what do we need to do for that? Since a DOI > refers to a state in time, GRASS GIS module DOIs might be attached to > releases since they evolve over time. How would that practically work? > There are some services which can give you DOI for SW. From what I understood, DOI for a specific version in version control is often encourage, but that wouldn't work if you want to add the DOI back to the source or documentation because you just advanced the version in version control. Associating DOI with release makes more sense but than what to do with addons which (at least usually) don't have releases? Also some modules don't change between releases of GRASS GIS. Does this mean same DOI or different one? Also, one module would accumulate different DOIs over time. Can we than accumulate number of citations for one module? Another idea (for core modules) is assigning DOI to GRASS GIS release and then use DOI with hash (...doi.../123456#r.slope.aspect) similarly to how the TBI AV-Portal references an exact time in a video. I hope Peter has a better idea if this makes at least some sense or it is completely off. Anyway, my current vision, partially related and partially unrelated, is to have a `Cite as` section in the manual unique for each module which would be generated from info stored in the parser information. Using parser is more flexible than putting it to the HTML directly and `Cite as` is more clear than including the info into `References` section. The info for `Cite as` can be DOI for the module or a paper associated with the module.
_______________________________________________ grass-psc mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-psc
