Skip to content

Sciebo-RDS/Sciebo-RDS

Repository files navigation

Sciebo RDS

pipeline status MIT License Version Release gitter

Sciebo RDS (Sciebo Research Data Services) allows researchers to enrich their research data with metadata and to export it directly from Enterprise Sync and Share (EFSS) Systems like Owncloud to Data Repositories like Zenodo and OSF. It acts as a interoperability layer, allowing them to assign a directory on a Sync and Share System to a research project, annotating the contained data to match the format required by the desired Data Repository and publishing the Research Data directly from the Cloud.

No need to download all the data to a desktop computer to cumbersomely upload it to the repository interface again.

Find more information on the official website at www.research-data-services.org.

Screenshots

An_RDS1 Configuring a project An_RDS2 Adding metadata
An_RDS2 Adding metadata An_RDS4 Adding metadata
An_RDS5 Publishing An_RDS6 Connecting repositories

Deployment

Requirements

To deploy Sciebo RDS you will need:

  1. A Kubernetes cluster
  2. An OwnCloud instance
  3. Two different domains

Getting Started

Please refer to our Getting Started Guide to learn how to deploy Sciebo RDS.

Development environment

To deploy a local environment on top of Minikube, including RDS and NextCloud and / or OwnCloud, please refer to this guide.

Monorepo Structure

We use a monorepo to make it easier to track related changes. This means that you will find all relevant files in this Github repository.

The following table will give an impression of the individual parts.

Folder Description
/charts Helm charts
/docs Website with documentation
/getting-started Files for easy deployment
/RDS The RDS code
/RDS/layer0_ingress/web/server The Python Backend
/RDS/layer0_ingress/web/client/packages/codebase The Vue.js Frontend
/RDS/layer3_central_services Microservices ResearchManager, TokenStorage
/ Metafiles and configuration

The monorepo only includes those parts of Sciebo RDS that are officially maintained by the University of Münster.

Additional Repositories

There is also an additional repository that functions as a community hub for development of 3rd party connectors, such as Dataverse. These connectors are community managed – if you are planning on developing a connector and sharing it as Open Source, feel free to use this repository.
A third repository is used for the ongoing development of the Nextcloud Plugin.

Contributing and Documentation

Contributions are always welcome! You can find technical documentation and guides on how to extend Sciebo RDS to your needs and connect additional repositories on our website.

We follow the Gitlab-flow. Our default branch is called develop and can be changed exclusively through pull requests via Github.
When a certain amount of features are done, they are merged into release. From there we will set a tag and publish the changes in helm and docker repositories.

Please adhere to our code of conduct.

Feedback and Support

Please use the Github Issues and Github Discussions for feedback and technical questions. We also have a Gitter chat. :)

If you are using Sciebo RDS as a researcher and need user level support, please refer to the administrators of your Sciebo RDS instance. You can find their email adresse in the Help tab of your Sciebo RDS instance.

Acknowledgements

Sciebo RDS relies on describo-online for metadata management.

Authors

Sciebo RDS is a project developed by the University of Münster and funded by the DFG.

You can reach the development team at sciebo.rds <at> uni-muenster.de or on Gitter.