I think this is useful (maybe because I'm an ex-academic) so I'll go ahead
and register both GeoServer and GeoTools tomorrow.

Ian

On Thu, 13 Jan 2022 at 15:44, Peter Löwe <peter.lo...@gmx.de> wrote:

> Hello Brad, all,
>
> unlike a URL, a DOI (
> https://en.wikipedia.org/wiki/Digital_object_identifier) will never break
> (no 404 error ever).
>
> The authors and editors for the Handbook project work without financial
> compensation by Springer and will not benefit from the number of volumes
> sold.
> The Open Source chapter aims to expose audiences, which still might
> believe that only facts are relevant when stated in cost intense non open
> access publications, to open source, open access, and open science.
>
> The Handbook will be around for at least five, maybe ten years. One reason
> for DOI (which will keep pointing to the latest Geoserver release, and
> maybe more up to date content (see #5 below) is to give added value to the
> readers and not to  bog them down with obsolete information.
>
> The Geoserver community can of course register a DOI whenever they agree
> to do so. I just want to make sure that all software projects covered in
> the Open Source chapter can make an informed decision whether they want to
> have their DOI referenced in the Handbook. Otherwise, the project URL will
> be used for reference.
>
> Some reasons for DOI for the Geoserver community are IMHO:
>
>  1) Little effort, no cost and significant benefits for everybody who's
> involved in GeoServer and can use scientific credit for their careers (->
> students, early career scientists, people on tenure track).
>  2) preservation of all code releases in an open access long term
> repository (https://en.wikipedia.org/wiki/Zenodo), free of charge and
> effortless for the project community
>  3) Reference by DOI is the way to go when citing anything with a long
> list of authors/committers: Geoserver has about _547_ committers according
> to GitHub, that's a lot.
>  4) When ORCIDs (https://orcid.org/) for persons serving as developers,
> maintainers, etc. are included into the committer - metadata
> (GitHub-sided), the DOI workflows will pick this up and will add due credit
> by reference to their citation lists.
>  5) DOI can be used to link information. This includes DOI for video
> recordings and presentations. Videos from FOSS4G events can now be linked
> to software project DOI and vice versa (and also linked to ORCIDs of real
> people), like this one: https://doi.org/10.5446/40822 :-)
>
> Does this help ?
>
> Cheers,
> Peter
> https://orcid.org/0000-0003-2257-0517
>
> <peter.lo...@gmx.de>
>
>
> > Gesendet: Donnerstag, 13. Januar 2022 um 04:01 Uhr
> > Von: "Brad Hards" <br...@frogmouth.net>
> > An: geoserver-devel@lists.sourceforge.net, "Peter Löwe" <
> peter.lo...@gmx.de>
> > Betreff: Re: [Geoserver-devel] DOI for the Geoserver project / Springer
> Handbook of Geoinformatics
> >
> > On Thursday, 13 January 2022 2:26:01 AM AEDT Peter Löwe wrote:
> > > Recently, new workflows for scientific citation of software projects
> have
> > > emerged and are becoming state of the art. This includes references by
> > > persistent digital object identifiers (DOI) to software projects
> instead of
> > > URLs. DOI-based references allow to give due credit to the whole
> project
> > > team, including first authors, developers, but also maintainers and
> people
> > > in other roles.
> > >
> > > The Editors of the Springer Handbook agree that including DOI
> references for
> > > Open Source projects is a win-win-scenario for the upcoming book and
> also
> > > the OSGeo project communities.
> > I'm not sure I understand what the advantage for geoserver is. I get
> that
> > Springer will sell more books. I don't see how having a DOI provides
> credit to
> > developers, maintainers or other people. How does it do that, and how
> does it
> > differ from a URL link in that respect.
> >
> > Can you clarify?
> >
> > Brad
> >
> >
> >
>
>
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 
Ian Turton
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to