What this category's data looks like
This page addresses primary and secondary school timetable and after-school service scheduling scenarios. Materials include the master timetable, teacher assignment table, and after-school service project table. Sources are the academic affairs office, grade groups, and after-school service administrators. The update cadence changes with semester adjustments, temporary class changes, and project additions. Field characteristics center on course name, assigned teacher, class date, period, project name and headcount, and signature or receipt. When materials enter the conversation log and audit function, the master timetable serves as the primary record, the teacher assignment table is used to verify teaching relationships, and the after-school service project table is used to verify projects and headcounts; the conversation record interface only provides session evidence and does not replace business ledgers.
Configuration and implementation checks
This step is performed by the conversation record interface (by application and session dimension), outputting the session message list and total record count, including role and reference information. The version ledger and change records are then completed manually or by an external system.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Course name, class date, period, and signature are consistent within the master timetable | Pull records by application and session identifier, verify role and reference information, and register the version number |
| Teacher assignment table | Assigned teacher matches class, course name, and date with the master timetable | Page through to retrieve all records, compare chatId and dataId, and flag discrepancies |
| After-school service project table | Project name, headcount, date, and receipt are complete | Open a single record to verify references and elapsed time, and backfill signature or receipt status |
| Version ledger | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, re-pull and verify whether the total record count and references are synchronized |
Three common errors
- Symptom: The course name and date of the same record do not match between the master timetable and the teacher assignment table. Cause: The two materials are maintained separately and are not registered and reviewed under the same version number.
- Symptom: The after-school service project table is missing headcount and receipts, and the old version is still in circulation. Cause: The version was not synchronized, and references and signature status were not updated after the change.
- Symptom: The interface returns empty but sessions exist in the UI. Cause: The application and session identifiers come from inconsistent sources, or only the first page was retrieved without paging through all records according to the total record count.
How to verify the setup
This feature acceptance: page through all records according to the total record count, sample one record to verify role, reference information, and time, and confirm the status code is 200.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Pull pages by application and session identifier, pull two consecutive pages to compare the total record count and offset, and check the role order.
- Open a single record to verify the reference and elapsed time fields, register the version ledger, and backfill the signature or receipt.