Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
rdms:solution:team [2023/06/28 15:02] jelte Started the normal user section. |
rdms:solution:team [2024/04/04 11:54] (current) jelte spell correction: native --> native |
||
---|---|---|---|
Line 4: | Line 4: | ||
{{ : | {{ : | ||
- | ===== General | + | ===== General |
- | The following points summarize some of the basics of these special collections | + | The following points summarize some of the basics of Team Drives |
* Within the different storage areas of the RDMS, the so called //Team Drives// fulfill the role of a **shared storage space for research groups**. | * Within the different storage areas of the RDMS, the so called //Team Drives// fulfill the role of a **shared storage space for research groups**. | ||
* They can be used to store a group' | * They can be used to store a group' | ||
* The RDMS Team Drive are can be seen as the **RDMS equivalent of the Y: Drive**. | * The RDMS Team Drive are can be seen as the **RDMS equivalent of the Y: Drive**. | ||
- | * Within the RDMS, Team Drives are always located at ''/ | + | * Within the RDMS, Team Drives are always located at ''/ |
* The data in a RDMS Team Drive can be shared with other group members, but also other RDMS users. | * The data in a RDMS Team Drive can be shared with other group members, but also other RDMS users. | ||
+ | * [[rdms: | ||
* The initial setup of a Team Drive has to be request. | * The initial setup of a Team Drive has to be request. | ||
- | * The management of a Team Drive (new users, permissions management) is in the hand of the research groups themselves. | + | * The management of Team Drives |
In the following sections, it will be described how a RDMS Team Drive is initially requested and setup. Furthermore, | In the following sections, it will be described how a RDMS Team Drive is initially requested and setup. Furthermore, | ||
Line 21: | Line 22: | ||
While the management and maintenance of a RDMS Team Drive are in the hands of the individual research groups or Team Drive owners, the initial setup of a Team Drive has to be requested via the RDMS Support. | While the management and maintenance of a RDMS Team Drive are in the hands of the individual research groups or Team Drive owners, the initial setup of a Team Drive has to be requested via the RDMS Support. | ||
- | To request a Team Drive, please contact < | + | To request a Team Drive, please contact < |
For the setup of a Team Drive, the following additional information are needed: | For the setup of a Team Drive, the following additional information are needed: | ||
- | - **Name of the Team Drive:** The requester decides for a name that the Team Drive should have. The name will also define the location within the RDMS. The new drive will be at ''/ | + | - **Name of the Team Drive:** The requester decides for a name that the Team Drive should have. The name will also define the location within the RDMS. The new drive will be at ''/ |
- **Owner Information**: | - **Owner Information**: | ||
- | - **Further Information: | + | - **Further Information: |
- | It should be noted that **the creation of a RDMS Team Drive also creates | + | It should be noted that **the creation of a RDMS Team Drive also creates |
- | If it is desired by the owner of the RDMS Team Drive to manage the permissions on a group level, in contrast to just assigning permissions for individual users (see below), please also mention this during | + | Moreover, the creator |
- | + | ||
- | Managing on a group level needs additional | + | |
- | Of course, it is also at a later stage always possible to add these privileges | + | |
===== Working with Team Drives ===== | ===== Working with Team Drives ===== | ||
- | For this example, we assume that a new Team Drive with the name '' | + | For this example, we assume that a new Team Drive with the name '' |
As there is a difference for the usage of Team Drives by by the managers/ | As there is a difference for the usage of Team Drives by by the managers/ | ||
Line 47: | Line 45: | ||
==== For Team Drive Owners/ | ==== For Team Drive Owners/ | ||
+ | |||
+ | ++++ Click to display section | | ||
Team Drive owners/ | Team Drive owners/ | ||
Line 59: | Line 59: | ||
+ | |||
+ | ---- | ||
=== Group Users Management Tab (Manage RDMS Team Drive Group Members) === | === Group Users Management Tab (Manage RDMS Team Drive Group Members) === | ||
Line 75: | Line 77: | ||
Removing Group members is done from the same tab. Simply click on the trash bin symbol next to the user's name. The user will be removed. | Removing Group members is done from the same tab. Simply click on the trash bin symbol next to the user's name. The user will be removed. | ||
- | **Note:** Do not remove yourself from the Group. Otherwise, you loose the capability to manage it. In case you accidentally remove yourself from a group, get in contact with the RDMS support. | + | **Note:**\\ Do not remove yourself from the Group. Otherwise, you loose the capability to manage it. In case you accidentally remove yourself from a group, get in contact with the RDMS support. |
{{ : | {{ : | ||
Line 104: | Line 106: | ||
- **Add Group:** Can be used to assign permission for a RDMS group, instead of a single user. | - **Add Group:** Can be used to assign permission for a RDMS group, instead of a single user. | ||
- | For all three selection, it is possible to choose a suitable [[rdms: | + | For all three selection, it is possible to choose a suitable [[rdms: |
+ | |||
+ | ---- | ||
=== Team Drive Data Tab === | === Team Drive Data Tab === | ||
Line 114: | Line 118: | ||
Selecting first a file/folder and then pressing the '' | Selecting first a file/folder and then pressing the '' | ||
+ | ---- | ||
- | === Additional | + | === Additional |
**Assigning other Owners/ | **Assigning other Owners/ | ||
Line 127: | Line 132: | ||
The steps to assign permissions that were described above always assign permissions on the top-level of the Team Drive, and all of its sub-folder and files if the specific checkbox was selected. | The steps to assign permissions that were described above always assign permissions on the top-level of the Team Drive, and all of its sub-folder and files if the specific checkbox was selected. | ||
- | For a more granular permission assignment, it is possible to adjust the permissions also differently for different files/ | + | For a more granular permission assignment, it is possible to adjust the [[rdms: |
For this, the respective file/folder has to be selected from the data tab. Subsequently, | For this, the respective file/folder has to be selected from the data tab. Subsequently, | ||
Line 133: | Line 138: | ||
{{ : | {{ : | ||
- | **Note: | + | **Note:**\\ |
- | While there are several use-cases and advantages of a granular permission management of data in a Team Drive, please take into account that this can lead to a loss of overview about which permissions are currently set on which files/ | + | |
Also please take into account that a permission change on a higher level will overwrite the different individual permissions of the same user/group if ' | Also please take into account that a permission change on a higher level will overwrite the different individual permissions of the same user/group if ' | ||
If you want to have a Team Drive that is setup with granular permissions for different users/ | If you want to have a Team Drive that is setup with granular permissions for different users/ | ||
+ | |||
+ | **Permission Inheritance and Team Drives** | ||
+ | |||
+ | It is furthermore possible to enable/ | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The owner of a Team Drive can enable permission inheritance on the whole drive if that is desired. To do this, you have to navigate to the management tab of the Team Drive and then first select the '' | ||
+ | |||
+ | From there, you can access a context menu that allows you to select 'Set permission inheritance' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Please read the section about [[rdms: | ||
**The Advantages of using Groups for Permission Management** | **The Advantages of using Groups for Permission Management** | ||
Line 157: | Line 175: | ||
For those RDMS users that do not use the web portal to work in the system, but who rather work via the command-line interface (CLI) using '' | For those RDMS users that do not use the web portal to work in the system, but who rather work via the command-line interface (CLI) using '' | ||
- | Please refer to the [[rdms: | + | Please refer to the [[rdms: |
A selection of the most common commands for CLI-based Team Drive management: | A selection of the most common commands for CLI-based Team Drive management: | ||
Line 165: | Line 183: | ||
* '' | * '' | ||
+ | |||
+ | ---- | ||
+ | |||
+ | === Additional Info: Creation of Team Drives by the User === | ||
+ | |||
+ | If you have requested a Team Drive, your account gets promoted to ' | ||
+ | |||
+ | To create a Team Drive as a ' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Afterwards, the system will ask you for the desired name of the new Team Drive. Specify a name, then confirm, and a new Team Drive is created with the specified name. | ||
+ | |||
+ | ++++ | ||
==== For ' | ==== For ' | ||
+ | |||
+ | ++++ Click to display section | | ||
For ' | For ' | ||
Line 174: | Line 208: | ||
=== Accessing Team Drives from the Web Portal and RDMS Clients === | === Accessing Team Drives from the Web Portal and RDMS Clients === | ||
- | === Transfer | + | **From the web portal** |
+ | |||
+ | From the web portal, available Team Drives are listed in the [[rdms: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Afterwards, basic tasks can be performed directly in the web interface, for example the creation of new folders or uploading of small files (<50 MB). | ||
+ | |||
+ | Alternatively, | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | **Using one of the GUI clients (e.g. Cyberduck)** | ||
+ | |||
+ | When using Cyberduck as an example for a GUI client for the RDMS, the Team Drive locations can be accessed in the following way: | ||
+ | |||
+ | If using the **native iRODS protocol for Cyberduck** and when no special configuration are made in Cyberduck, you will see your personal Home location after login (e.g. ''/ | ||
+ | |||
+ | As this is one level down the folder hierarchy of the RDMS, it is first needed to navigate one level up to see available RDMS Team Drive. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In the higher level, in this example ''/ | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | For Cyberduck on Windows, it is also again possible to directly specify the full location to reach a Team Drive. | ||
+ | |||
+ | Within Cyberduck, this can be done from the Menu under '' | ||
+ | |||
+ | **Note:**\\ If you do not use the native iRODS protocol for the connection to the RDMS in Cyberduck, but instead use the WebDAV protocol, the situation is slightly different: | ||
+ | |||
+ | Using the WebDAV protocol in Cyberduck always opens the location above the users' | ||
+ | |||
+ | From there, other location like Team Drives can be accessed directly. | ||
+ | |||
+ | **Via the CLI using '' | ||
+ | |||
+ | For users of '' | ||
+ | |||
+ | $ icd / | ||
+ | |||
+ | === Data Transfer/Sharing and Metadata Management within Team Drives === | ||
+ | |||
+ | Data transfer | ||
+ | |||
+ | If this does not work out as expected, you likely miss the correct permissions for your desired task. | ||
+ | |||
+ | Please check our overview about the different [[rdms: | ||
+ | If in doubt, contact the owner/ | ||
+ | ++++ |