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 [2023/07/03 10:48]
jelte Added section about inheritance 		rdms:solution:team [2024/04/04 11:54] (current)
jelte spell correction: native --> native
Line 4: Line 4:
 {{ :rdms:solution:rdms_locations_concept_team.png?800 |}} {{ :rdms:solution:rdms_locations_concept_team.png?800 |}}
  
-===== General Concept of 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 summarize some of the basics of Team Drives in the RDMS:
Line 12: Line 12:
   * 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 a RDMS Team Drive can be shared with other group members, but also other RDMS users.
 +  * [[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 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 (new users, permissions management) is in the hand 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 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. 
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 <rdms-support@rug.nl> or <dcc@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 are needed:
Line 27: Line 28:
   - **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 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>''.
   - **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 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.
-  - **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 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 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.
  
 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 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. 
  
-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 the initial request of the RDMS 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). 
- +
-Managing on a group level needs additional 'groupadmin' privileges that have to be granted to the managing person.  +
-Of course, it is also at a later stage always possible to add these privileges if it is desired to work with RDMS groups.  +
  
 ===== Working with Team Drives ===== ===== Working with Team Drives =====
Line 177: 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 ''iCommands'', it is also possible to do this management tasks from the CLI.  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 ''iCommands'', it is also possible to do this management tasks from the CLI. 
-Please refer to the [[rdms:access:linux:createprofile|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 184: Line 182:
   * ''ichmod'': Allows to modify permissions for files/folders.   * ''ichmod'': Allows to modify permissions for files/folders.
   * ''igroupadmin'': Command to manage groups from the CLI.    * ''igroupadmin'': Command to manage groups from the CLI. 
 +
 +
 +----
 +
 +=== Additional Info: Creation of Team Drives by the User ===
 +
 +If you have requested a Team Drive, your account gets promoted to 'groupadmin' level within the RDMS. This 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'.
 +
 +{{ :rdms:solution:team_create_new3.png?700 |}}
 +
 +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. 
  
 ++++ ++++
Line 203: Line 214:
 {{ :rdms:solution:tdms_team_user1.png?800 |}} {{ :rdms:solution:tdms_team_user1.png?800 |}}
  
-Afterwards, basic tasks can be performed directly in the web interface, for example the creation of new folders or uploading of small files (<32 MB). +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, if the correct location of the respective Team Drive is known, in our example ''/rug/home/Example_Team1'', it is also possible to copy this location to the address bar in the web portal, and confirm by pressing 'Enter' to reach the Team Drive.  Alternatively, if the correct location of the respective Team Drive is known, in our example ''/rug/home/Example_Team1'', it is also possible to copy this location to the address bar in the web portal, and confirm by pressing 'Enter' to reach the Team Drive. 
Line 214: Line 225:
 When using Cyberduck as an example for a GUI client for the RDMS, the Team Drive locations can be accessed in the following way: 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 **nativ iRODS protocol for Cyberduck** and when no special configuration are made in Cyberduck, you will see your personal Home location after login (e.g. ''/rug/home/<mailadress>''). +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. ''/rug/home/<mailadress>''). 
  
 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.  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.