Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
rdms:solution:team [2025/07/21 11:40] – [General Concepts of the RDMS Team Drives] burcurdms:solution:team [2025/07/22 10:34] (current) – burcu
Line 6: Line 6:
 ===== General Concepts of the RDMS Team Drives ===== ===== General Concepts of the RDMS Team Drives =====
  
-The following points summarize some of the basics of Team Drives in the RDMS:+The following points summarise some of the basics of Team Drives in the RDMS:
   * Within the different storage areas of the RDMS,  Team Drives fulfil the role of a **shared storage space for research groups**.   * Within the different storage areas of the RDMS,  Team Drives fulfil the role of a **shared storage space for research groups**.
   * They can be used to store a group's research data in the mid- and long-term.   * They can be used to store a group's research data in the mid- and long-term.
-  * The RDMS Team Drive are can be seen as the **RDMS equivalent of the Y: Drive**. +  * The RDMS Team Drive can be seen as the **RDMS equivalent of the Y: Drive**. 
   * Within the RDMS, Team Drives are always located at ''/<zone>/home/<Team_Name>''.   * Within the RDMS, Team Drives are always located at ''/<zone>/home/<Team_Name>''.
-  * The data in a RDMS Team Drive can be shared with other group members, but also other RDMS users.+  * The data in an RDMS Team Drive can be shared with other group members, but also with other RDMS users.
   * [[rdms:solution:policies|Automated Policies]] can be implemented by the managers of a Team Drive.    * [[rdms:solution:policies|Automated Policies]] can be implemented by the managers of a Team Drive. 
-  * The initial setup of a Team Drive has to be request. +  * The initial setup of a Team Drive has to be requested. 
-  * The management of Team Drives (new users, permissions management) is in the hand of the research groups themselves. +  * The management of Team Drives (new users, permissions management) is in the hands of the research groups themselves. 
  
-In the following sections, it will be described how a RDMS Team Drive is initially requested and setup. Furthermore, the management of a Team Drive and the working with a Team Drive will be explained by using some examples. +In the following sections, it will be described how an RDMS Team Drive is initially requested and set up. Furthermore, the management of a Team Drive and working with a Team Drive will be explained by using some examples. 
  
 ===== Initial Setup ===== ===== Initial Setup =====
  
-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 an 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 <rdms-support@rug.nl>.  To request a Team Drive, please contact <rdms-support@rug.nl>. 
  
