Event Monitor specification: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
The Event Monitor tool will allow users choose their favourites events and receive notifications in real time when the choosen event is happening in the frequency and time. | The Event Monitor tool will allow users choose their favourites events and receive notifications in real time when the choosen event is happening in the frequency and time. | ||
The main concept is to turn the new event system more usefull to teachers and admin. | |||
== Benefis == | |||
* Create a close relation between teachers and students. | |||
* Real time monitoring. | |||
* Keep Admins aware about major changes in the system. | |||
== Usage scenarios == | == Usage scenarios == |
Revision as of 03:13, 30 May 2014
The Event Monitor tool will allow users choose their favourites events and receive notifications in real time when the choosen event is happening in the frequency and time. The main concept is to turn the new event system more usefull to teachers and admin.
Benefis
- Create a close relation between teachers and students.
- Real time monitoring.
- Keep Admins aware about major changes in the system.
Usage scenarios
- Send message to teacher when more than X posts in any forum in their course in Y minutes.
- Send message to teacher when assignment is submitted in their course.
- Send message to admin when a course is deleted.
- Send message to student when they are graded for activity X.
User interface mock-ups
List rules
This is the main page of Event Monitor where users can list rules, subscribe to a rule, choose a specific module to monitor and delete rule. In the List rule page the user have a button Add New Rule, to access a form to create a new rule.
Add new rule
This is the form where users can create a new rule, customize the frequency and time and create a personalized notification message.
How it works
The tool observes acvitivity by capturing events in real time (and/or querying logs as necessary). A variety of trigger algorithms (with parameters and thresholds) are applied to the stream of data. The parameters may be modified by teachers and admins in their tool interface.
Example: a simple algorithm may be "Count the number of posts in a forum". A parameter can be a time period "X min" with a threshold of "Y".
When any given activity passes the threshold, a message would be generated (with relevant link) and sent to the specified users as a message. The message can contain data from any fields that are used in the event using {tags}. The user may then receive the message on their mobile phone via the Moodle Mobile app.
Example: when there are more than 10 posts within 30 minutes on a forum, the teacher will get a notification containing a description of the activity and a link to the forum.
New algorithms can be implemented via forms, with all the contents determined by Event discovery, and then saved by user (private), by course (all teachers in site can see and edit them) or by site (all admins in site can see and edit them).
See also
- Event 2
- Moodlerooms developed a "Personalized Learning Designer" that has some of these features (mostly for individual students only).