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:access:linux:icommands [2025/04/07 13:47] – Added how to restore deleted files giuliordms:access:linux:icommands [2025/07/03 11:48] (current) – [Common iCommands Usage Examples] Note about ibun and symlinks jelte
Line 56: Line 56:
     "irods_port": 1247,     "irods_port": 1247,
     "irods_ssl_verify_server": "cert",     "irods_ssl_verify_server": "cert",
-    "irods_user_name": "<emailadress>,+    "irods_user_name": "<emailadress>",
     "irods_zone_name": "sdrugZone"     "irods_zone_name": "sdrugZone"
 } }
Line 250: Line 250:
 For the explanation of commonly used ''iCommands'', we will split the ''iCommands'' into three different sections: For the explanation of commonly used ''iCommands'', we will split the ''iCommands'' into three different sections:
  
-  - **iCommands for Navigation** will describe the iCommands that are used to navigate the RDMS from the CLI, but also contain information about starting/ending of the connection.+  - **iCommands for Navigation** will describe the ''iCommands'' that are used to navigate the RDMS from the CLI, but also contain information about starting/ending of the connection.
   - **iCommands for (Meta)data Management** will describe how to transfer data in/out of the RDMS, explain how to set permissions for other users, how to work with metadata from the CLI, including a more detailed description on how to query the database for more extensive searches.   - **iCommands for (Meta)data Management** will describe how to transfer data in/out of the RDMS, explain how to set permissions for other users, how to work with metadata from the CLI, including a more detailed description on how to query the database for more extensive searches.
   -  **iCommands for Group Management** will focus on the respective commands that can be used by 'groupadmins' to manage RDMS groups from the CLI. As this section is not relevant for all users, it will be discussed separately.    -  **iCommands for Group Management** will focus on the respective commands that can be used by 'groupadmins' to manage RDMS groups from the CLI. As this section is not relevant for all users, it will be discussed separately. 
Line 644: Line 644:
   * The bundling and extraction operations do not display a progress. For large folders/archives, it might take a longer time to finish while your terminal seems to be stuck.   * The bundling and extraction operations do not display a progress. For large folders/archives, it might take a longer time to finish while your terminal seems to be stuck.
   * If you want to overwrite, you can again use the additional ''-f'' flag.   * If you want to overwrite, you can again use the additional ''-f'' flag.
 +  * Notes that extraction via ''ibun -x'' will fail if your archive contains symlinks as they are not supported by ''ibun'' (also see info in the [[rdms:bestpractices|Best Practices]] section). 
  
 **Assigning Data Permission**\\ **Assigning Data Permission**\\
Line 692: Line 693:
  
 **How to manage files in the RDMS trash folder**\\ **How to manage files in the RDMS trash folder**\\
-Files that have been deleted either from the web interface or using ''irm'' are not permanently removed from the system, but are stored in the ''trash'' folder of the RDMS. Should you wish to empty your ''trash'' folder, you can simply run the ''irmtrash'' command without any further parameter.+Files that have been deleted either via the web interface or using  the command ''irm'' are not permanently removed from the system, but are stored in the ''trash'' folder of the RDMS. Should you wish to empty your ''trash'' folder, you can simply run the ''irmtrash'' command without any further parameter.
  
-If instead you wish to restore files in the ''trash'' folder, you can do so by running these lines in iCommands:+If you wish to restore files in the ''trash'' folder using ''iCommands'', you can do so by running the following commands:
 <hidden> <hidden>
 <code> <code>
-#Locate a file in the trash folder. You will need to know the filename for this to work. +#To locate a file in the trash folder, you will need to know the filename: 
-$ ilocate -t <filename>  # -t for search in trash+$ ilocate -t <filename>  
  
-#Copy the path given by ilocate, then run either of the suggested commands. +# where the -t switch indicates to search in trash. Copy the path given by ilocate, then run any of the suggested commands. 
-$ imv <logical path(s) from ilocate> <logical path to destination folder> #This command will move the file out of the trash folder + 
-#or +# To move the file out of the trash folder (and preserve previously attached metadata): 
-$ icp <logical path(s) from ilocate> <logical path to destination folder> #This command will leave a copy of the restored file in the trash folder +$ imv <logical path(s) from ilocate> <path to RDMS destination folder> 
-#or + 
-$ iget <logical path(s) from ilocate> <logical path to destination folder> #This command will download the file to a folder in your local system+# To restore a copy of the file present in the trash folder (without previously attached metadata): 
 +$ icp <logical path(s) from ilocate> <path to RDMS destination folder> 
 + 
 +# To download a copy of the file to a folder on your local system (without previously attached metadata): 
 +$ iget <logical path(s) from ilocate> <path to local destination folder>
  
 </code> </code>