Hi,
We have a scenario where students are required to attend in person and scan a QR code to be marked as present. The challenge we are facing is that some students have started sharing their Moodle login credentials with other students so that attendance can be marked on their behalf.
To address this issue, I have considered the following two possible approaches:
-
Face verification during attendance marking
When a student scans the QR code on their mobile device to mark attendance, they are prompted to capture a photo of their face. The image is then processed by an AI service to generate a facial signature. This signature can be compared against those of students who have already marked attendance. If the system detects that the same face has already been used for another account, the attendance marking is blocked.
-
Device-based identification using cookies
Another approach is to assign a random value stored in a cookie on the student’s device when they log in. The same value is also stored in the database alongside the user ID. If the student logs out and attempts to log in with another student’s account on the same device, the cookie value can be checked against the database. If it is already associated with another user who has marked attendance, the system can block the attendance action.
I would appreciate any suggestions for alternative or more effective methods to prevent students from marking attendance on behalf of others.
Hi,
We have a scenario where students are required to attend in person and scan a QR code to be marked as present. The challenge we are facing is that some students have started sharing their Moodle login credentials with other students so that attendance can be marked on their behalf.
To address this issue, I have considered the following two possible approaches:
Face verification during attendance marking
When a student scans the QR code on their mobile device to mark attendance, they are prompted to capture a photo of their face. The image is then processed by an AI service to generate a facial signature. This signature can be compared against those of students who have already marked attendance. If the system detects that the same face has already been used for another account, the attendance marking is blocked.
Device-based identification using cookies
Another approach is to assign a random value stored in a cookie on the student’s device when they log in. The same value is also stored in the database alongside the user ID. If the student logs out and attempts to log in with another student’s account on the same device, the cookie value can be checked against the database. If it is already associated with another user who has marked attendance, the system can block the attendance action.
I would appreciate any suggestions for alternative or more effective methods to prevent students from marking attendance on behalf of others.