DataHUBs are the central place where research data and associated metadata can be stored as annotated research context (ARC). All DataHUBs are based on Gitlab and therefore offer version control features and give users full control over who can see and interact with their research data. Every DataHUB implementation has backup strategies in place to ensure that the data which is stored there is as safe as possible.
-Our Core - DataPLANT DataHUB provides a powerful platform for collaborative research on Annotated Research Contexts (ARCs). The Core DataHUB, maintained by DataPLANT, acts as a central instance for testing reference implementations and new features. It integrates all available add-ons and forms the centrepiece of our research environment. To get more information about DataHUB features and how to interact with DataHUBs, please visit our Knowledge Base.
-For maximum flexibility, we enable research groups and universities to run their own on-premise hub - known to us as a Satellite. This allows each institution to fulfil its individual requirements and design the platform according to its own needs.
-The on-premises DataHUB documentation and Docker images for installation can be found here:
-https://github.com/nfdi4plants/DataHUB.
-The maintenance and administration of the on-premise hub is in the hands of the respective institution. This decentralised approach ensures that research groups retain full control over their data and research environment. Each satellite can be configured according to the specific requirements and standards of the institution.
Our goal is to create an open and collaborative research environment that enables research groups worldwide to work together effectively and develop innovative solutions.
+DataPLANT provides two main DataHUB nodes, the DataHUB (reference) and the DataHUB (federated), which are available for the whole plant science community. In addition, there are further implementations for specific sub-communities which are called on-premise. All DataHUBs have backup and sustainability strategies in place ensuring the safety and longtime availability of the data.
+We recommend choosing a DataHUB implementation before creating your first ARC and keeping all your ARCs on a single DataHUB. To get more information about DataHUB features and how to interact with DataHUBs, please visit our Knowledge Base.
List of DataHUBs
+| DataHUB | +Futher Information | +
| DataHUB (reference) | ++The DataHUB (reference) is hosted at the University of Freiburg. To gain access to this DataHUB, you can either create an account on the sign-up page, or login through your home institution or another identity provider like ORCID, Google, or Apple. To secure your data, the DataHUB Node Freiburg makes use of backup and resilience strategies provided through the backend. + | +
| DataHUB (federated) | ++The DataHUB (federated) is a high-availability implementation of the DataHUB concept hosted at the University of Tübingen. The DataHUB runs on a federated infrastructure that relies on fail-over strategies to ensure that the service is always available, even when hardware or network failures occur. The nfdi4plants.de DataHUB can be accessed with your home institution credentials through the [Life Science Research Infrastructure](https://lifescience-ri.eu/ls-login.html) or by using another identity provider, like ORCID. + | +
| TRR356 (PlantMicrobe) | ++The TRR356 (PlantMicrobe) is a DataHUB implementation specific for the transregional collaboration project PlantMicrobe and is hosted at the University of Tübingen and the LMU in Munich. Only members of the project TRR356 PlantMicrobe have access to this DataHUB and can publish data there. Like the nfdi4plants.de DataHUB, the PlantMicrobe DataHUB runs on a federated infrastructure that relies on fail-over strategies to ensure the availability of the service. + | +