[Esip-preserve] Esip-preserve Digest, Vol 86, Issue 14

Tue Mar 29 17:33:26 EDT 2016

Software is an interesting beastie to deal with. USGS is wrestling with
this right now as we get ready to put out a long awaited (and overdue for
update) software release policy. As we're starting to work use cases
through our review and approval machinery and meet up with some parts of
the organization already out ahead on this (e.g., those projects on the
official USGS GitHub org <https://github.com/usgs>), we've been fairly
intensively discussing the issue of software citation, and more
importantly, management of software that is citable.

In US government, we have this other interesting dynamic in an Office of
Management and Budget policy that says we are supposed to provide a ".gov"
option for accessing government information if we use some third party
distribution mechanism (e.g., GitHub, CRAN, etc.). So, one of the things
we've been looking at is a Zenodo-type option that drops a snapshot on a
gov server (USGS ScienceBase in this case) and mints one of our DOIs for
it. That kind of kills two birds with one stone - snapshots a version of
the software for citation and ensures that there is a .gov option for
obtaining the content. We think this will cover quite a number of our use
cases.

Software is a bit different than data, but some of the same principles from
the RDA dynamic citation working group recommendations also apply. Source
control solutions give software a leg up if good coding practices are
followed. I do recognize a couple of ESIPers on the group (e.g., Matt
Jones), and I would certainly hope that the group is considering
software dynamicity up front instead of having to spin up a group down the
road to work on "dynamic software citation."

They do have this in there...

"Software citations should facilitate identification of, and access to, the
specific version of software that was used.  Software identification should
be as specific as necessary, such as using version numbers, revision
numbers, or variants such as platforms."

...which I would combine with this one...

"A software citation should include a method for identification that is
machine actionable, globally unique, interoperable, and recognized by a
community."

...to have unique, machine actionable identifiers (blah, blah, blah) for
citable software versions.

At any rate, we're very interested in this and will stay tuned for further
conversation.

Cheers,
Sky

On Tue, Mar 29, 2016 at 12:20 PM, <esip-preserve-request at lists.esipfed.org>
wrote:

> Send Esip-preserve mailing list submissions to
>         esip-preserve at lists.esipfed.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.deltaforce.net/mailman/listinfo/esip-preserve
> or, via email, send a message with subject or body 'help' to
>         esip-preserve-request at lists.esipfed.org
>
> You can reach the person managing the list at
>         esip-preserve-owner at lists.esipfed.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Esip-preserve digest..."
>
>
> Today's Topics:
>
>    1. Fwd: Software linking? (Parsons, Mark)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 29 Mar 2016 18:05:03 +0000
> From: "Parsons, Mark" <parsom3 at rpi.edu>
> To: ESIP Preserve List <esip-preserve at lists.esipfed.org>
> Subject: [Esip-preserve] Fwd: Software linking?
> Message-ID: <7600F761-11A2-48C2-AFA0-4BFA2AC2C6BA at rpi.edu>
> Content-Type: text/plain; charset="utf-8"
>
> I was unaware of this Force11 effort on software citation until recently.
> I?m surprised no-one from ESIP (that I recognized) was involved.  I have
> only skimmed it, but it looks like it is modeled after the Joint Data
> Citation Principles (which I?m not sure is wise). Perhaps we should discuss
> this at a future meeting. Perhaps the stewardship cluster would like to
> comment on the document.
>
> cheers,
>
> -m.
>
> Begin forwarded message:
>
> From: "Daniel S. Katz" <d.katz at ieee.org<mailto:d.katz at ieee.org>>
> Subject: Re: Software linking?
> Date: 29March2016 at 7:18:53 AM MDT
> To: Tobias Weigel <weigel at dkrz.de<mailto:weigel at dkrz.de>>, Adrian Burton <
> adrian.burton at ands.org.au<mailto:adrian.burton at ands.org.au>>
> Cc: "Parsons, Mark" <parsom3 at rpi.edu<mailto:parsom3 at rpi.edu>>, "Dewaard,
> Anita (ELS-HBE)" <A.dewaard at elsevier.com<mailto:A.dewaard at elsevier.com>>,
> "Hylke (ELS-AMS) Koers" <H.Koers at elsevier.com<mailto:H.Koers at elsevier.com>>,
> "Berman, Fran" <BERMAF at rpi.edu<mailto:BERMAF at rpi.edu>>, Eefke Smit <
> eefke.smit at xs4all.nl<mailto:eefke.smit at xs4all.nl>>, Michael Diepenbroek <
> mdiepenbroek at pangaea.de<mailto:mdiepenbroek at pangaea.de>>, Arfon Smith <
> arfon at github.com<mailto:arfon at github.com>>, Kyle Niemeyer <
> Kyle.Niemeyer at oregonstate.edu<mailto:Kyle.Niemeyer at oregonstate.edu>>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.deltaforce.net/pipermail/esip-preserve/attachments/20160329/034ebdf3/attachment.html
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: software-citation-principles.pdf
> Type: application/pdf
> Size: 266299 bytes
> Desc: software-citation-principles.pdf
> URL: <
> http://lists.deltaforce.net/pipermail/esip-preserve/attachments/20160329/034ebdf3/attachment.pdf
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Esip-preserve mailing list
> Esip-preserve at lists.esipfed.org
> http://lists.deltaforce.net/mailman/listinfo/esip-preserve
>
>
> ------------------------------
>
> End of Esip-preserve Digest, Vol 86, Issue 14
> *********************************************
>

-- 

<.(((<<<~~~~<.(((<<<~~~~<.(((<<<
     Sky Bristol
     USGS Core Science Systems
     sbristol at usgs.gov
     Mobile: 303-578-2127
<.(((<<<~~~~<.(((<<<~~~~<.(((<<<
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-preserve/attachments/20160329/2ea62bd3/attachment-0001.html>