From a9f8378387bd77bbb1a63e72b15ccd89cdae2e05 Mon Sep 17 00:00:00 2001 From: Sebastian Larsen Prehn Date: Fri, 23 May 2025 11:15:47 +0200 Subject: [PATCH 1/2] Add schedule tasks --- docs/index.rst | 1 + docs/sections/erda/scheduletask/index.rst | 12 ++++++++++++ 2 files changed, 13 insertions(+) create mode 100644 docs/sections/erda/scheduletask/index.rst diff --git a/docs/index.rst b/docs/index.rst index 95c046e..8808d90 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -26,6 +26,7 @@ ERDA/SIF: User Guides sections/erda/networkdrive/index sections/erda/seafile/index sections/erda/archiving/index + sections/erda/scheduletask/index .. toctree:: :maxdepth: 2 diff --git a/docs/sections/erda/scheduletask/index.rst b/docs/sections/erda/scheduletask/index.rst new file mode 100644 index 0000000..d640453 --- /dev/null +++ b/docs/sections/erda/scheduletask/index.rst @@ -0,0 +1,12 @@ +.. _erda-scheduletask-start: + +Schedule Tasks +============== + +It is possible to have ERDA do a number of tasks on your behalf with the **Schedule Tasks** functionality. +The corresponding navigation menu entry is not shown by default to keep it simple, but you can **Add** it to your home page, which you can read more about on `. + +On the **Schedule Tasks** page you can schedule one-time or regularly repeat tasks, such as inserting a task to create a new backup archive every day with the contents of some folder on ERDA. + +You can follow scheduled runs in the **View Logs** tab. +You can also read more about the automatic variables and available commands at the bottom of the **Manage Tasks** tab on the **Schedule Tasks** page. From af685e0a951e20bfb810786574c42a81b568358b Mon Sep 17 00:00:00 2001 From: Sebastian Larsen Prehn Date: Mon, 26 May 2025 10:59:10 +0200 Subject: [PATCH 2/2] Add initial data import / export --- docs/index.rst | 1 + docs/sections/erda/dataimportexport/index.rst | 35 +++++++++++++++++++ 2 files changed, 36 insertions(+) create mode 100644 docs/sections/erda/dataimportexport/index.rst diff --git a/docs/index.rst b/docs/index.rst index 8808d90..9693ceb 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -27,6 +27,7 @@ ERDA/SIF: User Guides sections/erda/seafile/index sections/erda/archiving/index sections/erda/scheduletask/index + sections/erda/dataimportexport/index .. toctree:: :maxdepth: 2 diff --git a/docs/sections/erda/dataimportexport/index.rst b/docs/sections/erda/dataimportexport/index.rst new file mode 100644 index 0000000..be22ead --- /dev/null +++ b/docs/sections/erda/dataimportexport/index.rst @@ -0,0 +1,35 @@ +.. _erda-dataimpexp-start: + +Data Import/Export +================== + +We offer the ability to import and export data from ERDA in an efficient way. +Typical scenarios include fetching big data sets from dedicated Linux/UNIX servers or from imaging sites, where data are recorded on-site with remote access afterwards. +This is probably mostly relevant for users with a certain experience in handling big data sets. + +ERDA comes with low-level background import and export of data through different efficient transfer protocols like SFTP/FTPS/RSYNC/HTTPS and WebDAVS. + +From the **Files** page you can right-click in the file manager and in the menu under *Data Transfers* you can find *Import* and *Export*. + +There is also the dedicated page. The corresponding navigation menu entry is not shown by default to keep it simple, but you can **Add** it to your home page, which you can read more about on `_. + +On the **Data Transfers** page you can create an external data transfer and either import or export data via a handy form. + + +.. _erda-dataimpexp-transfer: + +External Data Transfer +---------------------- + +Select whether you want to import or export data via **Action**, and (optionally) give it a transfer ID / name to recognize it by. + +Select **Protocol**, and specify **Host and port**. + +Choose your **Login method** and specify the **Source path(s)**, clicking on the button *Add another source field* in case you have several **source paths**. + +Add **Destination path** and **Exclude path(s)**. + +If you transfer from a slow site, you should set **Enable compression**, and otherwise make sure it is unset. + +You can specify your mail for a notification on completion, and then click **Request transfer**. +