Feature Wiki

Information about planned and released features

Tabs

Data Collection : Individual Configuration of Notifications

Page Overview

[Hide]

1 Initial Problem

At the moment, all activities in a table are notified when the notification function is activated.

This is sometimes a lot of information, not all of them seem to be useful for everyone.

2 Conceptual Summary

Similar to the forum, users should be able to decide exactly what they want to be notified about. 

  • New Entries
  • Updated Entries
  • Deleted Entries

MockUp for 'Notification Settings'-Modal

Alternatively, notifications could also be made configurable for each table. With the exception of the authors of the data collection, it is assumed that there is usually only access to one or two tables.
On the other hand, for authors with intensive use, it can be assumed that a lot needs to be displayed here.

Content in Modal:

[Table title A] 
     [☑] New Entries
     [☑] Updated Entries
     [☑] Deleted entries

[Table title B] 
     [☑] New Entries
     [☑] Updated Entries
     [☑] Deleted Entries

3 User Interface Modifications

3.1 List of Affected Views

  • Content-Tab of a Data Collection if "Enable Notification" in Settings in activated.

3.2 User Interface Details

  • Option A: 
    • If 'Activate Notification for Data Collection' is used, a second Action 'Notification Settings' is available.
    • Selecting the ‘Notification Settings’ action opens a modal that allows you to select the notification types.
  • Option B:
    • There is always only the ‘Notification Settings’ action, which opens a modal that allows you to select the notification types.
    • If a notification is activated, the bell forces active notification as the status. If no notification type is activated, the bell remains deactivated.

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

Nothing specific.

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

Nothing specific.

6 Security

Nothing specific.

7 Contact

8 Funding

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

  • …

9 Discussion

Kunkel, Matthias [mkunkel], 14 OCT 2024: IMHO, the most annoying problem with notification is that one is notified about every change in a data collection. I prefer the behaviour in the wiki where you don't get new notifications if one is working on a page unless the 'author' edits another page. I would prefer to have such a 'buffer' in the data collection, too.

Concerning the idea to 'watch' also single tables within a data collection I have to say that I never had the feeling yet to need such a feature. And I have created several data collections with more than one table, especially in the beginning of this feature. In my experience, changes are usually only made in the general table. Other tables are often delivering values for dropdowns within the general table. And these values are not changed that often. So you don't get crazy if you receive a notification from one of them...

To summarise briefly, having notification options for new entries, updated entries and deleted entries would be sufficient for me (and reduce complexity).

JourFixe, ILIAS [jourfixe], 14 OCT 2024: We highly appreciate this suggestion and schedule the feature for ILIAS 11. We prefer the implementation of option A and only to support the selection of new entries, modified entries and deleted entries.

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

Last edited: 14. Oct 2024, 16:57, Kunkel, Matthias [mkunkel]