D3.4. Final Platform Design
Creators: name: Blanquer, Ignacio
name: Quilis, J. Damian Segrelles
name: López-Huguet, Sergio
name: Lozano, Pau
name: Alic, Andrei Stefan
Publisher: name: Zenodo
Year: 2022
Subjects: subject: Cancer Images
subject: Cloud
subject: Repository
subject: Architecture
subject: FOS: Civil engineering

description: A final design of the CHAIMELEON Repository has been performed systematically and extensively (see “D3.3. Interim Platform Design” - 10.5281/zenodo.5645737 - for more details) that took into account the information on standards and technologies of previous deliverables. This deliverable performs a thorough process of identification of the expected functionality (User Actions) of the repository. The CHAIMELEON repository design is based on three main concepts: a) The CHAIMELEON Repository as a platform to store and process the data; b) Datasets as research objects comprising a subset of anonymised and annotated data that has a Persistent Identifier; c) Data Analytics Models trained on the data with a Persistent Identifier assigned, which can be embedded into tools in a marketplace. This document is a guideline for implementing the repository and all its components. The repository will be mainly developed using tools released under Open-Source licences. The document also serves as a guide for external developers who would like to contribute to the CHAIMELEON Repository. The repository users are classified into 8 User Roles or user profiles. Each role has a different way of interacting with the repository (User Actions) and, therefore, different permissions. A user may have multiple roles, but operations are defined at individual roles to limit permissions and accessibility. These actions trigger interactions among components illustrated in the architecture, specified through 34 Use Cases organised in 8 areas: Authentication and authorisation, Data Lake Management, Dataset Management, Processing Application Management, Standalone Application Management, Model Management, Marketplace Management and Tracing data. In the final architecture, the CHAIMELEON Repository identified 5 Platform Applications as Persistent applications that mainly expose the functionality (User Registration Application, Case Explorer Application, Marketplace, Dataset Explorer Application and Application Dashboard), 6 Services that interact directly with the resources (Authentication Service, Data Ingestion/Access Service, Dataset Service, Tracer Service and Orchestrator Service) and 6 Storages (for user data, clinical data, datasets, application binaries, source code and traceability). This process ended up with 85 requirements covering 15 transversal requirements applied to all Storages, Services and Applications, 28 requirements laid to the Storage, 18 for Services and 24 for Platform Applications. One of the critical aspects of the repository is traceability. Despite the use of anonymised data, the repository restricts the data processing to its local environment, so data is not downloaded outside of the platform. Even in this case, the repository annotates the main research objects and actors (datasets, models, users and applications) with persistent identifiers and keeps track of the interactions. This approach increases the trustworthiness of the repository and provides higher confidence to data providers. This final architecture of the CHAIMELEON Repository will be implemented in the frame of the project and will be exposed to the user community as planned in the project.