Software Source Code Identification WG

WG

Group details

Secretariat Liaison: 
Stefanie Kethers
TAB Liaison: 
Andrew Treloar
WGs Producing deliverables (~6-12 months after RDA endorsement)
 

Software, and in particular source code, plays an important role in science: it is used in all research fields to produce, transform and analyse research data, and is sometimes itself an object of research and/or an output of research.

Unlike research data and scientific articles, though, software source code has only very recently been recognised as important subject matter in a few initiatives related to scholarly publication and archiving. These initiatives are now working on a variety of plans for handling the identification of software artifacts.

At the same time, unlike research data and scientific articles, the overwhelming majority of software source code is developed and used outside the academic world, in industry and in developer communities where software is routinely referenced, in practice, through methods that are totally different from the ones used in scholarly publications. 
The objective of this working group is to bring together a broad panel of stakeholders directly involved in software identification.

The planned output will be concrete recommendations for the academic community to ensure that the solutions that will be adopted by the academic players are compatible with each other and especially with the software development practice of tens of millions of developers worldwide.


AttachmentSize
PDF icon RDA SCID WG-CaseStatement.pdf125.58 KB

Recent Activity

14 Oct 2019

[softwarecitation][SCID][software-source-code-ig] FORCE2019's Research Software Hackathon is tomorrow

Hello everyone,

I know that many of you can't join us tomorrow at the Research Software Hackathon.

If you want to see what is happening, you can follow the work on the FORCE11 SCID WG github repository [1] or on our hackathon gitter room [2].

Unfortunately it is complicated to put in place remote access to the different activities.

Feel free to chat on gitter[2], open issues [3] and questions on the repository [1] or comment the working google docs (access to the google docs is possible from the Hackathon README).

13 Sep 2019

RE: [software-source-code-ig][scid] [scid] Re: [software-source-code-ig][scid] [scid] Software...

I’d be very interested in hearing about this at RDA as well.
-Limor
Limor Peer, PhD
Associate Director for Research | Institution for Social and Policy Studies | Yale University
203-432-0054 | ***@***.*** | isps.yale.edu | @l_peer
- Show quoted text -From: ***@***.***-groups.org <***@***.***-groups.org>
Sent: Friday, September 13, 2019 8:46 AM

13 Sep 2019

Re: [software-source-code-ig][scid] [scid] Software Source Code activities this fall (Was: Re: ...

On 9/13/19 9:44 AM, andrew treloar via Software Source Code
Hi,
I won't be able to attend the Hackaton too but will be in Helsinki. So,
since I'm a newcomer, I'd be glad to meet members of the WG/IG there.
Cheers
--
Tovo J. Rabemanantsoa
IT Manager
Quality correspondent
INRA - UMR ISPA [Interactions Sol Plante Atmosphère]
Villenave d'Ornon - Gironde, France
+33 5 57 12 24 09

13 Sep 2019

Software Source Code activities this fall (Was: Re: [software-source-code-ig] Plenary 14)

Hi Tovo, all,
as Julia said, it was not clear that one of the group chairs would be able to
attend P14, so we did not submit a proposal for the IG meeting.
For the SCID working group, which is a joint effort with FORCE11, after the
Philadelphia kickoff at P13 this time the meeting will be at FORCE2019 in
Edimbourgh, where we organize a full day hackaton, see:
https://force2019.sched.com/event/U2pI/research-software-hackathon

06 Sep 2019

Guidelines for archiving and referencing (research) software in Software Heritage

Dear all,
one of the core goals of Software Heritage
is to support reproducible research, and
to this end it provides two essential and unique functionalities:
- a *universal archive* of software source code, because research
software depends on a myriad software components, that need all be archived
and referenced
- a *uniform identifier schema* that abstracts away the details of
source code provenance and version control, based on *intrinsic
identifiers* that are *compatible with git commit hashes *

05 Sep 2019

[softwarecitation][SCID][software-source-code-ig] Hackathon on October 15th FORCE19

Dear all,
We are happy to announce that a full day hackathon about Research Software
has been accepted to the Force2019 [1] conference and it will be held on
Oct. 15th 2019 in Edinburgh [2] .
The main theme will be about “Making software a first-class citizen in the
scholarly world” [3] and we hope bringing together a large group of
stakeholders who are actively working to improve the status of research
software in the scholarly environment.
This is a great opportunity for FORCE11 Software Citation Implementation WG

11 Jun 2019

Attributing and Referencing Research Software: Best Practices and Outlook from Inria

Dear all,
I'm delighted to share with you the following article containing the first
results of a working group that has been studying the complex issues one has to
face when taking into account software as a first class research output:
"Attributing and Referencing Research Software:
Best Practices and Outlook from Inria"
available from https://hal.archives-ouvertes.fr/hal-02135891v1
This article, currently submitted to a journal, is a contribution to the ongoing