Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
rdms:best [2024/03/25 12:06] jelte Added a little bit text at the start. |
rdms:best [2024/03/28 15:22] (current) burcu [Best Practices] |
||
---|---|---|---|
Line 1: | Line 1: | ||
{{indexmenu_n> | {{indexmenu_n> | ||
====== Best Practices ====== | ====== Best Practices ====== | ||
- | This section | + | This section |
- | The section will be gradually | + | The section will be gradually |
- | If you feel that an important information should be added to this section, | + | If you believe |
- | ===== Data Naming ===== | + | ===== Naming |
For the optimal usage of the RDMS, it is highly recommended to follow these best practices for naming your files/ | For the optimal usage of the RDMS, it is highly recommended to follow these best practices for naming your files/ | ||
Line 16: | Line 16: | ||
* Prefer usage of underscore ('' | * Prefer usage of underscore ('' | ||
- | Example of a folder structure with good naming: | + | Example of a folder structure with correct |
< | < | ||
$ itree project_name | $ itree project_name | ||
Line 37: | Line 37: | ||
</ | </ | ||
- | Example of a folder structure with wrong/ | + | Example of a folder structure with incorrect |
< | < | ||
$ itree " | $ itree " | ||
Line 58: | Line 58: | ||
</ | </ | ||
- | ===== Detecting Corrupt | + | ===== Bundling of Data Sets ===== |
+ | |||
+ | To improve the performance of the RDMS, it is recommended to store data sets numerous small files in a structured format like '' | ||
+ | |||
+ | Best practices to handle such cases are: | ||
+ | |||
+ | - Fist, collect all data locally. | ||
+ | - Before archiving in the RDMS, bundle the data set or its subsets into a structured data format (as mentioned above). | ||
+ | - Upload the bundled format to the RDMS. | ||
+ | - (Optional) Add metadata if desired. | ||
+ | - (Optional) Unbundle the data on the RDMS.) | ||
+ | |||
+ | For extraction on the RDMS, CLI users can use the '' | ||
+ | |||
+ | For RDMS web interface users, the " | ||
+ | |||
+ | ===== Locked | ||
+ | |||
+ | In rare cases, data may arrive in an incomplete form in the RDMS. This usually happens if a data transfer abruptly interrupted, | ||
+ | |||
+ | Restarting the data transfer may solve this issue. However, it is possible that the already transferred data remains in a locked state, causing problems when the transfer is restarted as those files cannot be overwritten directly. | ||
+ | |||
+ | If you experience these issues, it is recommended to contact [[rdms-support@rug.nl|RDMS-Support]]. | ||
+ | |||
+ | Users of the command-line tool [[rdms: | ||
+ | |||
+ | In general, these issues manifest in '' | ||
+ | |||
+ | To check all files at a RDMS location ''/ | ||
+ | |||
+ | < | ||
+ | $ iquest " | ||
+ | </ | ||
+ | |||
+ | These command will check the specified location for files which have a replica status of 2 (" | ||
+ | |||
+ | < | ||
+ | status: < | ||
+ | </ | ||
+ | |||
+ | ==== Removal of Locked Files ==== | ||
+ | |||
+ | While the locked files cannot be directly removed, they can still be moved first to another location in your home/team location, for example as a separate folder for locked files. Afterwards, the data transfer can be restarted. | ||
+ | |||
+ | Best practices to handle locked files and resolve the '' | ||
+ | |||
+ | - Create a new folder in your home or team drive to contain all locked files. | ||
+ | - Use the ' | ||
+ | - Restart the data transfer. The '' | ||
+ | - If you accumulated multiple locked files in your folder which you cannot delete, please contact [[rdms-support@rug.nl|RDMS-Support]] and we will help you remove these. | ||
+ | |||
+ | **Note:** It is recommended not to contact RDMS support for every locked file, but instead first try to resolve it as described above. However, if numerous locked files are detected, you can directly contact RDMS support. |