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:webapp:processes [2025/09/23 13:47] – some small text changes jelterdms:webapp:processes [2026/05/21 13:08] (current) – burcu
Line 1: Line 1:
 +{{indexmenu_n>6}}
 ====== Processes and Jobs ====== ====== Processes and Jobs ======
-{{indexmenu_n>5}} 
  
 The RDMS web interface allows you to observe the status of the processes/jobs that you started via the web interface. For that, you can use the "Processes/jobs" view on the left-side Menu bar. Moreover, this view allows you to observe the status of your **delayed rules**, a concept that will be explained in this section as well. The RDMS web interface allows you to observe the status of the processes/jobs that you started via the web interface. For that, you can use the "Processes/jobs" view on the left-side Menu bar. Moreover, this view allows you to observe the status of your **delayed rules**, a concept that will be explained in this section as well.
Line 26: Line 26:
 ===== Delayed Rules ===== ===== Delayed Rules =====
  
-The RDMS is built on top of the data management software [[https://irods.org/|iRODS]]. The iRODS system has the built-in capability to execute certain tasks when a certain event is registered in the system. These automated tasks are called **rules** and they can be delayed, meaning being queued and executed in the background even if the user is not logged in anymore.  +The RDMS is built on top of the data management software [[https://irods.org/|iRODS]]. The iRODS system has the built-in capability to execute certain tasks when a certain event is registered in the system. These automated tasks are called **rules**, and they can be delayed, meaning being queued and executed in the background even if the user is not logged in anymore.  
  
 We use rules in several places in the RDMS, often as delayed rules. Important examples of delayed rules are: We use rules in several places in the RDMS, often as delayed rules. Important examples of delayed rules are:
  
   * **Automated checksum calculations of your data**: If you upload files to the RDMS, an automated checksum calculation for your files will be executed as a delayed rule. This guarantees that all your files have a checksum registered, which gives you and us the capability to check the [[rdms:data:integrity|integrity of your data]].   * **Automated checksum calculations of your data**: If you upload files to the RDMS, an automated checksum calculation for your files will be executed as a delayed rule. This guarantees that all your files have a checksum registered, which gives you and us the capability to check the [[rdms:data:integrity|integrity of your data]].
-  * **Bundling/Unbundling via the web interface**: If you use the function to compress a folder to a tar archive or to decompress a archive, it will also be executed as a delayed rule.+  * **Bundling/Unbundling via the web interface**: If you use the function to compress a folder to a tar archive or to decompress an archive, it will also be executed as a delayed rule.
  
 You can observe the status of your rules via the second tab in the processes/jobs view.  You can observe the status of your rules via the second tab in the processes/jobs view.