[GRASS-PSC] GRASS DOI

Tue Jan 4 07:39:29 PST 2022

Dear Helena and all,

Yes, it is auto-generated by Zenodo. It was the first step - to get a DOI
(main one and one for each release). Now we need to decide what is right
for the authors list.

The current one looks messy. That is true. However, is it wrong? Or, in
what way is it wrong?

GitHub handles might be appropriate when that's all people choose to reveal
on GitHub, although it looks wrong in academia. However, looking at the
list, it is likely that some people just never came around to adding their
name to GitHub (while having it in the source code). Some others have just
part of their name, all-caps name, and yet some others have their name in
two languages.

Author order is derived from GitHub > Insights > Contributors [1] which is
mostly good from a software maintenance perspective (recency and line
volume). How well it represents the order of contributors in terms of
credit is a question related to the whole "academic credit for software"
debate. The whole auto-generated list can be in this case replaced by a
CITATION.cff file which Zenodo will now pick up and use.

Action item 1: Add or improve your name on GitHub. Use whatever you would
use when authoring a paper or a book. This name may also show in your
commits. See also what `git config --get user.name` gives you.

Action item 2: See where you are in the list or if you are even there.
Discuss on the grass-dev mailing list or complain to me privately how to
better represent your contribution.

I would be happy to discuss other ideas people have. Just let me know,
e.g., on grass-dev.

Best,
Vaclav

[1] https://github.com/OSGeo/grass/graphs/contributors
[2] https://doi.org/10.5281/zenodo.5176030

On Mon, Jan 3, 2022 at 4:02 PM Helena Mitasova via grass-psc <
grass-psc at lists.osgeo.org> wrote:

