new Forum Posts as Push Notifications

This is a Draft

1 Initial Problem

A Forum is itended to provide a interaction of participants. Due to notification via Mail a promt reaction to content can't be provided.

• direct interaction with content and therefore other users 
• amount of Mails

ILIAS only supprt Notifications via mail. These are for example used to inform about a course partipation. If multiple other Notifications shall be transported by ILIAS, there will an amout of Mails. Importend Mails may be missed due to the amount of mails send. Due to this, the visibility for users regarding new events is insufficient. 

2 Conceptual Summary

Since the Push Notification Service is implemented in ILIAS 10, the forum could benefit, since it aims to provide interaction between the participants.

The Trigger for Push Notifications, will be the same as for mail, but only referring to new posts.

3 User Interface Modifications

3.1 List of Affected Views

Notification settings tab in Private Settings according to the original Post ILIAS Push Notification Service.

3.2 User Interface Details

presentation of Pushnotifications

• Variant 1
  • Title: new Post in Forum
    
    • rententionTime or delete orphaned (old number)
  • Description: No Content as Description
  • Action: Link to Thread or Post?
  • Logo: Logo of Instance
• Variant 2
  • Title: 'Number of new Posts' unread Posts in Forum 'forumname'
    • every Post?
  • Description: 'Title of thread': 'Name' posted in Forum 'forumname'
  • Action: Link to Thread
• Variant 3
  • Title: 'Name' posted in Forum 'forumname'
    • every Post?
  • Description: 'Title of thread': Content of post shortened to 40 chars '...'
  • Action: Link to post

Activation and deactivation of Notifications

• general or specific for PushNotifications (Push Notification Channels)
  • activation in Notification or Private Settings
  • Actication / Trigger via Bell of a Forum

Was passiert wenn Post gelöscht

1. 2. 3. Minute, danach SlowMotionQueue → verhindern, dass zu viel PushNotifications gesendet werden. 

3.3 New User Interface Concepts

• none, since the Notifications are handed over to the browser

3.4 Accessibility Implications

• none, since the Notifications are handed over to the browser

further inforrmation ILIAS Push Notification Service

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

The content of the Notifications can be sensitive. Therefore we suggest variant 1 of implementation as most privacy-secured Version.

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

• Author of the Request: Stake, Sebastian [sstake], Szmais, Ingmar [iszmais]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

• If you are interest in funding this feature, please add your name and institution to this list.
• Hochschule Bielefeld
• ILIAS.nrw

9 Discussion

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

Privacy

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

Approval

Approved at {date} by {user}.