lost1227
commented
1 year ago I believe the issue is because we are forgetting to register end-of-meeting events.
Imagine the following scenario: A Wednesday meeting, Student A is checked-in but not checked-out, and no end-of-meeting event is registered. Then, at the next Monday meeting, a lead goes to check Student A in, notices they're already checked-in, and assumes it's because another lead already checked them in. Then, at the end of the Monday meeting, Student A is checked-out as usual.
In this scenario, Student A would be credited the whole 5 days between when they were checked in on Wednesday and checked out on Monday as time spend at a robotics meeting.
The solution is to have the system check nightly if anyone is still checked-in, and automatically mark an end-of-meeting event.
I plan to set up a cron script that will run nightly and call the attendance api through the CLI to schedule the end-of-meeting event if necessary.
Figure out a solution to the super-long attendance sessions.