Project

General

Profile

Feature #7843

Student life events

Added by Yannick Warnier over 3 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Global / Others / Misc
Target version:
Start date:
19/09/2015
Due date:
% Done:

0%

Estimated time:
80.00 h
Complexity:
Normal
SCRUM pts - complexity:
?

Description

In particular in primary and secondary school, there is a need for teachers and the school authorities to be aware of events in the student life.
  • punishments
  • retentions
  • exclusions
  • notifications of bad behaviour
  • measures of responsabilisation
  • measures of prevention
  • measures of accompaniment
  • definitive exclusion
  • health issues (visit to the nurse's office)

It should be possible for the teacher to register those events from the student sheet (from the students list in his course), in a "Student life events log".
For school personnel not related to a course (HRD, admins, etc), accessing the "Student life events log" should be done through the users list in the administration panel (also in the student personal sheet).
For now, only admins and HRD (i.e. parents) should be able to see all events. Teachers and other roles should only be able to see the events that they logged.
For admins and parents, there should be a way to contact (by in-mail, through the messaging tool), the person who registered the event.
Teachers and admins can choose to register the event anonymously. Parents should not see who registered anonymous reports, but admins should be able to see them, always.

The log should be displayed at the list of calendar events, the latest event first. There should be some paging in place as the sheet can be maintained for years.
Also, the events log should be exportable (for admins and parents) in a text document format (.docx and .odt), respecting the anonymous aspect, if selected.

An event log should be defined by:
  • student_life table
    • id
    • event_type_id
    • datetime of the event
    • datetime of record creation
    • user_id of student affected
    • user_id of person registering the event
    • description
    • cid (course ID, optional)
    • sid (session ID, optional)
    • rid (room ID, optional)
  • student_life_type table
    • id
    • title varchar(255)
    • description text
    • mail_parent tinyint
  • student_life_log
    • id
    • student_event_id
    • event_type_id
    • datetime of the event
    • datetime of record creation
    • user_id of student affected
    • user_id of person registering the event
    • description
    • cid (course ID, optional)
    • sid (session ID, optional)
    • rid (room ID, optional)
The configuration of these logs (event_type management and special reports) should be available through a new admin block and an option to enable the feature:
  • Option
    • student_life_events_enable
    • StudentLifeEventTitle = "Student life log";
    • StudentLifeEventComment = "Enable to make the student life events log available to teachers and parents. Student life events are registered when a student is missing in class, visiting the nurse's office, etc. These events can be configured to send e-mails to parents or HR directors".
  • New admin block's name: "Student's life"
    • Configure event types
    • Events log : page with paginated list with search tools on:
      • user who registered the event
      • user affected
      • date (range) for datetime of event

Ideally, this feature should be usable for all users (including teachers) as school authorities might want to track issues with teachers behaviour.

A web service should be available to register or get log events for a specific user.

Finally, an e-mail should be sent to the parents or DRH every time one of their children/student has a new event. Having a configuration array somewhere about each type of event and whether this should send a mail to the parents would be nice.

History

#1

Updated by Yannick Warnier over 3 years ago

  • Description updated (diff)
#2

Updated by Yannick Warnier over 3 years ago

  • Description updated (diff)
#3

Updated by Yannick Warnier over 3 years ago

  • Estimated time set to 80.00 h
#5

Updated by Yannick Warnier about 3 years ago

  • Target version changed from 2.0 to 3.0

Also available in: Atom PDF