Disk space and folder structure

The mass storage structure is designed to enable efficient organisation of data and data sharing between collaborators within defined groups.

The storage space is divided into three main entities:

  • Administration (ADM)

  • Platform (PTF)

  • Thematic research units (URT)

Besides these main components, there are also user specific directories and a resources (RES) directory.

Here is a schematic of the overall structure of the mass storage:

graph TB subgraph sub1[Main entities] C(Platforms) B(Administration) D(Research) Z(Resources) end subgraph sub2[ ] C --- CC(Platforms) CC --> E(CRC) CC --> F(GEN) CC --> G(IMG) CC --> sup1(...) end subgraph sub3[ ] F --- GG(Teams) GG --> Q(BIOINFO) GG --> R(NGS) GG --> fsub(GENO) GG --> fsub2(SANGER) end subgraph sub4[ ] D --- DD(Thematic Units) DD --> H(GEN) DD --> I(III) DD --> sup2(...) end subgraph sub5[ ] H --- HH(Laboratories) HH --> J(BBB) HH --> K(HG) HH --> L(UAG) HH --> sup3(...) end subgraph sub6[ ] L --- LL(Teams) LL --> M(BLV) LL --> N(FACT) LL --> O(IBD) LL --> P(QCG) LL --> X(TGV) end subgraph sub7[ ] O --- MM(Projects) MM --> S(...) MM --> T(BLUEPRINT) MM --> U(CROHN) MM --> V(SHARE) MM --> W(PLATFORMS) end style sub1 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style sub2 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style sub3 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style sub4 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style sub5 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style sub6 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style sub7 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style C fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style B fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style E fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style F fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style G fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style H fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style I fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style J fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style D fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style M fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style N fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style O fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style P fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style Q fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style R fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style S fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style T fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style U fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style V fill:#cfd2fa, stroke:#878ef5, stroke-width:2px style W fill:#dffccc, stroke:#5cb821, stroke-width:2px style X fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style K fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style L fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style Z fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style fsub fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style fsub2 fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style sup1 fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style sup2 fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style sup3 fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style CC fill:#91c5df,stroke:#4393c3,stroke-width:2px, stroke-dasharray: 5, 5 style DD fill:#91c5df,stroke:#4393c3,stroke-width:2px, stroke-dasharray: 5, 5 style GG fill:#91c5df,stroke:#4393c3,stroke-width:2px, stroke-dasharray: 5, 5 style HH fill:#91c5df,stroke:#4393c3,stroke-width:2px, stroke-dasharray: 5, 5 style LL fill:#91c5df,stroke:#4393c3,stroke-width:2px, stroke-dasharray: 5, 5 style MM fill:#91c5df,stroke:#4393c3,stroke-width:2px, stroke-dasharray: 5, 5

Home directory

Each user that connects to the mass storage gets a home directory limited to 100 GB in size (See the explanations about quotas).

It is intended for storing user analysis data not related to a project, or for installing user specific software not available on the cluser.

It also serves as an access point to all other folders a member has access to, thanks to the _SHARE_ located inside. This particular folder contains symbolic links to all the shared folders the user has access to (e.g., resources or projects).

Here is a schematic of the home directory of user u123456:

graph TB subgraph sub1[User u123456] C(_SHARE_) B(user_personnal_folder_01) D(user_personnal_folder_02) end subgraph sub2[ ] C --- CC(Shared folders to which the user u123456 has access) CC --> E(Resources) CC --> F(Platforms) CC --> G(Research) CC --> H(Administration) end style sub1 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style sub2 fill:#f3a581,stroke:#d65f4d,stroke-width:2px style C fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style B fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style D fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style F fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style G fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style H fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style E fill:#d2e6f0, stroke:#91c5df, stroke-width:2px style CC fill:#91c5df,stroke:#4393c3,stroke-width:2px, stroke-dasharray: 5, 5

Note

This directory is located on the mass storage. Hence, it is subject to the same backup policy as any other directory on the mass storage.

Teams and projects directories

Each member of the GIGA is, by definition, part of a research team and is working on one or more projects. To enable the sharing of data and results between members working on the same project, the mass storage infrastructure also contains team and project folders. Team and project folders are created upon request by a PI. Every team folder and the data/results contained within it are under the responsibility of this PI. Upon assignment to a project/team, GIGA members need to be granted access to the corresponding team folder on the mass storage. Folder privileges are set up and modified by UDI GIGA-MED, based on PI instructions.

Note

Space available in teams and projects folders belonging to a given laboratory is limited by a quota. Data from the associated platform-shared folders are included in this quota.

Platforms and teams shared directories

Upon request, UDI GIGA-MED can create SHARE folders:

  • inside a team directory to allow team members working on different projects to share data.

  • inside a platform directory to allow platforms to share newly generated/acquired data with other GIGA members[1].

    Important

    Users can either leave all data transferred by the platforms in the PLATFORMS folder or move them to the corresponding Project folder. Of note, most journals will ask for these raw data to be uploaded on a server before to accept any publication relative to them, so it’s extremely important to organise and annotate them properly to be able to retrieve them when needed.

    Danger

    To avoid having multiple copies of large files, the platforms won’t keep a copy of these raw data. It’s the PI responsibility to make sure that precious files are stored and annotated correctly.

Resources directory

This directory contains data accessible by all GIGA members, such as genomes or singularity containers.