Skip to content
This repository has been archived by the owner on Nov 25, 2020. It is now read-only.

Report Generation #4

Closed
maxfierke opened this issue Jan 10, 2013 · 3 comments
Closed

Report Generation #4

maxfierke opened this issue Jan 10, 2013 · 3 comments
Assignees
@maxfierke
Labels
feature high priority
Milestone
1.0 Alpha

Comments

@maxfierke
Copy link
Contributor

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.
@ghost ghost assigned maxfierke Jan 10, 2013
@maxfierke
Copy link
Contributor Author

Also, this depends on issue #11 being implemented

@maxfierke
Copy link
Contributor Author

Issue #11 has been resolved. Moving this to high priority.

maxfierke added a commit that referenced this issue Jan 22, 2013
@maxfierke
Implement time clock report generation.
f5b4ccf 
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>
@maxfierke
Copy link
Contributor Author

Implemented in f5b4ccf

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@maxfierke maxfierke

Labels
feature high priority
Milestone
1.0 Alpha
Development

No branches or pull requests
1 participant
@maxfierke