User: Import users in background tasks

1 Initial Problem

ILIAS allows modifications of user accounts in large bulk sets via XML-imports. These imports are handled as regular web requests and can take quite some time.

The problems at hand are:

• no feedback on progress
• risk of browser-timeout and loss of execution results
• risk of server-timeout and corrupted data

• dry-run: After validation, the user has to confirm the import and can set some final settings. The dry-run is much faster than the hot-run, but can take some time too with large data sets. Roughly 10x as fast, or more.
• hot-run: All changes happen in the hot-run.

2 Conceptual Summary

Execute user imports as background tasks with feedback.

To be precise: Only the hot-run will be executed as background-task, while the dry-run will stay a synchronuous web request as it is.

Note: A risk remains to hit the memory limit - also the dry-run could timeout itself.

3 User Interface Modifications

3.1 List of Affected Views

Administration > User Management

3.2 User Interface Details

On User Import: Immediate feedback that the task has started. All further feedback will be provided by the background task itself.

3.3 New User Interface Concepts

-

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Kiegel, Colin [kiegel]
• Maintainer: Meyer, Stefan [smeyer] (2nd: Killing, Alexander [alex] and Jansen, Michael [mjansen])
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.