Research Object Hub (RoHub) for FAIR research data management and Open Science in practice
Creators: name: Coca-Castro, Alejandro
name: Fouilloux, Anne
name: Iaquinta, Jean
Publisher: name: Zenodo
Year: 2023
Subjects: open science
collaboration
training
workshop
research object
EDSBook

description: Short presentation given in the mini-workshop on "Research Object Hub (RoHub) for FAIR research data management and Open Science in practice", during the Collaboration Workshop 2023. 16 participants attended this mini-workshop where the basics of Research Objects were presented. <strong>Scheduled:</strong> CW23 Day 2: Wednesday, 3 May 2023 from 15:10 - 16:10 BST (14:10 - 15:10 UTC; 60 minutes) <strong>Facilitator(s):</strong> Anne Fouilloux (Simula Research Laboratory), Alejandro Coca-Castro (The Alan Turing Institute) and Jean Iaquinta (The University of Oslo) <strong>Abstract:</strong> RoHub is a Research Object (RO) management platform that enables researchers to collaboratively manage, share and preserve their research work. RoHub implements the full RO model and paradigm: resources associated to a particular research work are aggregated into a single FAIR digital object, and metadata relevant for understanding and interpreting the content is represented as semantic metadata that are user and machine readable. In this mini-workshop, you will learn how to use RoHub to search, create and reuse different types of ROs: Bibliography-centric, data-centric, executable, software-centric, workflow-centric ROs. A new RO can either be created from scratch (empty Live RO) or from another existing RO (fork RO) and aggregate new objects (or modify existing objects) through its whole life cycle. This means, RO is filled incrementally by aggregating relevant resources such as software, workflows, datasets, documents according to its typology that are being created, reused or repurposed. These resources can be modified at any point in time. We can copy and keep ROs in time through snapshots which reflect their status at a given point in time. Snapshots can have their own identifiers (DOIs) which facilitates tracking the evolution of a research. At some point in time, a RO can be published and archived (so called Archived RO) with a permanent identifier (DOI). New Live ROs can be derived based on an existing Archived RO, for instance by forking it. In this mini-workshop, we will fork an existing executable RO containing a Jupyter Notebook as a main resource. Then we will check its reproducibility (through a Binder service such as MyBinder and/or EGI Binder) and modify the Jupyter Notebook. Finally, the updated Jupyter Notebook will be saved in the forked RO to update it. We will also discuss the reusability of Jupyter Notebook by introducing the need for defining and adopting Best practices. As an example, we will use the Environmental Data Science Book (EDS) where the EDS community has defined clear guidelines for submission and reviewing, templates for creating and scheduling notebooks using GitHub Actions CI/CD tools, FAIR practices through RoHub and Binder to facilitate fully documented, shareable and reproducible notebooks. <strong>Audience:</strong> Researchers with basic knowledge of Jupyter Notebooks and programming (Python, R, Julia).