Re: [rda-tailresearchdata-ig][rda-libresearchdata][software-source-code-ig] [rda-tailresearchdata-ig][rda-libresearchdata][software-source-code-ig] A new(?) aspect of software and the FAIR principles

23 Mar 2020

Dear Dan,
I can accept if it is outside of the scope of the group. But because there was no more appropriate
group, a sent the message to some groups I am member of. If I can find enough people interested,
we might decide to start another group.
Andras
----- Original Message -----
From: "Katz, Daniel S" <***@***.***>
To: "holl andras" <***@***.***>
Cc: "Robin Lindley Ruggaber" <***@***.***>, "Long tail of research data IG" <***@***.***-groups.org>, "Libraries for Research Data IG" <***@***.***-groups.org>, "Software Source Code IG" <***@***.***-groups.org>
Sent: Monday, 23 March, 2020 14:04:27
Subject: Re: [rda-tailresearchdata-ig][rda-libresearchdata][software-source-code-ig] [rda-tailresearchdata-ig][rda-libresearchdata][software-source-code-ig] A new(?) aspect of software and the FAIR principles
Andras,
While I generally agree with what you have stated as goals, I also feel that this is a dramatic expansion of scope, and should be handled outside of the FAIR4Software group.
Changing what software does is very different than changing how software is described.
The more things we add to the group's goals, the less likely it is that we will accomplish them.
Dan
p.s. sending email to lots of groups likely will lead to a broken discussion, since each reply will only go to the groups where the sender is allowed to send, which in my case is just one of the three. It is likely better to wait until there is a group and a mailing list for this group to discuss the scope of the group.
On Mar 23, 2020, at 7:50 AM, andrasholl via Software Source Code IG <***@***.***-groups.org> wrote:
Dear Robin, Rolf,
Thank you for Your suggestions. I agree with both of You.
My hope is that there would be enough people interested in my suggestion, to
draft some initial document on the question. All comments, suggestions, additions - like yours - are wellcome!
With kind regards,
Andras
----- Original Message -----
From: "Robin Lindley Ruggaber" <***@***.***>
To: "holl andras" <***@***.***>
Cc: "Long tail of research data IG" <***@***.***-groups.org>, "Libraries for Research Data IG" <***@***.***-groups.org>, "Software Source Code IG" <***@***.***-groups.org>
Sent: Monday, 23 March, 2020 13:38:51
Subject: Re: [rda-tailresearchdata-ig][rda-libresearchdata][software-source-code-ig] A new(?) aspect of software and the FAIR principles
Andras,
I agree that software ingesting, processing, producing, and archiving should adhere to FAIR principles. What seems questionable is the use of “especially open source” in 2 & 4. Commercial software, especially that software not orginiating from informed by communities committed to preservation and open content, is just as likely to not meet FAIR principles. There was a time when we would not buy software unless we had access to the source code. That vulnerability persists in my opinion especially software dealing with data.
Regards,
Robin
Robin Ruggaber
Director for Strategic Technology Initiatives & Partnerships
University of Virginia Library
On Mar 23, 2020, at 5:30 AM, andrasholl via Long tail of research data IG <***@***.***-groups.org> wrote:
Dear Colleagues,
I would like to share some thoughts on FAIR principles and software. I do not know how or whether it fits
the scope of this interest group.
Andras Holl
I think there is an other, maybe neglected aspect of the relation of FAIR principles and software.
Software should not only be FAIR itself, but should support FAIR-ness: let us call it FAIR-supporting or FAIR-friendly.
Ensuring that research data is FAIR could be a tedious job, and this is a major problem for Open Science. Ensuring FAIR-ness should be, as much as possible, off-loaded from the shoulder of the researcher. The instrumentation used in the creation of observational or experimental data (the software in the instrument) or the software that produces the modelling data should take care - to the possible extent - of creating FAIR output. The software used for data processing should support FAIR data objects. The free software used for repositories (like DSpace and EPrints) should support the FAIR principles, and help the arciving and dissemination.
1.) Creation of the data. Software used for the creation of the data should i.) output data in standard, FAIR compliant formats; ii.) should take care of capturing and logging metadata into the FAIR data object it outputs.
2.) Processing of the data. Software used for data processing – especially open source software – should i.) be able to input FAIR data objects; ii.) output FAIR data objects; iii.) and log metadata on the processing steps into the FAIR data objects it produces.
3.) Visualizing data. Software used for data visualization should produce output that is FAIR, and could be re-used, and should be able to input fair data objects, and use captured metadata in the visual output.
4.) Archiving and distributing data. Software used for repositories – especially open source software – should support FAIR-ness: i.) support FAIR data objects, ii.) support workflows ensuring FAIR-ness.
Such FAIR-supporting or FAIR-friendly behaviour of software should be certified, so researchers and research support organisations could rely on using software that is FAIR-supporting.
Astronomy provides an example how such (though at that time FAIR principles were not laid out yet) properties
of software could promote openness in science.
--
Full post: https://www.rd-alliance.org/group/long-tail-research-data-ig-libraries-r...
Manage my subscriptions: https://www.rd-alliance.org/mailinglist
Stop emails for this post: https://www.rd-alliance.org/mailinglist/unsubscribe/68715
--
Holl András
informatikai főigazgató-helyettes / deputy director (IT)
MTA Könyvtár és Információs Központ / MTA Library and Information Centre
--
Full post:
https://www.rd-alliance.org/group/long-tail-research-data-ig-libraries-r...
Manage my subscriptions: https://www.rd-alliance.org/mailinglist
Stop emails for this post:
https://www.rd-alliance.org/mailinglist/unsubscribe/68723
--
Daniel S. Katz
Assistant Director for Scientific Software and Applications, NCSA
Research Associate Professor, CS
Research Associate Professor, ECE
Research Associate Professor, iSchool
University of Illinois
(217) 244-8000
***@***.*** or ***@***.***
http://danielskatz.org
--
Holl András
informatikai főigazgató-helyettes / deputy director (IT)
MTA Könyvtár és Információs Központ / MTA Library and Information Centre