Extended Data Protection by Suppressing xAPI-Statements

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ.

1 Initial Problem

Many applications created with the help of popular authoring tools would often like to store a lot of data in an LRS. This would not be allowed by the current jurisdiction without distinguishing the purpose of usage.

2 Conceptual Summary

Depending on the intended use (testing, self-assessment, etc.), statement sets, that regulate the data transfer from the ILIAS xAPI proxy to the LRS, should be developed and supplemented. For example, the tracking of individual edits of tasks would suppressed if it were a mere self-assessment. If necessary, the same object would then enable this tracking during an audit.
It is also necessary to check the concept on which data is required for the proper program sequence.

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

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:  Kohnle, Uwe [ukohnle]
• Maintainer: Kohnle, Uwe [ukohnle]
• Implementation of the feature is done by: Kohnle, Uwe [ukohnle]

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}.