By Mario Antonioletti, Daina Bouquin, Daniel S. Katz, Lucia Michielin, Colin Sauze, and Lucy Whalley. This post is part of the CW19 speed blog posts series. In this blog post, we address the idea of training in software sustainability in the form of questions and answers.
By Patrick McCann, Rachel Ainsworth, Jason M. Gates, Jakob S. Jørgensen, Diego Alonso-Álvarez, and Cerys Lewis. This post is part of the CW19 speed blog posts series. What are the challenges? For many researchers, the development of software is a means to an end—a chore that is necessary to allow them to get on with the real work of conducting research and publishing papers. They may not see themselves as programmers or recognise the code that they write as being software. Their supervisors or senior colleagues may not see the value of devoting perceived extra effort to following good…
By Emily Bell, Radu Gheorghiu, Patricia Herterich, Daniel Hobley, and Sarah Stewart, British Library This post is part of the CW19 speed blog posts series. All attendees of the Software Sustainability Institute Collaboration Workshop 2019 are users or developers of research software, but may not recognise that the production and use of research software demands effective curation and attention to the metadata. We spent a breakout session thinking about where the community is in terms of effective curation of software and its metadata, what the problems still are, and where we can see…
By Adam Jackson, Dav Clarke, Becky Arnold, Ben Krikler, Joanna Leng. This post is part of the CW19 speed blog posts series. At the Software Sustainability Institute’s 2019 Collaborations Workshop, many discussions for the speed-blogging session focused on deposit of relatively fixed data and analysis code.
By Niall Beard, Chris Greenshields, Sam Mangham, Louise Bowler, Mike Allaway, and Jess Ward. This blog post covers some of the important topics to consider when constructing training material. A definition given for the aim of training: “The Confidence to perform a task, repeatedly, to a defined standard in a timely manner.” -- Robin Hoyle, LearnWorks
Did you miss Collaborations Workshop 2019 earlier this year? Would you like to hear one of the talks again? All talks at the event were recorded and these are now available on our YouTube channel.
By Stephan Druskat, Tyler Whitehouse, Alessandro Felder, Sorrel Harriet, Benjamin Lee This post is part of the CW19 speed blog posts series. Good documentation is a fundamental aspect of research software. It influences how easy-to-use, extendable, and by extension how sustainable, a piece of software is. In this blog post, we are interested in addressing issues surrounding good documentation of research software and how they can be approached in a general sense, that may be applicable to a wide research software engineering audience.
By Sarah Gibson, Anna Krystalli, Arshad Emmambux, Alexandra Simperler, Tom Russell, and Doug Lowe Like history, reproducible data processing is just one, um, thing after another. When the number of tools, models or steps in a process grows beyond a handful, we start to feel the need for some automation or structure. Running the same sequence of tools over multiple data? Capturing the steps of an analysis for collaborators or students to repeat, modify and extend? Conducting a scenario analysis using coupled models? Workflow, pipeline and model coupling tools all respond to the need for…
By Raniere Silva, Software Sustainability Institute, and Selina Aragon, Software Sustainability Institute. Photo by Kushagra Kevat. Inspired by the videos created by Sustain during their 2018 Summit, we asked some of the Collaborations Workshop 2019 attendees to share their thoughts about research software sustainability. Each video contains a question relating to software in research, and each interviewee shared their views with us.
Subscribe to CW19
By Emmy Tsang, eLife. Here’s a brutally honest account of what didn’t happen at the Software Sustainability Institute's Collaborations Workshop – and my first un-conference ever – last week.