| Both sides previous revision Previous revision Next revision | Previous revision |
| rdms:access:linux:icommands [2026/08/28 07:45] – removed reference to ibun extraction giulio | rdms:access:linux:icommands [2026/11/15 19:56] (current) – [iCommands] admin |
|---|
| * ''iCommands'' consist of a whole set of different commands that allow interaction with the RDMS from the CLI. Next to [[https://docs.irods.org/4.3.0/icommands/user/|commands relevant to general users]] (navigation, data transfer, etc.), it has [[https://docs.irods.org/4.3.0/icommands/metadata/|commands specifically for metadata]], and [[https://docs.irods.org/4.3.0/icommands/groupadmin/|commands for management of groups]]. | * ''iCommands'' consist of a whole set of different commands that allow interaction with the RDMS from the CLI. Next to [[https://docs.irods.org/4.3.0/icommands/user/|commands relevant to general users]] (navigation, data transfer, etc.), it has [[https://docs.irods.org/4.3.0/icommands/metadata/|commands specifically for metadata]], and [[https://docs.irods.org/4.3.0/icommands/groupadmin/|commands for management of groups]]. |
| * ''iCommands'' are already installed on the LWP and Habrók HPC cluster. In these environments, you just need to: | * ''iCommands'' are already installed on the LWP and Habrók HPC cluster. In these environments, you just need to: |
| - Create a ''~\.irods'' directory in your home directory. | - Create a ''~/.irods'' directory in your home directory. |
| - Create an ''irods_environment.json'' file in that directory. | - Create an ''irods_environment.json'' file in that directory. |
| * For other Linux distributions, instructions to install ''iCommands'' are also explained in this section. | * For other Linux distributions, instructions to install ''iCommands'' are also explained in this section. |
| |
| **Notes:** | **Notes:** |
| * The unbundling functionality of ''ibun'' has been **disabled** due to a security issue. | * The unbundling functionality of ''ibun -x'' has been **disabled** due to a security issue. |
| * The bundling operations do not display progress. For large folders/archives, it might take a longer time to finish, while your terminal seems to be stuck. | * The bundling operations do not display progress. For large folders/archives, it might take 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. |
| |
| The ''iCommands'' can also be used to add metadata to a file/folder, list already existing metadata, modify existing metadata, and also query (search) for objects that contain certain metadata. | The ''iCommands'' can also be used to add metadata to a file/folder, list already existing metadata, modify existing metadata, and also query (search) for objects that contain certain metadata. |
| |
| Within the RDMS, metadata is always added as so-called 'attribute-value-units' triples, AVUs. The 'attribute' specifies the metadata key (e.g., 'Author') while the 'value' specifies the corresponding value for this key (e.g., 'John Doe'). The 'unit' entry is optional, but can be useful in cases where the entries could be otherwise ambiguous (e.g., A: 'Distance:, V: '100', U: 'km'). This can be left blank if no unit is desired. | Within the RDMS, metadata is always added as so-called 'attribute-value-units' triples, AVUs. The 'attribute' specifies the metadata key (e.g., 'Author') while the 'value' specifies the corresponding value for this key (e.g., 'John Doe'). The 'unit' entry is optional, but can be useful in cases where the entries could be otherwise ambiguous (e.g., A: 'Distance ', V: '100', U: 'km'). This can be left blank if no unit is desired. |
| |
| The command that is used to work with metadata from the CLI is the ''imeta'' command, which has additional subcommands depending on the desired operation : | The command that is used to work with metadata from the CLI is the ''imeta'' command, which has additional subcommands depending on the desired operation : |
| **Notes:** | **Notes:** |
| * The ''imeta'' command requires that you also specify the additional ''-C'' or ''-d'' flag. | * The ''imeta'' command requires that you also specify the additional ''-C'' or ''-d'' flag. |
| * Use ''-C'' if you want to work with a folder (collection). For example ''imeta ls -C <foldername>''. | * Use ''-C'' if you want to work with a folder (collection). For example, ''imeta ls -C <foldername>''. |
| * Use ''-d'' if you want to work with a file (data object). For example ''imeta ls -d <filename>''. | * Use ''-d'' if you want to work with a file (data object). For example, ''imeta ls -d <filename>''. |
| * There are additional help pages available for the different ''imeta'' subcommands, which can be displayed by executing ''imeta help <subcommand>''. For example: ''imeta help qu'' to display more information about the query (search) command. | * There are additional help pages available for the different ''imeta'' subcommands, which can be displayed by executing ''imeta help <subcommand>''. For example: ''imeta help qu'' to display more information about the query (search) command. |
| |