Differences

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

--- rdms:solution:team [2023/08/10 10:01] – [General Concept of RDMS Team Drives] burcu
+++ rdms:solution:team [2024/12/17 15:25] (current) – burcu
@@ Line 1: / Line 1: @@
-{{indexmenu_n>3}}
+{{indexmenu_n>4}}
 ====== Team Drives ======
-{{ :rdms:solution:rdms_locations_concept_team.png?800 |}}
+{{ :rdms:solution:rdms_locations_concept_team.png?direct&800 |}}
 ===== General Concepts of the RDMS Team Drives =====
 The following points summarize some of the basics of Team Drives in the RDMS:
-  * 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,  //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.
   * 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 ''/<zone>/home/<Team_Name>''.
   * 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 management of Team Drives (new users, permissions management) is in the hand of the research groups themselves.
@@ 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>''.
   - **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.
@@ Line 51: / Line 52: @@
 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?300 |}}
+{{ :rdms:solution:team_drive1.png?direct&300 |}}
 Clicking on the name of one of the available RDMS Team Drives, opens the management tab of the respective Team Drive. On this page, diverse management tasks can be performed by the owner/manager of the Team Drive.
-{{ :rdms:solution:team_drive2.png?900 |}}
+{{ :rdms:solution:team_drive2.png?direct&900 |}}
@@ Line 63: / Line 64: @@
 === Group Users Management Tab (Manage RDMS Team Drive Group Members) ===
-{{:rdms:solution:team_group_tab.png?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 about the current members of the RDMS Group that is automatically created and added to a Team Drive when it is setup.
@@ Line 70: / Line 71: @@
 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?600 |}}
+{{ :rdms:solution:team_add_group_merged.png?direct&600 |}}
 **Removing Group Members**
@@ Line 78: / Line 79: @@
 **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.
-{{ :rdms:solution:team_group3.png?1000 |}}
+{{ :rdms:solution:team_group3.png?direct&1000 |}}
 === Team Drive Permissions Tab ===
-{{:rdms:solution:team_permissions_tab.png?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 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_tab2.png?900 |}}
+{{ :rdms:solution:team_permissions_tab2.png?direct&900 |}}
 **Changing/Revoking Permissions of listed Users/Groups**
@@ Line 91: / Line 92: @@
 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 select. Also permissions can be removed by selecting 'None' from the permission selection field.
-{{ :rdms:solution:team_permission2.png?400 |}}
+{{ :rdms:solution:team_permission2.png?direct&400 |}}
 When adjusting the permissions, there is an additional selection possibility which decides if the permission change should apply for all files/folders within the Team Drive (select 'Including sub files and folder') or just for the top-level of the Team Drive (select 'Only this file/folder').
@@ Line 111: / Line 112: @@
 === Team Drive Data Tab ===
-{{:rdms:solution:team_data_tab.png?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 creation of a new folder, moving of a folder/file to another location, uploading of small files.
+{{: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 creation of a new folder, moving of a folder/file to another location, uploading of small files.
-{{ :rdms:solution:team_data_tab3.png?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]].
@@ Line 135: / Line 136: @@
 For this, the respective file/folder has to be selected from the data tab. Subsequently, pressing the ''i'' button while the file/folder are selected will open a new menu which also contains a 'Members' tab which lists all the currently set permissions for that file/folder.
-{{ :rdms:solution:team_permission3.png?600 |}}
+{{ :rdms:solution:team_permission3.png?direct&600 |}}
 **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/folders in the Team Drive.
@@ Line 147: / Line 148: @@
 It is furthermore possible to enable/disable [[rdms:data:permissions|permission inheritance]] for the whole Team Drive or its sub-folders. If a Team Drive is created, the standard setting will create it with permission inheritance 'false' (inheritance disabled) which means that a newly created sub-folder or file within the Team Drive's main folder will not inherit the permissions that were assigned on the main folder.
-{{ :rdms:solution:team_inheritance1.png?800 |}}
+{{ :rdms:solution:team_inheritance1.png?direct&800 |}}
 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 ''i'' button to reveal the information window.
@@ Line 153: / Line 154: @@
 From there, you can access a context menu that allows you to select 'Set permission inheritance'.
-{{ :rdms:solution:team_inheritance2.png?800 |}}
+{{ :rdms:solution:team_inheritance2.png?direct&800 |}}
 Please read the section about [[rdms:data:permissions|permissions]] which also contains a more detailed explanation about permission inheritance in general.
@@ Line 174: / 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.
-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:
@@ Line 191: / Line 192: @@
 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 |}}
+{{ :rdms:solution:team_create_new3.png?direct&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 211: / Line 212: @@
 From the web portal, available Team Drives are listed in the [[rdms:webapp:databrowser|Data Browser]] tab. Clicking on the name of one of the listed Team Drives will open it.
-{{ :rdms:solution:tdms_team_user1.png?800 |}}
+{{ :rdms:solution:tdms_team_user1.png?direct&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.
-{{ :rdms:solution:rdms_team_user2.png?800 |}}
+{{ :rdms:solution:rdms_team_user2.png?direct&800 |}}
@@ Line 224: / 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:
-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.
-{{ :rdms:solution:rdms_team_cyberduck2.png?700 |}}
+{{ :rdms:solution:rdms_team_cyberduck2.png?direct&700 |}}
 In the higher level, in this example ''/rug/home/'', all of your available location, including Team Drives will be available. Just click on a folder to access/open it. Afterwards, file management tasks like up-/download (see below) can be performed.
-{{ :rdms:solution:rdms_team_cyberduck3.png?700 |}}
+{{ :rdms:solution:rdms_team_cyberduck3.png?direct&700 |}}
 For Cyberduck on Windows, it is also again possible to directly specify the full location to reach a Team Drive.