TAC: Customizing Metadata of Export File for TestArchiveCreator

1 Initial Problem

When creating an archive export, the export, which is often executed via a cron job at odd times, appears in the Export tab of a test. The name of this export file is typically cryptic and unique, much like many other ILIAS export files. This poses a problem for individuals responsible for performing multiple archive exports and storing them in another system. They have to locate these files in different places and they are not easily distinguishable. Additionally, since the exports are executed at unknown times, the individual triggering the exports does not know when they will be available for retrieval.

2 Conceptual Summary

To facilitate more convenient archiving processes, we propose the following enhancements:

b) Allow the user that set the archive to be created to receive a notification via internal mail system upon completion of the export file. This should be an optional e-mail. In the admin interface it should be possible to activiate this functionality globally (default off). If globally activated the GUI should automatically fill in the current users loginname to the address field. The current user then can decide and add additional loginnames to the field or remove his/her own. The mail notification must include a permalink to the test-object. If several exports are triggered by one user all links should be combined in one e-mail to reduce a possible flood of e-mails.

c) Provide a prefilled time of export execution that indicates when the export will be created (might be not necessary if users are informed via mail).

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

3.2.1 Plugin Configuration (Mockup)

(the image above shows plugin-configuration in admin area)

3.2.2 Edit Form for Archive Settings (Mockup)

(the image above shows the setting to the archive creator, visible and adjustable by users with access to TAC)

The text for the notification send via ILIAS internal mail service is stored in a language variable. The proposed standard text reads:

3.2.3 Mail-Templates

3.3 New User Interface Concepts

3.4 Accessibility Implications

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 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

8 Funding

9 Discussion

10 Implementation

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

Test Cases

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.