-For the setup of a Team Drive, the following additional information are needed:+For the setup of a Team Drive, the following additional information is 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 ''/<zone>/home/<Team_Name>''. +  - **Name of the Team Drive:** The requester decides on a name that the Team Drive should have. The name will also define the location within the RDMS. The new drive will be at ''/<zone>/home/<Team_Name>''. 
-  - **Owner Information**: Every RDMS Team Drive gets at least one owner assigned to it. This is usually the PI of a research group. As is just possible to assign a owner if this person is already registered in the RDMS, please login at least once via the [[https://research.web.rug.nl/rdmswebapp/|RDMS web portal]] to have your account registered. +  - **Owner Information**: Every RDMS Team Drive gets at least one owner assigned to it. This is usually the PI of a research group. As it is just possible to assign an owner if this person is already registered in the RDMS, please log in at least once via the [[https://research.web.rug.nl/rdmswebapp/|RDMS web interface]] to have your account registered. 
-  - **Further Information:** As will be explained later, individual users and also groups can be added with different permissions to a Team Drive. This can be done at any time by the owner of a RDMS Team Drive, but if it is already known that certain groups or users should have access to the Team Drive, it is also possible to adjust this already during the initial setup.+  - **Further Information:** As will be explained later, individual users and also groups can be added with different permissions to a Team Drive. This can be done at any time by the owner of an RDMS Team Drive, but if it is already known that certain groups or users should have access to the Team Drive, it is also possible to adjust this already during the initial setup.
  
-It should be noted that **the creation of a RDMS Team Drive also creates an associated RDMS Group** with the same name as the Team Drive. This group is automatically added to the newly created Team Drive. +It should be noted that **the creation of an RDMS Team Drive also creates an associated RDMS Group** with the same name as the Team Drive. This group is automatically added to the newly created Team Drive. 
  
-Moreover, the creator of the Team Drive will get elevated 'groupadmin' permissions within the RDMS that allow to manage Team Drive via the [[rdms:webapp:datamanagement|Data Management tab]] of the web portal as well as create further new Team Drives if needed (see below). +Moreover, the creator of the Team Drive will get elevated 'groupadmin' permissions within the RDMS that allow them to manage Team Drive via the [[rdms:webapp:datamanagement|Data Management tab]] of the web interface as well as create further new Team Drives if needed (see below). 
  
 ===== Working with Team Drives ===== ===== Working with Team Drives =====
  
-For this example, we assume that a new Team Drive with the name ''Example_Group1'' was requested. Accordingly, the location of the new Team Drive is at ''/<zone>/home/Example_Group1'', the top-level of our RDMS Team Drive.+For this example, we assume that a new Team Drive with the name "Example_Group1" was requested. Accordingly, the location of the new Team Drive is at ''/<zone>/home/Example_Group1'', the top-level of our RDMS Team Drive.
  
-As there is a difference for the usage of Team Drives by by the managers/owners of the Team Drives and by 'normal' RDMS users, the following section will be split according to this distinction: +As there is a difference in the usage of Team Drives by the managers/owners of the Team Drives and by regular RDMS users, the following section will be split according to this distinction: 
  
-   * The section for Team Drive owners/managers will focus on managing of the RDMS Drive (permissions, sharing options, etc.) with the RDMS web interface.  +   * The section for Team Drive owners/managers will focus on managing the RDMS Drive (permissions, sharing options, etc.) with the RDMS web interface.  
-   * The section for 'normal' RDMS users will mostly focus on accessing the Team Drive collection to transfer data in/out of this area as well as collaboration. +   * The section for regular RDMS users will mostly focus on accessing the Team Drive collection to transfer data in/out of this area, as well as collaboration. 
  
  
Line 51: Line 51:
 Team Drive owners, if they are also group admins, can use the [[rdms:webapp:datamanagement|Data Management tab]] in the interface to get an overview of currently set permissions of the respective Team Drives, and also to manage the Team Drive.   Team Drive owners, if they are also group admins, can use the [[rdms:webapp:datamanagement|Data Management tab]] in the interface to get an overview of currently set permissions of the respective Team Drives, and also to manage the Team Drive.  
  
-Navigating to the Data Management tab and selecting the ''Team drives'' button will reveal an overview of all RDMS Team Drives that are available for the user.+Navigating to the Data Management tab and selecting the "Team drives" button will reveal an overview of all RDMS Team Drives that are available for the user.
  
 {{ :rdms:solution:team_drive1.png?direct&300 |}} {{ :rdms:solution:team_drive1.png?direct&300 |}}
Line 65: Line 65:
 === Group Users Management Tab (Manage RDMS Team Drive Group Members) === === Group Users Management Tab (Manage RDMS Team Drive Group Members) ===
  
-{{:rdms:solution:team_group_tab.png?direct&50|}} The leftmost button gives an overview about the current members of the RDMS Group that is automatically created and added to a Team Drive when it is setup. +{{:rdms:solution:team_group_tab.png?direct&50|}} The leftmost button gives an overview of the current members of the RDMS Group that is automatically created and added to a Team Drive when it is set up. 
  
  
 **Adding a new group member** **Adding a new group member**
  
-To add a new member to this group, the cogwheel symbol in the top-right corner reveals a context menu. Selecting 'Add Group member' from this menu can be used to add a new member to this Team Drive Group. Select the user that should be added in the next menu and then confirm.+To add a new member to this group, the cogwheel symbol in the top-right corner reveals a context menu. Selecting "Add Group member" from this menu can be used to add a new member to this Team Drive Group. Select the user that should be added in the next menu and then confirm.
  
 {{ :rdms:solution:team_add_group_merged.png?direct&600 |}} {{ :rdms:solution:team_add_group_merged.png?direct&600 |}}
Line 78: Line 78:
 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 lose the capability to manage it. In case you accidentally remove yourself from a group, get in contact with the RDMS support. 
  
 {{ :rdms:solution:team_group3.png?direct&1000 |}} {{ :rdms:solution:team_group3.png?direct&1000 |}}
Line 85: Line 85:
 === Team Drive Permissions Tab === === Team Drive Permissions Tab ===
  
-{{:rdms:solution:team_permissions_tab.png?direct&50|}} The middle button gives an overview about the current assigned permissions on the top-level of the Team Drive. The RDMS Groups that have permissions are also listed here. The currently set [[rdms:data:permissions|permission levels]] are listed in the table next to the user/group name. +{{:rdms:solution:team_permissions_tab.png?direct&50|}} The middle button gives an overview of the current assigned permissions on the top-level of the Team Drive. The RDMS Groups that have permissions are also listed here. The currently set [[rdms:data:permissions|permission levels]] are listed in the table next to the user/group name. 
  
 {{ :rdms:solution:team_permissions_tab2.png?direct&900 |}} {{ :rdms:solution:team_permissions_tab2.png?direct&900 |}}
Line 91: Line 91:
 **Changing/revoking permissions of listed users and groups** **Changing/revoking permissions of listed users and groups**
  
-To change the permission level, just click on the pencil symbol next to the name of the user/group. This will open a new window where a new permission level can be selected. Also, permissions can be removed by selecting 'None' from the permission selection field. +To change the permission level, just click on the pencil symbol next to the name of the user/group. This will open a new window where a new permission level can be selected. Also, permissions can be removed by selecting "None" from the permission selection field. 
  
 {{ :rdms:solution:team_permission2.png?direct&400 |}} {{ :rdms:solution:team_permission2.png?direct&400 |}}
Line 111: Line 111:
 **Adding a new user as a Team Drive owner only** **Adding a new user as a Team Drive owner only**
  
-As a Team Drive owner without group admin privileges, you can still add new users and manage their permissions. To do this, you do not need to use the ''Data Management'' tab. Instead, follow the steps below:+As a Team Drive owner without group admin privileges, you can still add new users and manage their permissions. To do this, you do not need to use the "Data Management" tab. Instead, follow the steps below:
  
-1. Go to your Team Drive using the ''Team drives'' drop-down menu, then click the ''i'' icon in the top right corner of the dashboard. \\+1. Go to your Team Drive using the "Team drives" drop-down menu, then click the "i" icon in the top right corner of the dashboard. \\
  
 {{ :rdms:solution:step1_add_user.png?direct&800 |}} \\ {{ :rdms:solution:step1_add_user.png?direct&800 |}} \\
Line 133: Line 133:
 === Team Drive Data Tab === === Team Drive Data Tab ===
  
-{{:rdms:solution:team_data_tab.png?direct&50|}} The rightmost button gives an overview about the data that is currently stored on the Team Drive. From this overview,  it is also possible to do some basic tasks, like creating a new folder, moving a folder/file to another location, or uploading small files. +{{:rdms:solution:team_data_tab.png?direct&50|}} The rightmost button gives an overview of the data that is currently stored on the Team Drive. From this overview,  it is also possible to do some basic tasks, like creating a new folder, moving a folder/file to another location, or uploading small files. 
  
 {{ :rdms:solution:team_data_tab3.png?direct&900 |}} {{ :rdms:solution:team_data_tab3.png?direct&900 |}}
  
-Selecting first a file/folder and then pressing the ''i'' button results in a new menu which displays some information about the selected file/folder. Here, it is possible to see the currently set permissions on the respective data, see its metadata entries (if there are any), and it also gives the possibility to setup/remove a [[rdms:data:sharing|shared link]]. +Selecting first a file/folder and then pressing the ''i'' button results in a new menu which displays some information about the selected file/folder. Here, it is possible to see the currently set permissions on the respective data, see its metadata entries (if there are any), and it also gives the possibility to set up/remove a [[rdms:data:sharing|shared link]]. 
  
 ---- ----
Line 181: Line 181:
 **Advantages of using groups for permission management** **Advantages of using groups for permission management**
  
-As indicated earlier, it is possible to assign permissions either for individual users or also for RDMS Groups. Both ways of managing a Team Drive, either individual-based or group-based, can have their advantages. +As indicated earlier, it is possible to assign permissions either for individual users or for RDMS Groups. Both ways of managing a Team Drive, either individual-based or group-based, can have their advantages. 
  
   * Using RDMS Groups gives an additional layer of structure to the permission management.    * Using RDMS Groups gives an additional layer of structure to the permission management. 
   * Using RDMS Groups allows grouping users with different permissions. Permission changes can then be done in a single step.    * Using RDMS Groups allows grouping users with different permissions. Permission changes can then be done in a single step. 
-  * Grouping of users can be beneficial also for other parts of the RDMS if the person within a respective group needs access to another section of the RDMS. Instead of assigning permissions for everyone individually or creating a new group and adding the respective users, the already existing groups can be re-used. +  * Grouping of users can also be beneficial for other parts of the RDMS if the person within a respective group needs access to another section of the RDMS. Instead of assigning permissions for everyone individually or creating a new group and adding the respective users, the already existing groups can be reused. 
  
 It should be emphasised again that while a group is automatically created during Team Drive creation, it is **not mandatory** to use RDMS groups for the management of the drive.  It should be emphasised again that while a group is automatically created during Team Drive creation, it is **not mandatory** to use RDMS groups for the management of the drive. 
  
-If it is desired to manage the drive based on Groups, you can already specify this during the setup, and we will assign 'groupadmin' privileges for the respective user. This allows for managing the members of a RDMS group as well as giving the privilege to create new RDMS groups. +If it is desired to manage the drive based on Groups, you can already specify this during the setup, and we will assign 'groupadmin' privileges for the respective user. This allows for managing the members of an RDMS group as well as giving the privilege to create new RDMS groups. 
  
 If you are unsure if using RDMS Groups is suitable/beneficial for your use case, do not hesitate to get in contact with the RDMS support and we can further assist you. If you are unsure if using RDMS Groups is suitable/beneficial for your use case, do not hesitate to get in contact with the RDMS support and we can further assist you.
Line 195: Line 195:
 **An additional note for iCommands users** **An additional note for iCommands users**
  
-For those RDMS users that do not use the web interface to work in the system, but who rather work via the command-line interface (CLI) using ''iCommands'', it is also possible to do this management tasks from the CLI.  +For those RDMS users who do not use the web interface to work in the system, but who rather work via the command-line interface (CLI) using ''iCommands'', it is also possible to do these management tasks from the CLI.  
-Please refer to the [[rdms:access:linux:icommands|icommands]] wiki which provides some examples on specific commands that can be used for management tasks. Also refer to the [[https://docs.irods.org/4.3.0/|official iRODS documentation]] which also has a summary of the available commands. +Please refer to the [[rdms:access:linux:icommands|icommands]] wiki, which provides some examples on specific commands that can be used for management tasks. Also refer to the [[https://docs.irods.org/4.3.0/|official iRODS documentation]], which also has a summary of the available commands. 
  
 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 207: Line 207:
 ---- ----
  
-=== Creating of Team Drives as a Group Admin ===+=== Creating Team Drives as a Group Admin ===
  
-The 'groupadmin' role does not just allow for the management of RDMS Groups, but also makes the [[rdms:webapp:datamanagement|Data Management tab]] available in the web interface. +The "groupadmin" role does not just allow for the management of RDMS Groups, but also makes the [[rdms:webapp:datamanagement|Data Management tab]] available in the web interface. 
  
-To create a Team Drive as a 'groupadmin', first navigate to the Data Management tab, then select the ''+'' button to reveal the menu that allows you to create a new Team Drive by selecting 'New Team Drive'.+To create a Team Drive as a "groupadmin", first navigate to the Data Management tab, then select the "+" button to reveal the menu that allows you to create a new Team Drive by selecting 'New Team Drive'.
  
 {{ :rdms:solution:team_create_new3.png?direct&700 |}} {{ :rdms:solution:team_create_new3.png?direct&700 |}}
Line 260: Line 260:
 **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: **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 user's personal home location, for example ''/rug/home/''.+Using the WebDAV protocol in Cyberduck always opens the location above the user's personal home location, for example, ''/rug/home/''.
  
 From there, other locations like Team Drives can be accessed directly.  From there, other locations like Team Drives can be accessed directly.