-
-
Notifications
You must be signed in to change notification settings - Fork 489
proposal notification module
| Date | 2017-06-30 | Contacts | Paul van Genuchten |
| Status | Brainstorming | Release | 3.4? |
| Resources | Ticket # | ||
| Source code | |||
| Funding | |||
Several modules send notifications to users. By managing all notifications centrally, new options are possible, like: see a list of notifications, users can indicate they want daily digest, notification via slack, etc.
idea is to create a central notification system. Notifications such as:
- user requests a reviewer to review his record
- metadata owner gets notified of incoming feedback item on a metadata
- user requested to join a group (or update profile)
- user gets notified of an update on a metadata-thread he joined
- a validation service detects a link is unavailable or a metadata is invalid
A new database table containing the notifications, with columns from, to, date, type, message, status, template, language
Modules that need to send a notification call the notification API to create or update status of a notification.
The notification system could either receive the full message and send it, or it could receive a reference to a template and an array of key|value to substitute in the template. In the latter case, GeoNetwork can have a central configuration option to manage about the contents of the notification templates.
Some configuration settings on the user profile to configure notification settings (dayly digest, ...)
- Type: Improvement to existing feature
- Module:
- Vote Proposed: TBA
- Paul van Genuchten
If you have some comments, start a discussion, raise an issue or use one of our other communication channels to talk to us.