Notifications
Version 2.0
Goal:
A stream of activities displaying changes to things that you own and things that you are involved with.
Phase One
Framework for notifications
- Framework for capturing all changes to links
- Integrate this with the framework created for "edit history"
- Replace the forum notifications
- Framework for grouping/summarizing these captures
- Possibility for the sysadmin to configure/filter these captures and automatic cleaning up
- Possibility for users to configure/filter their display of the stream of the change history
- .... additions and changes by Arjan ....
Breakdown of the stream of activity for a user
Changes to things you own (you 'own' yourself as well):
- Notification about link changes (excluding KNOWS and FRIEND) that are made to you (e.g. tag in a photo).
- Notification about contact request/confirms (KNOWS and FRIEND)
- Notification about links that are changed (added/deleted) to things that you own (e.g. interest, tag/keyword, comment, participant etc)
- Notification about text edits that others make to things you own.
Phase Two
Notification about new or changed links to things that:
- …you have linked to, but are not the owner of.
- …you have edited, but are not the owner of.
Notification about text edits that others make to things that
- …you are linked to, but are not the owner of.
- …you have edited, but are not the owner of.
Phase Three
- Design filters
- Decide what notifications are sent in a personal mail
Design
- Design work being done by Kim: http://clients.mediamatic.nl/common/history/screens/1_.html
Interface
- The interface should look similar to the designs that are made for the history pages (http://clients.mediamatic.nl/common/history/screens/1_3.html) using icons for adding, editing and deleting edges/text. In the activity stream we will need an extra column for the things that are 'changed'.
Format:
| Person | Action | Thing | Date |
| Gillian Evans | + Actor: Eveline Wiegmans | Eveline & Gillian at Kom je ook? 5 | Date |
Notes about existing notification system
In module: Teleport exists very basic handling of notifying owners of things about changes to the edges of these things. The changes that involve Teleport are only changes to intra-site edges, so no notifications of changes within one website. Notifying is done by email only, not stored in messages inbox.
The system still is functioning by storing all these changes in its own table (teleport_edge_notify_in) but the scheduled daily sending of emails (and cleaning up that table) is switched off.
The actual email that used to be sent is no more that a line “The following relations have been made to your account in the last day.” and 1 or 2 lines like “Jim at Mediamatic Lab made a new INTERESTED connection to Chikako Watanabe in Schokland“. Only exception to these lines are contacts made, with a line like “Mary added You as a contact”
On Mediamatic.net these Teleport changes average about 5 per day.
Notes about existing messaging system
Messaging is basically handled by Anymeta_Message that stores the messages in the database and sends the email by Anymeta_Emailer. There are 2 types of messages: message and notify.
The displaying of message lists and the message is done in a very basic way in module:Message and doesn't differentiate between messages and notifications.
Type Notify are send from:
- module:Contact
Type: Message are send from:
- module:Message
- module:MemberAdministration
- module:Signup
- module:Checkout
- action dialogs
No message, only email is sent by:
- module: Forum
- module: Invite
Problems in Messaging
To send messages, 3 different ways are used and have different ACL rules:
- message_module > sendMessage
- service anymeta_messages_send
- message > send
To create all the different e-mail texts only one template is used with a confusing mix of all the possible combinations.
To display the message on the website another template is used with a different confusing mix of all the possible combinations.
The sending of multiple messages (like to your contacts) is mixed up with sending one message.
Recommendations for Messaging (inbox)
- (De)select all messages
- Mark as (un)read
- Auto delete notifications older then one week
- <Previous Next> message (nice to have)
Telecommunicatiewet: http://wetten.overheid.nl/BWBR0009950/geldigheidsdatum_23-06-2010
Bijdragen
Reacties
Gillian
Fred
Eveline
Jeana