0% found this document useful (0 votes)
2 views3 pages

User Submission Tracking System Overview

The Check-In System tracks user submissions similarly to a workplace attendance system, providing automatic detection of daily limits and color-coded feedback for completion status. Admins have the ability to manually override submission statuses and access historical data for verification. The system includes a user-friendly interface for tracking recent submissions and maintains security and transparency through controlled access and logging of admin actions.

Uploaded by

mehran.abbasi93
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views3 pages

User Submission Tracking System Overview

The Check-In System tracks user submissions similarly to a workplace attendance system, providing automatic detection of daily limits and color-coded feedback for completion status. Admins have the ability to manually override submission statuses and access historical data for verification. The system includes a user-friendly interface for tracking recent submissions and maintains security and transparency through controlled access and logging of admin actions.

Uploaded by

mehran.abbasi93
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Overview of the Check-In System

This system functions similarly to a fingerprint-based attendance system at a workplace. Just as

employees check in when they arrive and check out when they leave, the website tracks whether

users have completed their daily submission limits.

---

### Core Functionality

1. Daily Submission Limit Tracking:

- Automatic Detection: Like clocking in and out, the system automatically detects when a user

completes their daily submissions, akin to completing a workday.

- Color-Coded Feedback: Upon reaching the daily limit, the system marks the day with a green tick

(similar to recording a completed workday in an attendance system). If the limit is not reached, the

tick remains grey (indicative of an incomplete workday).

2. Admin Oversight:

- Manual Override: The admin has the capability to manually adjust the check-in status from the

backend?marking a submission day as complete (green) or incomplete (grey), regardless of the

actual submissions made by the user. This is similar to an HR manager who can manually correct

attendance records if the automatic system fails or errs.

---
### User Interface (Frontend)

1. Visual Display for Users:

- Users can view their submission status for the last 30 days, represented by green (completed)

and grey (not completed) ticks. This mirrors how an employee might view their past month?s

attendance on a digital system.

2. Periodic Reset:

- Every 30 days, the frontend resets all ticks to grey, signaling the start of a new tracking period.

This is similar to how attendance records might be archived monthly, and a new record starts.

---

### Backend System

1. Historical Data Storage:

- While the frontend displays only a recent window of 30 days, the backend retains all historical

submission data. This comprehensive log is like maintaining all historical attendance records for

reference and audits.

2. Functionality for Admins:

- Admins can access full records to review or modify any user's daily submission status. This is

akin to an HR department having full access to employee attendance records for verification and

adjustments.

---
### Implementation Details

- Database Schema:

- A database table should track daily submissions with columns for user ID, date, number of

submissions, and status (completed/incomplete).

- Implement logs for any admin adjustments to maintain transparency and auditability.

- Logic for Automatic and Manual Updates:

- Develop scripts or cron jobs to automatically update the submission status based on user activity.

- Provide a secure interface for admins to manually update statuses as needed.

- Security and Permissions:

- Ensure that only authorized personnel (admins) have access to the backend system for making

manual status updates.

- Testing and Validation:

- Rigorous testing should be done to ensure that automatic detections are accurate and that

manual updates reflect correctly on both the backend and frontend.

---

This system should effectively track and manage user submissions in a transparent, automated, yet

controllable manner, much like modern digital attendance systems in workplaces.

You might also like