> Peter Loewe is including the OSGeo projects' DOI in the Springer Handbook
> chapter about open source geospatial
> and we noticed that the authors names are messy (some are just ID) - I
> assume that this is autogenerated and I am wondering
> what would be the best way to fix it. Vashek, did you set this up? Do you
> have any suggestions?
> Here is the GRASS DOI link
> https://doi.org/10.5281/zenodo.5810537
>
> Thank you, Helena
>
> Helena Mitasova
> Professor, Department of Marine, Earth and Atmospheric Sciences
> Faculty Fellow, Center for Geospatial Analytics
> North Carolina State University
> Raleigh, NC 27695-8208
>
>
> ---------- Forwarded message ---------
> From: Peter Löwe <peter.loewe at gmx.de>
> Date: Mon, Jan 3, 2022 at 11:09 AM
> Subject: Aw: Re: Open Source Chapter of the Springer Handbook of
> Geoinformation: Status update / New Deadline / Opportunity
> To: Helena Mitasova <hmitaso at ncsu.edu>
>
>
> Helena,
>
> I just checked the DOI landing page for GRASS GIS (
> https://doi.org/10.5281/zenodo.5810537).
> It's amazing to see how the content has grown.
>
> One minor detail: Your name shows in the list of authors in uppercase
> letters, unlike the other authors. Is this intended ?
>
> 1. Martin Landa, Markus Neteler, Markus Metz, Anna Petrasova, glynnc,
> HamishB, Vaclav Petras, huhabla, Huidae Cho, Luca Delucchi, Pietro, Michael
> Barton, Yann Chemin, Tomas Zigo, Māris Nartišs, ostepok, Helmut Kudrnovsky,
> mlennert, nilason, Stefan Blumentrath, William Kyngesburye, Linda
> Kladivova, aghisla, Veronica Andreo, 積丹尼 Dan Jacobson, Denis Ovsienko,
> madi, HELENA MITASOVA, Carmen Tawalika, Caitlin H.: OSGeo/grass: GRASS GIS
> 8.0.0RC1, (2021)
>
> Cheers,
> Peter
>
> <peter.loewe at gmx.de>
>
>
> > Gesendet: Sonntag, 26. Dezember 2021 um 04:57 Uhr
> > Von: "Helena Mitasova" <hmitaso at ncsu.edu>
> > An: "Peter Löwe" <peter.loewe at gmx.de>
> > Cc: "Markus Neteler" <neteler at osgeo.org>
> > Betreff: Re: Open Source Chapter of the Springer Handbook of
> Geoinformation: Status update / New Deadline / Opportunity
> >
> > Peter,
> >
> > Thank you for sharing the proof - the GRASS history and section looks
> good to me, just a minor request if possible -
> > For the Fig. 30.2 would it be possible to add GRASS GIS to the caption?
> Something like this
> > Examples of geospatial modeling and analysis in GRASS GIS with 2D/3D
> raster data, vector data and tangible interaction.
> >
> > Thank you and let's hope for a Happy New Year,
> >
> > Helena
> >
> > > On Dec 23, 2021, at 4:42 AM, Peter Löwe <peter.loewe at gmx.de> wrote:
> > >
> > > Dear co-authors of the Open Source Chapter of the Springer Handbook of
> Geoinformation,
> > >
> > > I hope you are all in good health, ready for the upcoming holiday
> season and the new year.
> > >
> > > Work on the Springer Handbook of Geoinformation has progressed.
> Corrections and updates for all chapters are being implemented and checked.
> The Handbook is now scheduled to be published in 2022.
> > >
> > > A new proof of our chapter is available here:
> https://www.le-tex.de/dbdownload/6oAP4r6MyilKUIufQzXwRgnp29tm5OSIiLiCtcdp/M_3_030_proof_2.pdf
> > >
> > > A few minor quirks have been noted in the proof, which will be fixed.
> > >
> > > The Editors are asking us to review the proof and indicate any
> additional corrections before January 6, if necessary.
> > >
> > > Please note that any changes in the chapter text are at this stage
> limited to typographical errors and serious errors of fact.
> > > Please review the parts of the document you have written and send me
> your corrections before January 6, if necessary.
> > >
> > > In addition, I would like to point out an opportunity which has
> emerged due to recent advances in scientific citation for software projects
> with Digital Object Identifiers (DOI).
> > > In the last months, improved options for the citation of open source
> software projects have become available.
> > > In a nutshell, any open source software project which is hosted on
> GitHub (e.g. all OSGeo projects) can now be linked to the scientific Open
> Access repository Zenodo (www.zenodo.org)
> > > based on a persistant identifier (DOI), which can be used for
> scientific citation, as in our chapter.
> > >
> > > Unlike a URL, a DOI can never "break" and it is guaranteed to point to
> the lastest version of the software, which would be added value for the
> readers of our chapter.
> > >
> > > In addition (this is new), the DOI reference can provide due
> scientific credit to the whole project team (first authors, developers,
> maintainers, etc.).
> > > This is an emerging approach, which was first rolled out for
> GitHub/Zenodo, there are also ongoing efforts to establish this for
> GitLab-based software repositories.
> > >
> > > This creates a win-win-win situation, as our chapter will receive its
> own DOI (as an individual book chapter, linked to the DOI of the overall
> Handbook), which will be linked (for scientific credit from citation) to
> the ORCIDs of all Coauthors, but _also_ to the software project DOIs and
> their respective teams (and their names/ORCIDs). With the new edition of
> Springer Handbook becoming the new reference in this field of Science,
> > > the new DOI mechanism ensures that the open source projects receive
> their (over)due share in scientific credit and recognition.
> > >
> > > Both the GRASS GIS and the MOSS project are already using DOI (->
> References [3]-> https://doi.org/10.5281/zenodo.5559460 and [6] ->
> https://doi.org/10.5281/zenodo.5140319 in our chapter).
> > > The OSGeoLive project is currently discussing to obtain a DOI shortly.
> > >
> > > Registering a DOI can be achieved in a few minutes by persons with
> admin rights to the respective GitHub repository.
> > > The metadata related to the DOI can also be edited and extended later,
> after the DOI has been minted (and is included in the Reference Section of
> our chapter).
> > >
> > > Please contact me if you believe that a geospatial project covered in
> our chapter might be interested (and able) to obtain a DOI before January
> 6, so it could be included in our chapter.
> > >
> > > More information on this is available here:
> > > - OSGeo AGM presentation (
> https://docs.google.com/presentation/d/1brbBb7-sKRI6U4dZ7LKnBT_-NnWzyS2TaZqVXzy8RDo/edit#slide=id.p4
> [slides 93-94])
> > > - Hands on howto: https://guides.lib.berkeley.edu/citeyourcode
> > > - Example of a CFF file to be included in a GitHub repo to be used for
> automated updates on authors, etc:
> https://github.com/OSGeo/MOSS/commit/2324a69add200f726640904f0084bec83d50bbde
> > >
> > > Best regards, happy holidays and a happy new year,
> > > Peter
> > >
> > > <peter.loewe at gmx.de>
> > >
> >
> >
> _______________________________________________
> grass-psc mailing list
> grass-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-psc/attachments/20220104/95215bbe/attachment-0001.html>