Attendance Module & API Improvements.

[dasunhegoda]

The proposed improvements as follows

attendance_type & attendance_location

• The attendance_type & attendance_location fields should be an integer value.
• The values for attendance_type & attendance_location should be fetched dynamically from an API when it's used.
• The attendance_type & attendance_location dropdown should be populated with these fetched values, and user input should be restricted to prevent manual typing to avoid errors.
• We need to determine if attendance_location should be a sub-type of attendance_type based on specific use cases.

submitted_by

• Update the submitted_by field to store the user_id or another parameter to identify the user submitting the attendance.
• Add a new parameter submission_source to identify which application is being used to submit the attendance, such as self-reg, OCR, etc.

Timestamp for submission_date

• The submitted_date field should be stored as a timestamp with hours, minutes, and seconds for better precision.

Data audit logging in attendance module

• All values retrieved from the attendance server for program management purposes within the SP-MIS must be stored in the attendance module to ensure traceability.

Options for retrieving data from the attendance server

• Option 1: When new data becomes available on the attendance server, a webhook will automatically trigger and push the relevant data to the SP-MIS in real-time.
• Option 2: Configure the SP-MIS to periodically poll the attendance server and pull any new or updated data at regular intervals.
• Should the data pushed from the attendance server to SP-MIS be archived upon receipt? If so, what is the retention period for storing this data
• We need to decide which approach we should take here