What this category's data looks like
The materials for primary and secondary school timetables and after-school service scheduling include the master timetable, teacher assignment table, after-school service project table, as well as accompanying deployment status and operation records, handover forms, and receipts. These materials come from three stages: academic scheduling, after-school service registration, and operations handover, and are updated by semester, week number, and duty shift. Field characteristics center on course name, assigned teacher, class, date, period, project name, signature field, and version number. When entering the conversation log and audit function, the master timetable handles structural verification of classes and periods, the teacher assignment table handles verification of the correspondence between personnel and courses, the after-school service project table handles registration verification of project names and participant counts, the deployment status and operation records handle verification of version and connection information, and the handover forms and receipts handle verification of signatures and destinations.
Configuration and implementation checks
This step is executed by the conversation record interface (by application and session dimension), outputting a session message list and total record count, including role and reference information. "Handover-ready deployment status and operation records" are then completed manually or by an external system. Conversation records are pulled in pages by application and session dimension; the returned results distinguish between the two role types, question and answer, and include reference and elapsed time fields.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Class, period, date, and version number match in name, quantity, and date across the master timetable and teacher assignment table | Pull session records by chatId, verify the order of the two role types, question and answer, in the returned list, and compare the class and period fields of the master timetable and teacher assignment table |
| Teacher assignment table | The correspondence between assigned teachers and courses is consistent across the two materials, and the signature field and receipt are complete | Open one record to verify the reference and elapsed time fields, use dataId to locate a single message, and check the teacher names and course names in the teacher assignment table and after-school service project table |
| After-school service project table | Project name, participant count, and date match between the registration materials and the handover form, and the version is synchronized | Pull two pages consecutively to compare the total record count total and the offset, verify response code of 200, and check the project names and participant counts in the after-school service project table and handover form |
| Deployment status and operation records | Version, connection, and task records are consistent; if a signature or receipt is missing, the handover is considered incomplete | Use value to view the details of a single record, verify the version number and connection information in the deployment status and operation records, and compare the signature field of the handover form item by item |
Three common errors
- Symptom: The name, quantity, and date of the same course record do not match between the master timetable and the teacher assignment table. Cause: The two materials are registered separately and were not verified against the same version number.
- Symptom: The version in the deployment status and operation records is not synchronized, and the connection information and task records are inconsistent. Cause: The version and connection fields were not verified item by item during handover.
- Symptom: The handover form lacks a signature or receipt, and the after-school service project table does not match the registration materials. Cause: The materials were not traced by application and session identifier when entering the function.
How to verify the setup
Acceptance of this function: page through by total record count to retrieve all records, sample one record to verify the role, reference information, and time, and confirm that response code of 200 and the total record count total match.
Business test: verify once item by item according to the handover form, see which record item is missing, and focus on verifying the fields, dates, and signatures of the master timetable, teacher assignment table, and after-school service project table.
- Verify the sources of the two identifiers by application and session identifier, pull two pages consecutively to compare the total record count and offset, and confirm that the number of records matches the total.
- Open one record to verify the reference and elapsed time fields, use
dataIdandvalueto locate a single message, and check that the number of references and the reference text tokens are recorded separately.