Hi - I'm Dan Katz. I do a bunch of things related to research software, including co-leading URSSI (http://urssi.us) which is trying to build up a US institute around research software, the US-RSE organization (https://us-rse.org), ReSA (https://www.researchsoft.org), and a FORCE11 group working on software citation (https://www.force11.org/group/software-citation-implementation-working-group). I also work on some research projects that develop and maintain software, such as Parsl (http://parsl-project.org) and funcX (https://funcx.org). Since I wasn't involved in the initial paper for FAIR 4 research software, I have always wanted to try roughly the same process to see if I would come up with roughly the same results, and I though it would more interesting to do this as part of a group
Hi everyone, I'm Vanessa, I'm a research software engineer that (historically) has done work in neuroinformatics, a lot with containers and open source communities, and then general tools for researchers at Stanford and the school of medicine. In context of this community I've developed a lot of the tooling/automation for USRSE and am also actively involved in it. I created and run the Research Software engineering stories podcast (https://us-rse.org/rse-stories), and the rseng community on GitHub (https://github.com/rseng/) that hosts the phenotype generator and some other fun, community open source software. I'm particularity interested in more community-driven approaches to definition for RSEs and research software, and specially have started the Research Software Encyclopedia (database, software, and tooling) https://rseng.github.io/2020/rse/ and the weekly software survey https://rseng.github.io/rseng/blog/. I like building things, and I like making them pretty. That about sums me up :)
Hi All! Mark Wilkinson, Universidad Politecnica de Madrid, Spain. I'm a biological informatician with two main research lines: FAIR/Web interoperability/related topics, and Artificial Intelligence applied to metagenomics and microbiome engineering. I'm interested in this group because FAIR for software is an under-developed area I would like to see improved. I have no expertise in research software (from the perspective of archival, at least! I write software every day, of course!), so I am mostly here to listen. I am writing FAIR "Maturity Indicators" that can be automatically applied to various kinds of digital objects, so I would like to know what this community thinks FAIR for RS should be, in order to design tests for these kinds of resources. Also, I'd just like to become a better netizen, so learning what I should do v.v. software publishing would help me improve! :-)
Hi subgroup1, my name is Morane Gruenpeter I'm a software engineer and metadata specialist at the Inria research center in France working on the Software Heritage archive (which goal is to collect, preserve and share all software source code) https://archive.softwareheritage.org.
I'm interested in FAIR4RS because one of my roles on the Software Heritage team is archiving research software through a deposit mechanism that we have with HAL the national open access repository and the IPOL Journal (Image Processing On Line). With the deposit we receive software artifacts and metadata for which we return a Software Heritage ID (SWHID). I am also representing the Inria research center and software in general on the FAIRsFAIR initiative.
I'm interested in FAIR4RS because one of my roles on the Software Heritage team is archiving research software through a deposit mechanism that we have with HAL the national open access repository and the IPOL Journal (Image Processing On Line). With the deposit we receive software artifacts and metadata for which we return a Software Heritage ID (SWHID). I am also representing the Inria research center and software in general on the FAIRsFAIR initiative.
Hello, I'm Catherine Jones and I lead the Energy Data Centre located at the Science & Technology Facilities Council in the UK. I have been involved with open access to publications, data and more recently research software for the last twenty years. I've been a member of the UK RSE Group Leaders network since 2015 and am currently on the ReSA steering group with Dan. FAIR as a concept in Research data has really taken off, but different content/object/material types (to use library jargon) don't always have the same requirements to achieve the same aim, and I'm interested to understand and contribute to what the aims of FAIR is in a research software context. I am both a chartered librarian and an ex-database programmer/analyst so I am obsessed with order and definitions, so that's why I have volunteered to join this group. :-)
Hi everyone, I'm Paula Andrea Martinez, for a few years i developed software for genomics / bioinformatics. I am now working with neuroscientists to level up and use HPC and GPUs. My current institution is The University of Queensland and I work for the National Imaging Facility in Australia. I'm one of the co-chairs of FAIR4RS, I am interested to learn from the community and help putting together a new set of guiding principles for research software. I'm really glad to meet you all.
Hi everyone. I'm a software skills specialist at the Australian Research Data Commons and my main interest is in getting more researchers and research support professionals thinking computationally and treating software as a research output. I'm here because I'm mostly interested in ways to unpack and express the FAIR principles in a way that can be understood by as many people as possible.
Hi all! I'm Sarah Stevens (she/her/hers), a facilitator at the Data Science Hub at the University of Wisconsin-Madison. Most of what I did for my grad thesis would probably be considered research software engineering and now I help others with the computational/data science needs so I'm very interested about how the FAIR principles can be applied to research software.
For those who haven't, please do go ahead into the google doc and put in a few comments on why you decided to vote the way you did on the 20 questions (https://docs.google.com/document/d/1vexHkz39aCNt9X5iFqe_ENesS844KmBYpkVgnq1IMJE/edit#heading=h.hwvk7ularcki) - lots of questions have no discussion starters yet
Hi All, I'm Tom Honeyman, I have been working for the Australian Research Data Commons (ARDC) for the last couple of years, and have just started in the role of "Software Program Manager" at the ARDC. The ultimate aim for this position is to push for Research Software as a first class research output in an Australian context through a program of work that I'm setting up. In this role I'll be drafting an agenda for research software for the ARDC, helping to set up a local chapter of the SSI (...AuSSI, hopefully), and otherwise trying to align with international efforts in this space. A fresh start is exactly where I'd like to start with this. Looking forward to working with you all.
I've just been through the document - thanks for putting your thoughts in already @vsoch, @cm-j0nes, and @danielskatz. I'm getting a good idea of your frustrations/concerns with the FAIR principles as they stand.
I would love to hear more from people who think that the foundational principles (Findable, Accessible, Interoperable, Reusable) do not apply to software as written.
At least @vsoch and I have been trying to avoid putting in more text at this point so that our thinking does not dominate the coversation I hope we will have. But this will only work if other people help start it. Thanks to @mpfl and @cm-j0nes for starting discussion on some new points, and also to @tom-h for adding some comments to existing points.
To others, please add some starting points for the principles where there is not any discussion so far.
@markwilkinson - @tom-h points out that R1 in https://www.go-fair.org/fair-principles/ (and earlier versions of the principles going back to the FORCE11 webpage) says "R1. Meta(data) are richly described with a plurality of accurate and relevant attributes" - and wonders why this is not (Meta)data - is this intentional or a mistake?
Hi! My name is Maggie Hellström, and I work at the ICOS Carbon Portal (the data center & repository of a European research infrastructure called Integrated Carbon Observation System) as a research data manager. My main RDM interests are Open Science & how to achieve FAIR data (and other research resources!). My interest in FAIR4RS was triggered by two things: 1) I'm coordinating an RDA Sweden mini-project looking at researcher attitudes towards Open Software in Sweden and the Nordic countries, and the topics covered by the 4 Task Forces are very much aligned with the issues that we're trying to cover; and 2) my organisation ICOS has made a firm commitment to use Open Software, and we run our own GitHub repo. However, we're not very good at using persistent identifiers for our code, which is causing problems both for capturing provenance metadata for our data objects, and for documenting and curation of our Jupyter Hub-based data analysis environments. So I want to learn more about what others are doing about this!
FYI, we now know that meta(data) in R1 should be (meta)data - see https://twitter.com/markmoby/status/1295635692517720064?s=20
1 reply
Hello! My name is Marie-Josée Cros and I have been working as a computer engineer specializing in artificial intelligence for many years at INRAE (new National Institute for Research on Agriculture, Food and the Environment , ex INRA). I have just joined the group because I have been interested for several years in the reproducibility of scientific calculations and in general in the quality of software. I've heard a lot about FAIR principles for data but not so much for software and I really appreciate digging into this and being able to share it with other people.
Any comments/edits/suggestions/etc on the draft synthesis doc (https://docs.google.com/document/d/1WsKbZAr5HAVHCCXq5A5Bed3IRafu-CzJtmwJpdrOjSQ/edit) are welcome
Hi all, I added some minor comments and edits to the document. The structure looks good. I saw that there was a discussion over software identification and specifically persistent identification. To answer these interrogations, I invite you to check out the SCID WG output (which is still under community review): https://www.rd-alliance.org/groups/rdaforce11-software-source-code-identification-wg