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:multizone [2025/01/24 14:41] – burcurdms:solution:multizone [2025/03/24 08:00] (current) – burcu
Line 1: Line 1:
-{{indexmenu_n>3}}  
 ====== Different Zones ====== ====== Different Zones ======
  
Line 23: Line 22:
 ===== How to access Sensitive Data Zone?==== ===== How to access Sensitive Data Zone?====
  
-1) Contact [[rdms-support@rug.nl|rdms-support@rug.nl]]. You will receive a request form where you will be asked to provide the following information:+1) Contact [[rdms-support@rug.nl|rdms-support@rug.nl]]. Keep in mind that only research group leaders, supervisors or PIs can make the initial request. You will receive a request form where you will be asked to provide the following information:
 <hidden Click to display request form><code> <hidden Click to display request form><code>
 Faculty name: Faculty name:
Line 35: Line 34:
 * An administrator is the person who is responsible of the management of the whole Team Drive. The administrator is responsible of giving others permissions and roles to access data, as well as revoking their permissions and roles.  * An administrator is the person who is responsible of the management of the whole Team Drive. The administrator is responsible of giving others permissions and roles to access data, as well as revoking their permissions and roles. 
  
-** A RDMS Team Drive is a group environment where the administrator has  total control of its management. Research data from different projects are  organized and stored in a RDMS Team Drive. If the applicant is an administrator, they can propose a name for a Team Drive. If the applicant is  not an administrator, they should learn the name of the Team Drive from their  administrator(s). +** A RDMS Team Drive is a group environment where the administrator has total control of its management. Research data from different projects are organized and stored in a RDMS Team Drive. If the applicant requesting a new Team Drive is going to be its administrator, they can propose a name for the Team Drive when it is created. If the applicant is not an administrator, they should ask the designated Team Drive administrator(s) to provide a name for the new Team Drive. 
 </code></hidden> </code></hidden>
 \\ \\
  
 2) If everything is in order with your request form, you will receive an email from us outlining  the terms and conditions for archiving research data in the SD zone of the RDMS, as well as the date you can access the RDMS SD zone. By receiving this email, you confirm that you have read and accepted these terms and conditions required for using the RDMS SD zone. 2) If everything is in order with your request form, you will receive an email from us outlining  the terms and conditions for archiving research data in the SD zone of the RDMS, as well as the date you can access the RDMS SD zone. By receiving this email, you confirm that you have read and accepted these terms and conditions required for using the RDMS SD zone.
 +
 +Other project members should individually contact [[rdms-support@rug.nl|rdms-support@rug.nl]] to ask for the initial access to the Team Drive requested by their supervisors. 
 <hidden Click to display Terms & Conditions required for using the RDMS SD zone><code> <hidden Click to display Terms & Conditions required for using the RDMS SD zone><code>
 Rules for Data Storage: Rules for Data Storage:
Line 45: Line 46:
    * Folder and file names must not contain sensitive information.    * Folder and file names must not contain sensitive information.
    * Metadata keywords must not contain sensitive information.    * Metadata keywords must not contain sensitive information.
-   * No user except the administrator can retrieve data from the sensitive data zone without the permission of the administrator(s).+   * Users should request permission from the administrator before they retrieve data from the sensitive data zone. 
  
 Rules for Data Sharing and Access: Rules for Data Sharing and Access:
Line 58: Line 59:
 \\ \\
  
-3) Accessing the RDMS SD zone and transferring data. Similar to the Default zone, you can access the RDMS SD zone via the web interface and ''iCommands''. To transfer data, you can continue to use Cyberduck and ''iCommands''; you simply need to configure the profiles accordingly. Check the [[https://wiki.hpc.rug.nl/rdms/access/windows/cyberduck|Cyberduck]] and [[https://wiki.hpc.rug.nl/rdms/access/linux/icommands|icommands]] subsections in this wiki for instructions on setting up the profiles.+3) Accessing the RDMS SD zone and transferring data is similar to the Default zone. You can access the RDMS SD zone via the [[https://wiki.hpc.rug.nl/rdms/webapp|web interface]] and ''iCommands''. To transfer data, you can continue to use Cyberduck and ''iCommands''; you simply need to configure the profiles accordingly. Check the [[https://wiki.hpc.rug.nl/rdms/access/windows/cyberduck|Cyberduck]] and [[https://wiki.hpc.rug.nl/rdms/access/linux/icommands|icommands]] subsections in this wiki for instructions on setting up the profiles.
  
 ===== How to switch between zones and recognize the zone you are working in?==== ===== How to switch between zones and recognize the zone you are working in?====
Line 67: Line 68:
 {{ :rdms:solution:switch_zone2.png}} {{ :rdms:solution:switch_zone2.png}}
  
 +\\
  
 When you click on the RUG icon, the name of the zone you are working in will appear on the right side of the banner. Additionally, there is a slight difference in the colour scheme between the two zones, with the Sensitive Data Zone featuring a menu with a darker colour on the left side of the web interface. When you click on the RUG icon, the name of the zone you are working in will appear on the right side of the banner. Additionally, there is a slight difference in the colour scheme between the two zones, with the Sensitive Data Zone featuring a menu with a darker colour on the left side of the web interface.
 +
 +\\
  
 {{ :rdms:solution:banner_top_sd2.png}} {{ :rdms:solution:banner_top_sd2.png}}