Test: Revise Notifications

1 Initial Problem

Currently, the Notifications in Test are really messed up. There is no concept for not user finished tests. Also, only the owner of a test could be notified. With the Test: Abandon Notifications, we remove the old instable code to shape the T&A code base.

With this feature request, we propose to introduce a new Notification implementation, which does not lack the problems of the old implementation.

2 Conceptual Summary

Test creators / lecturers / tutors want to know if participants have finished a test pass. In some cases to give manual feedback, in other cases to score some question types. In further cases, to transmit the results to the Examination Office.

But they do not want to sit before the test participant tab or the result page and check the status of every participant regular. So, we send a notification after a user has finished a test attempt. We recognize the following types of test endings:
 

We want not only the test owner to receive the notification, but to be able to determine who receives it. The notification function will only be available to users with the right to access test results. If this right is given through Organisational Units, a notification will only be sent, if the notified superior has the right to access her data.

We propose to add the activation for Notifications to the Top Actions of the Test, similar to e.g. the Course. But unlike there, the notifications are not dependent on the news service and do not have to be activated separately in the settings. The notification is sent to the people who have activated it for a test in the top actions when a participant's test is finished/ended (see above).

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

Mockup of the TopActions:

We add the link to the test, which was finished to the notification mail. Also, to be clear, no results are attached to the notification:

3.3 New User Interface Concepts

No new Interface Concepts

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

This feature will increase the privacy instead to the feature today, as no new files with result & personal data are generated and sent.

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

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  Strassner, Denis [dstrassner]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

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

6.4 Approval

Approved at {date} by {user}.