You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 25, 2020. It is now read-only.
Clock data needs to be moved weekly to an external data store (not the MySQL database) and stored for 4 months or so before it is pruned. The data should be stored by week and reports should be generated in a way where it compares clock data with schedule data, distinguishing between scheduled and worked, not scheduled and worked, scheduled and not worked, and not scheduled and not worked. Backend could be either SQLite, or maybe even MongoDB.
Garreth also asked for something along the lines of employee statistics. E.g. Rank employees by lateness, earliness, frequency of late clock in, etc. See issue #24.
The text was updated successfully, but these errors were encountered:
This allows supervisors to generate reports that compare time clock data with when users are scheduled and show when users worked and whether or not they had clocked in. Implements issue #4.
Signed-off-by: Max Fierke <max@maxfierke.com>
Clock data needs to be moved weekly to an external data store (not the MySQL database) and stored for 4 months or so before it is pruned. The data should be stored by week and reports should be generated in a way where it compares clock data with schedule data, distinguishing between scheduled and worked, not scheduled and worked, scheduled and not worked, and not scheduled and not worked. Backend could be either SQLite, or maybe even MongoDB.
Garreth also asked for something along the lines of employee statistics. E.g. Rank employees by lateness, earliness, frequency of late clock in, etc.See issue #24.The text was updated successfully, but these errors were encountered: