RRP helps researchers turn their code-based analysis workflows into FAIR data products with provenance tracking. RRP takes inspiration from BinderHub, but makes data input and output a priority and lets users export the entire project for easy sharing with colleagues or reviewers.
Use Case Status Before Joining EOSC Data Commons
Currently, RRP relies on openBIS (the electronic lab notebook and database solution also developed at ETH Zurich) for staging input data, which can be either the user’s unpublished research data or data mirrored from a public repository. RRP instances run on dedicated Kubernetes clusters that have to be set up manually for individual user groups upon request.
Objectives in the Project
- Make RRP a deployment target for workflows registered in the Catalogue of Tools;
- Let RRP users package new workflows and register them in the Catalogue of Tools;
- Contribute to research FAIRification, as RRP is a tool that helps scientists track the provenance of code and data as they are producing new research outputs.
Integration with EOSC Data Commons Services and Components
- Two representative bioinformatics workflows (genome analyses) will be made available for the Catalogue of Tools in the Matchmaker service, both depending on RRP as an execution environment, i.e. VRE.
- Contribute a plug-in for the Data Player’s Dispatcher component, which will handle the Package and translate it into API calls to an RRP instance, possibly spawned on demand on EOSC infrastructure.
Technical Integration Plan
RRP still under development before integration with EOSC Data Commons components.
One-way integration in place, i.e. receiving a Package (using one of our demonstration workflows) from the Dispatcher, by the first release.
Enable round-trip integration, i.e. upload of new workflows to the Catalogue of Tools, in the second release, once an API suitable for RRP’s needs is specified and available.

