Research increasingly becomes data-driven, with substantial amounts of information being generated and analyzed to produce new insights and discoveries. Since Virtual Research Environments (VRE) like JupyterHub [1] are becoming more available, the audience that uses these compute resources becomes more heterogeneous too, demanding seamless identity management, datasource integration and high availability from VRE service providers. To make VRE research outputs more FAIR, they can be deposited in dedicated research data repositories. At TU Wien, we provide two different research data repositories [2,3] for publication of research data results, and Jupyter [4] for data processing as part of our VRE.

In order to improve user experience, we are building a library to be used in the Jupyter notebooks that allows researchers to use datasets directly in the VRE seamlessly provided by the repositories in the background, abstracted from the researcher.

Because the library only depends on public APIs, it is not tied to our VRE and can be used in other deployments as well. Further, we aim to keep the design of the library intentionally simple so that it can be extended with support for additional repository types.

[1] https://jupyter.org/hub

[2] https://researchdata.tuwien.ac.at

[3] https://www.ifs.tuwien.ac.at/infrastructures/dbrepo/

[4] https://jupyter.hpc.tuwien.ac.at/

Increasing the level of FAIRness of resources is high on the agenda of repository developers and managers. The FAIR Signposting profile offers concrete recipes to approach this goal and has therefore seen an increased level of adoption in the international repository community. To further support developers, we have designed and implemented the FAIR Signposting Validator. The validator provides immediate feedback to users regarding the syntactic and semantic validity of their FAIR Signposting implementation. This presentation will outline the design, implementation details, and utility of the validator. We will share the source code openly for the developer community, in order to enable local installations.

Antleaf and Cottage Labs are working with Ruhr University Bochum (RUB) to develop a Research Data Management System (RDMS) based on a Samvera Hyrax 3 repository. Three key requirements have, taken together, led to some interesting challenges:

1. RDMS must support multiple, complex data/metadata models

2. RDMS must preserve data privacy within each research group, until it is ready for publishing.

3. RDMS must persisting all data & metadata in RUB's S3 object storage facility

The presentation will give a brief overview of the three requirements, before describing the challenges that these requirements introduce both separately and in conjunction. It will then describe the technical solutions to these challenges, commenting on their effectiveness and any trade-offs that have had to be accommodated.

Digital preservation, and data preservation, are key concerns to repository owners and stakeholders. However, implementation of system-independent, versioned, digital storage for digital repository content is often proprietary and financially expensive. Here, we present an open source, decoupled, remote solution for the preservation of repository content in an OCFL (Oxford Common File Layout) file system using the Fedora 6 Repository application to manage ingest and export.

A new effort under the “Signposting the Scholarly Web” umbrella specifies a way in which repositories can advertise the interoperability affordances they support by publishing a FAIR Interoperability Catalog, FAIRiCat in short. It also specifies how FAIRiCats can be discovered to support obtaining an insight in the nature of a repository’s investments in interoperability, finding the machine entry points of repository-wide affordances (e.g. SPARQL endpoint), and examples of affordances that are available when interacting with individual objects managed by the repository (e.g. IIIF support).