Search

Current biodiversity models often struggle to represent the complexity of global crises, as the affected ecosystems are shaped by many different ecological, physical, and social processes. To understand these dynamics better, we will need to build larger and more complex ecological models, and couple ecological models to models produced by other disciplines, such as climate science, economics, or sociology. However, constructing such integrated models is a significant technical undertaking, which has received little attention by ecological modellers so far. We review literature from computer science and several other environmental modelling disciplines to identify common challenges and possible strategies when creating large integrated models. We show that there is a software-architectural trade-off between modularity and integration, where the former is required to keep the technical complexity of a model manageable, and the latter is desirable to represent the scientific complexity of a studied system. We then present and compare five different software engineering techniques for navigating this trade-off. Which technique is most suitable for a given model depends on the model’s aims and the available development resources. The larger a model becomes, the more important it is to use more advanced techniques, such as integrating models from different domains using a model coupling framework. Our review shows that ecological modellers can learn from other modelling disciplines, but also need to invest in increased software engineering expertise, if they want to build models that can represent the numerous processes affecting ecosystems and biodiversity loss.

This paper introduces Tilbot, an open source, easy to use platform for the design of conversational user interfaces. Although many platforms for the creation of conversational agents already exist, they often are closed source and focus mainly on commercial purposes. Tilbot is created as an open source solution that can be hosted on-premises. By focusing primarily on students and researchers, Tilbot stimulates open science research, collaborations, and building a scientific community to create and share best practices and experiences. At the CUI conference, visitors will be able to try out Tilbot, and engage with its original creators to highlight their wishes and brainstorm directions for future development.

The deliverable defines 17 metrics that can be used to automate the assessment of research software against the FAIR4RS Principles, and provides examples of how these might be implemented in one exemplar disciplinary context of the social sciences. The FAIR-IMPACT project will then work to implement the metrics as practical tests by extending existing assessment tools such as F-UJI; this work will be reported in Q2 2024. Feedback will be sought from the community, through webinars and an open request for comments. The information from all these sources will be used to publish a revised version of the metrics.

Software is increasingly acknowledged as valid research output. Academic libraries adapt to this change to become research software-ready. Software publication and citation are key areas in this endeavor. We present and discuss the current state of the practice of software publication and software citation, and discuss four areas of activity that libraries engage in: (1) technical infrastructure, (2) training and support, (3) software management and curation, (4) policies., Software wird zunehmend als gültiges Forschungsergebnis anerkannt. Wissenschaftliche Bibliotheken passen sich diesem Wandel an, um für Forschungssoftware gerüstet zu sein. Softwarepublikation und -zitierung sind hierbei Schlüsselbereiche. Wir präsentieren und diskutieren hier den aktuellen Praxisstand und heben vier Bereiche hervor, in denen Bibliotheken aktiv werden können, um für Forschungssoftware gerüstet zu sein: (1) technische Infrastruktur, (2) Schulung und Support, (3) Management und Kuratierung von Software, (4) Richtlinien., Peer Reviewed

Finding research software is a complex task, as research software engineers regularly search for algorithms and methods deeply embedded in large software packages during the creation of research software. Furthermore, they go through lengthy evaluation and extraction processes to find one particular algorithm relevant to their research project. Additionally, for creators of research software, it is hard to show the impact that their code has made on the field, and only very course measures exist for evaluating the success of research software. This study introduces the concept of FAIRSECO, which aims to enable research software engineers to rapidly find and extract relevant software fragments from the worldwide research software ecosystem. Research software engineers from all fields can transplant these source code fragments, maintain the provenance of source code, and easily credit the original authors of the software. Simultaneously, the platform also enables research software engineers to report on their software's impact. With FAIRSECO, we introduce a platform for research software engineers that creates a “method economy”, i.e., where smaller granularity reuse becomes possible while increasing FAIRness (Findable, Accessible, Interoperable, and Reusable) of the worldwide research software ecosystem.

Publishing your research software in a publication repository is the first step on the path to making your (research) software FAIR! But the publication of the software itself is not quite enough: To truly enable findability, accessibility and reproducibility, as well as making your software correctly citable and unlock credit for your work, your software publication must come with rich metadata to support these goals.

