> For the complete documentation index, see [llms.txt](https://eucaim.gitbook.io/enduserguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eucaim.gitbook.io/enduserguide/6-userguide4members.md). # 6. User Guide for Data Holders This guide is designed to help users wishing to become a new member to navigate the platform and understand the procedures in place. The EUCAIM platform facilitates data sharing, reuse, and collaborative research within a governed framework to ensure transparency and compliance. If you keep browsing the dashboard, you will find different *‘Become a’* sections corresponding to the four main roles that can be part of EUCAIM. ![Figure 6-1. EUCAIM Dashboard, user roles information](https://2507472304-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMdon45CiYu3gjAOtyiFh%2Fuploads%2Fgit-blob-8882b642dff7d9d70b52e35cdd91b6eb0a7223f6%2Ffig0.avif?alt=media) EUCAIM defines two ways of participating as data holders, each with unique capabilities and contributions in both research and clinical environments: * Data holders transferring data to a Reference Repository Data Holders: If you have completed research projects and aim to maintain your datasets for long-term research availability but need support, EUCAIM offers a solution. By contributing to one of our Reference Nodes, you will ensure that data remains accessible to other researchers. The process involves signing a Data Transfer Agreement (DTA) and sharing information about your project, metadata catalogue, and software. We will guide you through data de-identification, making your contribution hassle-free. * Federated Data Holders: If you manage active repositories and want to maintain your datasets within a federated node, EUCAIM provides the platform. As a Federated Holder, you'll collaborate with us through a Data Sharing Agreement (DSA). Share details about your research project, metadata catalogue, and software, along with information about your local computational and storage capabilities. ## 6.1. Data Preparation EUCAIM defines three interoperability layers: * Tier 1: Interoperability at the level of the Catalogue. * Tier 2: Interoperability at the level of the Federated Search. * Tier 3: Interoperability at the level of the Processing. Whether the participation is as transferring data to a reference node or maintaining a federated node, the data must be prepared for any of the tiers. A detailed description of these interoperability levels and how data have to be prepared for each is provided in section 5 of the Data Holder's Handbook:\ ## 6.2. Contribution through Data Transfer Data Holders can choose between transferring their data or setting up a federated node. The setup of a federated node requires the provision of storage and computing resources, as well as the setup of the federation services and the development of the adaptors. The section 6 in the Data Holder's Handbook describes the case of Data Holders that opt to transfer their data to one of the reference nodes:\ Next sections have been transferred to the Handbook and left here as reference (just to not break links in previous published documents). ### 6.2.1. Create a dataset ### 6.2.2. Data Transfer to the UPV reference node using QP-Insights #### 6.2.2.1 Batch upload via QP-Insights Uploader (Desktop App) #### 6.2.2.2 Case-by-case upload via QP-Insights Web Interface #### 6.2.2.3. Creating the dataset #### 6.2.2.4. Upload metadata #### 6.2.2.5. Dataset tracing ### 6.2.3. Data Transfer to the HealthRI reference node #### 6.2.3.1 Uploading Dicom data #### 6.2.3.2 Uploading Nifti data ## 6.3. Contribution through a Federated Node The section 7 in the Data Holder's Handbook describes the case of Data Holders that opt to build a Federated Node:\ The next subsections have been transferred to the Handbook and left here as reference (just to not break links in previous published documents). ## 6.3.1 Setting up a local node with Mini-node #### 6.3.1.1 Requirements #### 6.3.1.2 Minikube customisation ### 6.3.1.3. Mini node installation ## 6.3.2. Tier 1 compliance ## 6.3.3. Tier 2 compliance ### 6.3.3.1. Node Registration and Deployment ## 6.3.4. Tier 3 compliance