Activities: Attendance Register
This is an activity module for tracking time spent by Students (or other users) in a Course or in a related group of Courses.
Online activity is automatically tracked.
Users may also (optionally) record "offline" sessions of work.
The module will show aggregate report by user, or detailed report at user's session level.
Printable versions of all reports are available.
It also supports activity completion rules by minimum time in the Course.
By defaults, it tracks only activity in the Course the instance is in.
You may change this behaviour by module instance configuration. You may track all Courses in the same Category or Courses "meta-linked" to this Course.
By default, it tracks only Student's activity.
You may choose whose activity will be tracked by modifying Role Capabilities.
By default, only Teachers, Managers and Administrator may see other report of other user's activities.
You may change this behaviory by modifying Role Capabilities.
The Module is currently translated in English and Italian.
Documentation and an FAQ (small - work in progress) are available in English only.
Note
this module is based on the idea of the old Register module for Moode 1.x, but it is not an update of this module.
You cannot upgrade or restore Register data from Moodle 1.9 using this Attendance Register module.
Please note that this module is not related to Attendance module.
Attendance Register (this module) automatically calculates time spent online in Moodle's courses, while Attendance module allow teacher to explicitly certify attendance to a specific "offline" session.
Useful links
Screenshots
Thank you for reporting Bootstrap-based theme problems, I'd never noticed by myself
Table contents were not misaligned actually, but Bootstrap styling made them unreadable.
I've added some Bootstrap specific css classes. Now they should look much better using those themes than using others
@Daniel Méthot
The version I've just released is marked 2.5-compatible
I've tested it on 2.5.1+ and I didn't have to make any code change actually, except for aesthetic ones above.
Also, there's a slight typo "Last actitity on Site " ! Oops !
Cheers
Ray
I'll fix the typo in next release
About compatibility, I've just tested it working on 2.5.1+, so what does it means "I can't it into 2.5.1"?
the "last session" is delayed on purpose, not by mistake, to avoid miscalculation of the current session or need to continuously recalculating sessions and aggregates (total times) while the user is online.
The logic is explained here: https://github.com/nicusX/moodle-mod_attendanceregister/wiki/Online-Session-delay
Currently, sessions are never updated, just added when considered closed.
They may be considered "closed" only after waiting a certain time after the last user's detected activity (and waiting the next cron run, as Moodle isn't able to do anything in background out of cron).
Showing the "current" user session is not just a matter of reducing the delay.
The logic should be changed, and you'd need to continuously update current session while the user is online.
Serious performance problems may also occur in sites with many users.
I've no short-term plan for testing and porting on 2.6.
If anyone else have time and skill to check it (and fix it, if needed) for 2.6, I'll be glad to integrate in the release.
The code is available on https://github.com/nicusX/moodle-mod_attendanceregister
You may add additional columns showing any User's field, using some PHP coding.
The code generating the Users list table is the html_table() method in attendanceregister_tracked_users.class.php
I installed the module without any problem in moodle 2.52. I entered the information required to use the module in one of my courses but when I pulsed the button Save and Display, got the following error message
[an error occurred while processing this directive]. What are the possible causes and what should I do to solve it?
Thanks, Luis
I'm using it on 2.5.4 with no error, so there should be some issue related to your installation.
This error you report is rather generic and not very helpful.
Please, raise the debug level to get some meaningful message.