We introduce the concept of Canonical Workflow Building Blocks (CWBB), a methodology of describing and wrapping computational tools, in order for them to be utilised in a reproducible manner from multiple workflow languages and execution platforms. The concept is implemented and demonstrated with the BioExcel Building Blocks library (BioBB), a collection of tool wrappers in the field of computational biomolecular simulation. Interoperability across different workflow languages is showcased through a protein Molecular Dynamics setup transversal workflow, built using this library and run with 5 different Workflow Manager Systems (WfMS). We argue such practice is a necessary requirement for FAIR Computational Workflows and an element of Canonical Workflow Frameworks for Research (CWFR) in order to improve widespread adoption and reuse of computational methods across workflow language barriers., This work has been done as part of the BioExcel CoE (https://www.bioexcel.eu/), a project funded by the European Union contracts H2020-INFRAEDI-02-2018 823830, and H2020-EINFRA-2015-1 675728. Additional work is funded through EOSC-Life (https://www.eosc-life.eu/) contract H2020-INFRAEOSC-2018-2 824087, and ELIXIR-CONVERGE (https://elixir-europe.org/) contract H2020-INFRADEV-2019-2 871075. The authors would also like to acknowledge contributions from Cibin Sadasivan Baby, Finn Bacall, Rosa M. Badia, Sarah Butcher, Gerard Capes, Michael R. Crusoe, Alberto Eusebi, Carole Goble, Josep Lluís Gelpí, Modesto Orozco, Geoff Williams, and Felix Amaladoss., Peer Reviewed, Postprint (author's final draft)

The goal of this project is to support researchers in publishing their research software, in a way that makes it findable, comprehensible, citable and reusable. The key to this is the creation, curation and deposit of rich metadata with software publications. To this end, the project will conceptualize, produce and provide well-documented, adoption-ready workflows with automation interfaces and reference implementations for InvenioRDM and Dataverse.

Publishing your research software in a publication repository is the first step on the path to making your (research) software FAIR! But the publication of the software itself is not quite enough: To truly enable findability, accessibility and reproducibility, as well as making your software correctly citable and unlock credit for your work, your software publication must come with rich metadata to support these goals.

The goal of this project is to support researchers in publishing their research software, in a way that makes it findable, comprehensible, citable and reusable. The key to this is the creation, curation and deposit of rich metadata with software publications. To this end, the project will conceptualize, produce and provide well-documented, adoption-ready workflows with automation interfaces and reference implementations for InvenioRDM and Dataverse.

The presentation highlights the research data repository of the HZDR RODARE. In the first part Maik Fiedler gives an overview of the current use of the repository, shows features and statistics on the development and embeds the system in the publication economy of the HZDR. In the second part the update upgrade from Rodare to an InvenioRDM-based RODARE-RDM is introduced with the technical background and conditions by Oliver Knodel. Furthermore, the concept for the integration of Rodare into the HELIPORT data management system HELIPORT is presented.

Almost all scientific research relies on software. This is particularly true for research that uses neuroimaging technologies, such as functional magnetic resonance imaging (fMRI). These technologies generate massive amounts of data per participant, which must be processed and analyzed using specialized software. A large portion of these tools are developed by teams of researchers, rather than trained software developers. In this kind of ecosystem, where the majority of software creators are scientists, rather than trained programmers, it becomes more important than ever to rely on community-based development, which may explain why most of this software is open source. It is in the development of this kind of research-oriented, open source software that I have focused much of my graduate training, as is reflected in this dissertation. One software package I have helped to develop and maintain is tedana, a Python library for denoising multi-echo fMRI data. In chapter 2, I describe this library in a short, published software paper. Another library I maintain as the primary developer is NiMARE, a Python library for performing neuroimaging meta-analyses and derivative analyses, such as automated annotation and functional decoding. In chapter 3, I present NiMARE in a hybrid software paper with embedded tutorial code exhibiting the functionality of the library. This paper is currently hosted as a Jupyter book that combines narrative content and code snippets that can be executed online. In addition to research software development, I have focused my graduate work on performing reproducible, open fMRI research. To that end, chapter 4 is a repli- cation and extension of a recent paper on multi-echo fMRI denoising methods Power et al. (2018a). This replication was organized as a registered report, in which the introduction and methods were submitted for peer review before the analyses were performed. Finally, chapter 5 is a conclusion to the dissertation, in which I reflect

Computational tools are increasingly becoming constitutive parts of scientific research, from experimentation and data collection to the dissemination and storage of results. Unfortunately, however, research software is not subjected to the same requirements as other methods of scientific research: being peer-reviewed, being reproducible and allowing one to build upon another’s work. This situation is detrimental to the integrity and advancement of scientific research, leading to computational methods frequently being impossible to reproduce and/or verify [1]. Moreover, they are often opaque, direcly unavailable or impossible to use by others [2]. One step to address this problem could be formulating a set of principles that research software should meet to ensure its quality and sustainability, resembling the FAIR (Findable, Accessible, Interoperable and Reusable) Data Principles [3]. The FAIR Data Principles were created to solve similar issues affecting scholarly data, namely great difficulty of sharing and accessibility, and are currently widely recognized accross fileds. We present here FAIRsoft, our initial effort to assess the quality of research software using a FAIR-like framework, as a first step towards its implementation in OpenEBench [4], the ELIXIR benchmarking platform.

Course that reviews and exercises good practices on Software Quality Assurance (SQA) within research environments.

Publishing your research software in a publication repository is the first step on the path to making your (research) software FAIR! But the publication of the software itself is not quite enough: To truly enable findability, accessibility and reproducibility, as well as making your software correctly citable and unlock credit for your work, your software publication must come with rich metadata to support these goals.

Research software has become a central asset in academic research. It optimizes existing and enables new research methods, implements and embeds research knowledge, and constitutes an essential research product in itself. Research software must be sustainable in order to understand, replicate, reproduce, and build upon existing research or conduct new research effectively. In other words, software must be available, discoverable, usable, and adaptable to new needs, both now and in the future. Research software therefore requires an environment that supports sustainability. Hence, a change is needed in the way research software development and maintenance are currently motivated, incentivized, funded, structurally and infrastructurally supported, and legally treated. Failing to do so will threaten the quality and validity of research. In this paper, we identify challenges for research software sustainability in Germany and beyond, in terms of motivation, selection, research software engineering personnel, funding, infrastructure, and legal aspects. Besides researchers, we specifically address political and academic decision-makers to increase awareness of the importance and needs of sustainable research software practices. In particular, we recommend strategies and measures to create an environment for sustainable research software, with the ultimate goal to ensure that software-driven research is valid, reproducible and sustainable, and that software is recognized as a first class citizen in research. This paper is the outcome of two workshops run in Germany in 2019, at deRSE19 - the first International Conference of Research Software Engineers in Germany - and a dedicated DFG-supported follow-up workshop in Berlin.

The goal of this project is to support researchers in publishing their research software, in a way that makes it findable, comprehensible, citable and reusable. The key to this is the creation, curation and deposit of rich metadata with software publications. To this end, the project will conceptualize, produce and provide well-documented, adoption-ready workflows with automation interfaces and reference implementations for InvenioRDM and Dataverse.

The goal of this project is to support researchers in publishing their research software, in a way that makes it findable, comprehensible, citable and reusable. The key to this is the creation, curation and deposit of rich metadata with software publications. To this end, the project will conceptualize, produce and provide well-documented, adoption-ready workflows with automation interfaces and reference implementations for InvenioRDM and Dataverse.

Mit der voranschreitenden Digitalisierung von Forschung und Lehre steigt die Zahl an Software-Lösungen, die an wissenschaftlichen Einrichtungen entstehen und zur Erkenntnisgewinnung genutzt werden. Die – unter dem Stichwort Open Science geforderte – Zugänglichkeit und Nachnutzung von wissenschaftlichen Ergebnissen kann in vielen Fachgebieten nur sichergestellt werden, wenn neben Forschungsdaten auch Programmcode offen zugänglich gemacht wird. Die vorliegende Handreichung richtet sich an Entscheider*innen in den Helmholtz-Zentren, die sich mit der Implementierung von Richtlinien für nachhaltige Forschungssoftware befassen. Sie ergänzt eine Muster-Richtlinie, die den Zentren bereits eine richtungsweisende und nachnutzbare Vorlage zur Erstellung von Regelungen für einen nachhaltigen Umgang mit Forschungssoftware gibt.

Aufgrund des informationstechnologischen Fortschritts, der immer stärkeren, domänenübergreifenden Vernetzung in Wissenschaft und Forschung sowie der Notwendigkeit, gemeinsam Dienste und Ressourcen zu nutzen, werden von den Akteuren in Forschung und Wissenschaft zunehmend verteilte digitale Dienste verwendet. Der Fokus dieser Handreichung liegt auf den wissenschaftlichen Informationsdiensten, zu denen man u. a. Werkzeuge für kollaboratives Arbeiten, für die Aufbereitung und Analyse von Daten sowie Dienste zum wissenschaftlichen Publizieren, aber auch Dienste für die Entwicklung von Forschungssoftware zählen kann. Dabei zielen die Fragen nach der Art der geforderten bzw. wirklich verwendeten Diensten, der Vor- und Nachteile der gegenwärtigen Nutzung sowie der eigenverantwortlichen Bereitstellung dieser Dienste unter dem Aspekt der (finanziellen) Ressourcen- Effizienz.

Aufgrund des informationstechnologischen Fortschritts, der immer stärkeren, domänenübergreifenden Vernetzung in Wissenschaft und Forschung sowie der Notwendigkeit, gemeinsam Dienste und Ressourcen zu nutzen, werden von den Akteuren in Forschung und Wissenschaft zunehmend verteilte digitale Dienste verwendet. Der Fokus dieser Handreichung liegt auf den wissenschaftlichen Informationsdiensten, zu denen man u. a. Werkzeuge für kollaboratives Arbeiten, für die Aufbereitung und Analyse von Daten sowie Dienste zum wissenschaftlichen Publizieren, aber auch Dienste für die Entwicklung von Forschungssoftware zählen kann. Dabei zielen die Fragen nach der Art der geforderten bzw. wirklich verwendeten Diensten, der Vor- und Nachteile der gegenwärtigen Nutzung sowie der eigenverantwortlichen Bereitstellung dieser Dienste unter dem Aspekt der (finanziellen) Ressourcen- Effizienz.

Mit der voranschreitenden Digitalisierung von Forschung und Lehre steigt die Zahl an Software-Lösungen, die an wissenschaftlichen Einrichtungen entstehen und zur Erkenntnisgewinnung genutzt werden. Die – unter dem Stichwort Open Science geforderte – Zugänglichkeit und Nachnutzung von wissenschaftlichen Ergebnissen kann in vielen Fachgebieten nur sichergestellt werden, wenn neben Forschungsdaten auch Programmcode offen zugänglich gemacht wird. Die vorliegende Handreichung richtet sich an Entscheider*innen in den Helmholtz-Zentren, die sich mit der Implementierung von Richtlinien für nachhaltige Forschungssoftware befassen. Sie ergänzt eine Muster-Richtlinie, die den Zentren bereits eine richtungsweisende und nachnutzbare Vorlage zur Erstellung von Regelungen für einen nachhaltigen Umgang mit Forschungssoftware gibt.

After years of using Graphics Processing Units (GPUs) to accelerate scientific applications in fields as varied as tomography, computer vision, climate modeling, digital forensics, geospatial databases, particle physics, radio astronomy, and localization microscopy, we noticed a number of technical, socio-technical, and non-technical challenges that Research Software Engineers (RSEs) may run into. While some of these challenges, such as managing different programming languages within a project, or having to deal with different memory spaces, are common to all software projects involving GPUs, others are more typical of scientific software projects. Among these challenges we include changing resolutions or scales, maintaining an application over time and making it sustainable, and evaluating both the obtained results and the achieved performance.

Open science means opening up the research cycle completely. The article gives an overview on the single stages and delineates the challenges and issues that are related to the opening up of each stage., "Open Science" bedeutet die komplette Öffnung des Forschungskreislaufs. Der Beitrag stellt überblicksartig die einzelnen Elemente vor und zeigt auf, was jeweils die Herausforderungen bzw. Diskussionspunkte sind, die mit einer Öffnung verbunden sind.

Aufgrund des informationstechnologischen Fortschritts, der immer stärkeren, domänenübergreifenden Vernetzung in Wissenschaft und Forschung sowie der Notwendigkeit, gemeinsam Dienste und Ressourcen zu nutzen, werden von den Akteuren in Forschung und Wissenschaft zunehmend verteilte digitale Dienste verwendet. Der Fokus dieser Handreichung liegt auf den wissenschaftlichen Informationsdiensten, zu denen man u. a. Werkzeuge für kollaboratives Arbeiten, für die Aufbereitung und Analyse von Daten sowie Dienste zum wissenschaftlichen Publizieren, aber auch Dienste für die Entwicklung von Forschungssoftware zählen kann. Dabei zielen die Fragen nach der Art der geforderten bzw. wirklich verwendeten Diensten, der Vor- und Nachteile der gegenwärtigen Nutzung sowie der eigenverantwortlichen Bereitstellung dieser Dienste unter dem Aspekt der (finanziellen) Ressourcen- Effizienz.

Aufgrund des informationstechnologischen Fortschritts, der immer stärkeren, domänenübergreifenden Vernetzung in Wissenschaft und Forschung sowie der Notwendigkeit, gemeinsam Dienste und Ressourcen zu nutzen, werden von den Akteuren in Forschung und Wissenschaft zunehmend verteilte digitale Dienste verwendet. Der Fokus dieser Handreichung liegt auf den wissenschaftlichen Informationsdiensten, zu denen man u. a. Werkzeuge für kollaboratives Arbeiten, für die Aufbereitung und Analyse von Daten sowie Dienste zum wissenschaftlichen Publizieren, aber auch Dienste für die Entwicklung von Forschungssoftware zählen kann. Dabei zielen die Fragen nach der Art der geforderten bzw. wirklich verwendeten Diensten, der Vor- und Nachteile der gegenwärtigen Nutzung sowie der eigenverantwortlichen Bereitstellung dieser Dienste unter dem Aspekt der (finanziellen) Ressourcen- Effizienz.

After years of using Graphics Processing Units (GPUs) to accelerate scientific applications in fields as varied as tomography, computer vision, climate modeling, digital forensics, geospatial databases, particle physics, radio astronomy, and localization microscopy, we noticed a number of technical, socio-technical, and non-technical challenges that Research Software Engineers (RSEs) may run into. While some of these challenges, such as managing different programming languages within a project, or having to deal with different memory spaces, are common to all software projects involving GPUs, others are more typical of scientific software projects. Among these challenges we include changing resolutions or scales, maintaining an application over time and making it sustainable, and evaluating both the obtained results and the achieved performance.

Research software is vital to advancement in the sciences, engineering, humanities, and all other fields. Scientific research is dependent on the quality of and accessibility to research software. Research software is often developed hastily to solve one-off problems, leading to flimsy code that is not sustainable or usable beyond the lifetime of a given research project and is difficult for researchers, outside of the original context, to use, reuse or extend. It is critical to address the many challenges related to the development, deployment, and maintenance of research software. Therefore, there is a growing concern in the scientific community regarding designing sustainable research software. The academic research context refers to the environment or community concerned with scientific research, sponsored by research grants and public funding. Despite the increasing dependence on research software, software development practices in academia lag far behind those in the commercial sector. Health care relies on a very complex information technology architecture with many different IT components and also has a highly complex governance structure alongside the very rapid technology development. Additionally, there are ever-increasing demands and needs from health care users for more flexibility, more functionality and making the care transparent and patient-centred. Taken together, this poses significant challenges for eHealth and Information Systems researchers, as each artefact, depending on the context, has different quality characteristics to operationalise the requirements under consideration. The research objective is to explore what Information Systems researchers and practitioners need to be aware of for sustaining the usefulness of eHealth research software, in the academic research context. This longitudinal action design research (ADR) project, with its three cases, was conducted in an eHealth research project over a period of six years. Contributions fro

Research software is vital to advancement in the sciences, engineering, humanities, and all other fields. Scientific research is dependent on the quality of and accessibility to research software. Research software is often developed hastily to solve one-off problems, leading to flimsy code that is not sustainable or usable beyond the lifetime of a given research project and is difficult for researchers, outside of the original context, to use, reuse or extend. It is critical to address the many challenges related to the development, deployment, and maintenance of research software. Therefore, there is a growing concern in the scientific community regarding designing sustainable research software. The academic research context refers to the environment or community concerned with scientific research, sponsored by research grants and public funding. Despite the increasing dependence on research software, software development practices in academia lag far behind those in the commercial sector. Health care relies on a very complex information technology architecture with many different IT components and also has a highly complex governance structure alongside the very rapid technology development. Additionally, there are ever-increasing demands and needs from health care users for more flexibility, more functionality and making the care transparent and patient-centred. Taken together, this poses significant challenges for eHealth and Information Systems researchers, as each artefact, depending on the context, has different quality characteristics to operationalise the requirements under consideration. The research objective is to explore what Information Systems researchers and practitioners need to be aware of for sustaining the usefulness of eHealth research software, in the academic research context. This longitudinal action design research (ADR) project, with its three cases, was conducted in an eHealth research project over a period of six years. Contributions fro

Research software is vital to advancement in the sciences, engineering, humanities, and all other fields. Scientific research is dependent on the quality of and accessibility to research software. Research software is often developed hastily to solve one-off problems, leading to flimsy code that is not sustainable or usable beyond the lifetime of a given research project and is difficult for researchers, outside of the original context, to use, reuse or extend. It is critical to address the many challenges related to the development, deployment, and maintenance of research software. Therefore, there is a growing concern in the scientific community regarding designing sustainable research software. The academic research context refers to the environment or community concerned with scientific research, sponsored by research grants and public funding. Despite the increasing dependence on research software, software development practices in academia lag far behind those in the commercial sector. Health care relies on a very complex information technology architecture with many different IT components and also has a highly complex governance structure alongside the very rapid technology development. Additionally, there are ever-increasing demands and needs from health care users for more flexibility, more functionality and making the care transparent and patient-centred. Taken together, this poses significant challenges for eHealth and Information Systems researchers, as each artefact, depending on the context, has different quality characteristics to operationalise the requirements under consideration. The research objective is to explore what Information Systems researchers and practitioners need to be aware of for sustaining the usefulness of eHealth research software, in the academic research context. This longitudinal action design research (ADR) project, with its three cases, was conducted in an eHealth research project over a period of six years. Contributions fro

Mit dem Ziel den gesamten Lebenszyklus wissenschaftlicher Artikel, Forschungssoftware und Daten in Vereinbarkeit mit den FAIR-Prinzipien zu unterstützen, wurde am HZDR eine integrierte Entwicklungs- und Publikationsumgebung geschaffen. Insbesondere die Publikation von Forschungssoftware und Daten erfordert eine technische und organisatorische Infrastruktur. Oft ist auch ein intensiverer Wissensaustausch und die Unterstützung der Wissenschaftler notwendig. Die Hürde zur Veröffentlichung sollte durch Automatisierung und Integration verschiedener Plattformen möglichst klein gehalten werden. In diesem Vortrag wird der aktuelle Stand, Erfahrungen und Herausforderungen gezeigt, die bei der Bereitstellung einer derartigen Umgebung gemacht wurden.

Mit dem Ziel, das Publizieren von Artikeln, Forschungsdaten und wissenschaftlicher Software gemäß den FAIR-Prinzipien zu unterstützen, wurde am HZDR ein integriertes Publikationsmanagement aufgebaut. Insbesondere Daten- und Softwarepublikationen erfordern die Entwicklung bedarfsgerechter organisatorischer und technischer Strukturen ergänzend zu bereits sehr gut funktionierenden Services im Publikationsmanagement. In der Zusammenarbeit mit Wissenschaftlern des HZDR und internationalen Partnern in ausgewählten Projekten wurde der Bedarf an Unterstützung im Forschungsdatenmanagement analysiert. Darauf aufbauend wurde schrittweise ein integriertes System von Infrastrukturen und Services entwickelt und bereitgestellt. In einer seit Mai 2018 gültigen Data Policy wurden die Rahmenbedingungen und Regelungen sowohl für wissenschaftliche Mitarbeiter als auch für externe Messgäste definiert. Zusammenfassend werden unsere Erfahrungen im integrierten Publikationsmanagement für Artikel, Forschungsdaten und Forschungssoftware vorgestellt. Es wird ein Ausblick auf die nächsten Schritte und Aufgaben gegeben und Aspekte der Integration im Kontext der europäischen und nationalen Forschungsorganisationen herausgearbeitet.

Mit dem Ziel, das Publizieren von Artikeln, Forschungsdaten und wissenschaftlicher Software gemäß den FAIR-Prinzipien zu unterstützen, wurde am HZDR ein integriertes Publikationsmanagement aufgebaut. Insbesondere Daten- und Softwarepublikationen erfordern die Entwicklung bedarfsgerechter organisatorischer und technischer Strukturen ergänzend zu bereits sehr gut funktionierenden Services im Publikationsmanagement. In der Zusammenarbeit mit Wissenschaftlern des HZDR und internationalen Partnern in ausgewählten Projekten wurde der Bedarf an Unterstützung im Forschungsdatenmanagement analysiert. Darauf aufbauend wurde schrittweise ein integriertes System von Infrastrukturen und Services entwickelt und bereitgestellt. In einer seit Mai 2018 gültigen Data Policy wurden die Rahmenbedingungen und Regelungen sowohl für wissenschaftliche Mitarbeiter als auch für externe Messgäste definiert. Zusammenfassend werden unsere Erfahrungen im integrierten Publikationsmanagement für Artikel, Forschungsdaten und Forschungssoftware vorgestellt. Es wird ein Ausblick auf die nächsten Schritte und Aufgaben gegeben und Aspekte der Integration im Kontext der europäischen und nationalen Forschungsorganisationen herausgearbeitet.

Mit dem Ziel, das Publizieren von Artikeln, Forschungsdaten und wissenschaftlicher Software gemäß den FAIR-Prinzipien zu unterstützen, wurde am HZDR ein integriertes Publikationsmanagement aufgebaut. Insbesondere Daten- und Softwarepublikationen erfordern die Entwicklung bedarfsgerechter organisatorischer und technischer Strukturen ergänzend zu bereits sehr gut funktionierenden Services im Publikationsmanagement. In der Zusammenarbeit mit Wissenschaftlern des HZDR und internationalen Partnern in ausgewählten Projekten wurde der Bedarf an Unterstützung im Forschungsdatenmanagement analysiert. Darauf aufbauend wurde schrittweise ein integriertes System von Infrastrukturen und Services entwickelt und bereitgestellt. In einer seit Mai 2018 gültigen Data Policy wurden die Rahmenbedingungen und Regelungen sowohl für wissenschaftliche Mitarbeiter als auch für externe Messgäste definiert. Zusammenfassend werden unsere Erfahrungen im integrierten Publikationsmanagement für Artikel, Forschungsdaten und Forschungssoftware vorgestellt. Es wird ein Ausblick auf die nächsten Schritte und Aufgaben gegeben und Aspekte der Integration im Kontext der europäischen und nationalen Forschungsorganisationen herausgearbeitet.

Mit dem Ziel, das Publizieren von Artikeln, Forschungsdaten und wissenschaftlicher Software gemäß den FAIR-Prinzipien (https://www.go-fair.org/fair-principles/) zu unterstützen, wurde am HZDR ein integriertes Publikationsmanagement aufgebaut. Insbesondere Daten- und Softwarepublikationen erfordern die Entwicklung bedarfsgerechter organisatorischer und technischer Strukturen ergänzend zu bereits sehr gut funktionierenden Services im Publikationsmanagement. In der Zusammenarbeit mit Wissenschaftlern des HZDR und internationalen Partnern in ausgewählten Projekten wurde der Bedarf an Unterstützung im Forschungsdatenmanagement analysiert. Darauf aufbauend wurde schrittweise ein integriertes System von Infrastrukturen und Services entwickelt und bereitgestellt. In einer seit Mai 2018 gültigen Data Policy wurden die Rahmenbedingungen und Regelungen sowohl für wissenschaftliche Mitarbeiter als auch für externe Messgäste definiert. Im Vortrag wird auf die Erfahrungen im integrierten Publikationsmanagement für Artikel, Forschungsdaten und Forschungssoftware eingegangen und daraus resultierend werden die nächsten Aufgaben und Ziele entwickelt

Mit dem Ziel den gesamten Lebenszyklus wissenschaftlicher Artikel, Forschungssoftware und Daten in Vereinbarkeit mit den FAIR-Prinzipien zu unterstützen, wurde am HZDR eine integrierte Entwicklungs- und Publikationsumgebung geschaffen. Insbesondere die Publikation von Forschungssoftware und Daten erfordert eine technische und organisatorische Infrastruktur. Oft ist auch ein intensiverer Wissensaustausch und die Unterstützung der Wissenschaftler notwendig. Die Hürde zur Veröffentlichung sollte durch Automatisierung und Integration verschiedener Plattformen möglichst klein gehalten werden. In diesem Vortrag wird der aktuelle Stand, Erfahrungen und Herausforderungen gezeigt, die bei der Bereitstellung einer derartigen Umgebung gemacht wurden.

Open-source research software is an important element of open science. While the number of software packages made available by researchers is increasing, there has been little analysis about their subsequent uptake. We collect basic information about prospective users when sharing our open-source sensitivity analysis toolbox. This enabled us to carry out a user survey to assess adoption success – beyond simply counting download numbers. Survey results confirm the key role of extensive documentation to ensure adoption, to enhance learning and to enable research implementation. We found that workflows are an effective tool to guide users to tailor methods to their problems. However, workflows also need to include guidance for interpretation of results, otherwise sophisticated functionalities are overlooked as their value is unclear. Developing effective documentation requires significant time investment but is essential if the ultimate aim of open research software is to promote the adoption of scientific methodologies and best practices.

Research software is vital to advancement in the sciences, engineering, humanities, and all other fields. Scientific research is dependent on the quality of and accessibility to research software. Research software is often developed hastily to solve one-off problems, leading to flimsy code that is not sustainable or usable beyond the lifetime of a given research project and is difficult for researchers, outside of the original context, to use, reuse or extend. It is critical to address the many challenges related to the development, deployment, and maintenance of research software. Therefore, there is a growing concern in the scientific community regarding designing sustainable research software. The academic research context refers to the environment or community concerned with scientific research, sponsored by research grants and public funding. Despite the increasing dependence on research software, software development practices in academia lag far behind those in the commercial sector. Health care relies on a very complex information technology architecture with many different IT components and also has a highly complex governance structure alongside the very rapid technology development. Additionally, there are ever-increasing demands and needs from health care users for more flexibility, more functionality and making the care transparent and patient-centred. Taken together, this poses significant challenges for eHealth and Information Systems researchers, as each artefact, depending on the context, has different quality characteristics to operationalise the requirements under consideration. The research objective is to explore what Information Systems researchers and practitioners need to be aware of for sustaining the usefulness of eHealth research software, in the academic research context. This longitudinal action design research (ADR) project, with its three cases, was conducted in an eHealth research project over a period of six years. Contributions fro

Research software is vital to advancement in the sciences, engineering, humanities, and all other fields. Scientific research is dependent on the quality of and accessibility to research software. Research software is often developed hastily to solve one-off problems, leading to flimsy code that is not sustainable or usable beyond the lifetime of a given research project and is difficult for researchers, outside of the original context, to use, reuse or extend. It is critical to address the many challenges related to the development, deployment, and maintenance of research software. Therefore, there is a growing concern in the scientific community regarding designing sustainable research software. The academic research context refers to the environment or community concerned with scientific research, sponsored by research grants and public funding. Despite the increasing dependence on research software, software development practices in academia lag far behind those in the commercial sector. Health care relies on a very complex information technology architecture with many different IT components and also has a highly complex governance structure alongside the very rapid technology development. Additionally, there are ever-increasing demands and needs from health care users for more flexibility, more functionality and making the care transparent and patient-centred. Taken together, this poses significant challenges for eHealth and Information Systems researchers, as each artefact, depending on the context, has different quality characteristics to operationalise the requirements under consideration. The research objective is to explore what Information Systems researchers and practitioners need to be aware of for sustaining the usefulness of eHealth research software, in the academic research context. This longitudinal action design research (ADR) project, with its three cases, was conducted in an eHealth research project over a period of six years. Contributions fro

Peer Reviewed

This article describes the motivation, design, and progress of the Journal of Open Source Software (JOSS). JOSS is a free and open-access journal that publishes articles describing research software. It has the dual goals of improving the quality of the software submitted and providing a mechanism for research software developers to receive credit. While designed to work within the current merit system of science, JOSS addresses the dearth of rewards for key contributions to science made in the form of software. JOSS publishes articles that encapsulate scholarship contained in the software itself, and its rigorous peer review targets the software components: functionality, documentation, tests, continuous integration, and the license. A JOSS article contains an abstract describing the purpose and functionality of the software, references, and a link to the software archive. The article is the entry point of a JOSS submission, which encompasses the full set of software artifacts. Submission and review proceed in the open, on GitHub. Editors, reviewers, and authors work collaboratively and openly. Unlike other journals, JOSS does not reject articles requiring major revision; while not yet accepted, articles remain visible and under review until the authors make adequate changes (or withdraw, if unable to meet requirements). Once an article is accepted, JOSS gives it a digital object identifier (DOI), deposits its metadata in Crossref, and the article can begin collecting citations on indexers like Google Scholar and other services. Authors retain copyright of their JOSS article, releasing it under a Creative Commons Attribution 4.0 International License. In its first year, starting in May 2016, JOSS published 111 articles, with more than 40 additional articles under review. JOSS is a sponsored project of the nonprofit organization NumFOCUS and is an affiliate of the Open Source Initiative (OSI).

This article describes the motivation, design, and progress of the Journal of Open Source Software (JOSS). JOSS is a free and open-access journal that publishes articles describing research software. It has the dual goals of improving the quality of the software submitted and providing a mechanism for research software developers to receive credit. While designed to work within the current merit system of science, JOSS addresses the dearth of rewards for key contributions to science made in the form of software. JOSS publishes articles that encapsulate scholarship contained in the software itself, and its rigorous peer review targets the software components: functionality, documentation, tests, continuous integration, and the license. A JOSS article contains an abstract describing the purpose and functionality of the software, references, and a link to the software archive. The article is the entry point of a JOSS submission, which encompasses the full set of software artifacts. Submission and review proceed in the open, on GitHub. Editors, reviewers, and authors work collaboratively and openly. Unlike other journals, JOSS does not reject articles requiring major revision; while not yet accepted, articles remain visible and under review until the authors make adequate changes (or withdraw, if unable to meet requirements). Once an article is accepted, JOSS gives it a digital object identifier (DOI), deposits its metadata in Crossref, and the article can begin collecting citations on indexers like Google Scholar and other services. Authors retain copyright of their JOSS article, releasing it under a Creative Commons Attribution 4.0 International License. In its first year, starting in May 2016, JOSS published 111 articles, with more than 40 additional articles under review. JOSS is a sponsored project of the nonprofit organization NumFOCUS and is an affiliate of the Open Source Initiative (OSI).

The proper management of research data is imperative to ensure that scientific findings are findable, accessible, interoperable and reusable (FAIR). The national and international research organizations support the long-term safeguarding of and the open access to research data from publicly funded research, as laid down in the "Berlin Declaration on Open Access” of 2003 and the “Guidelines on Data Management in Horizon 2020”. The Alliance of German Science Organizations, the Deutsche Forschungsgemeinschaft and the Helmholtz Association took up this idea in their guide- lines for the handling of research data. The HZDR approves the principle of open access to research data. The HZDR supports its guests in the fulfillment of the requirements of funders and of the scientific community. To this end, it pro- vides the necessary infrastructure for data management and regulates the access to research data by these terms and conditions. Open access to research data should be ensured wherever possible taking the pathway of the citable data publication.

Die Langzeitverfügbarkeit von Forschungsergebnissen und der dafür häufig notwendige langfristige Erhalt der Lauffähigkeit von Software ist eine gemeinschaftliche Herausforderung für Forschung, Softwareentwicklung und Gedächtnisinstitutionen. Es stehen verschiedene Maßnahmen wie Standardisierung, Emulation oder auch die Weiterentwicklung durch Open-Source-Communities zur Verfügung, die in unterschiedlichen Kontexten für unterschiedliche Arten von Software zum Einsatz kommen können., Long-term availability of research findings is a challenge for research, software development, and memory institutions altogether. This often includes the necessity to keep research software running over a long time. There are various methods and actions like standardization, emulation, or the development of research software by an open source community which can be taken to achieve this goal.

The suggestions by Hutton et al. might not be enough to guarantee reproducible computational hydrology. Archiving software code and research data alone will not be enough. We add to the suggestion of Hutton et al. that hydrologists not only document their (computer) work, but that hydrologists use the latest best practices in designing research software, most notably the use of containers and open interfaces. To make sure hydrologists know of these best practices, we urge close collaboration with Research Software Engineers (RSEs)., Water Resources

The suggestions by Hutton et al. might not be enough to guarantee reproducible computational hydrology. Archiving software code and research data alone will not be enough. We add to the suggestion of Hutton et al. that hydrologists not only document their (computer) work, but that hydrologists use the latest best practices in designing research software, most notably the use of containers and open interfaces. To make sure hydrologists know of these best practices, we urge close collaboration with Research Software Engineers (RSEs)., Water Resources