What this category's data looks like
This page's material covers primary and secondary school student status establishment and changes, including three categories: student status records, transfer applications, and suspension/resumption materials. The sources are school student status systems and paper forms; the update cadence follows semesters and the points at which changes occur; fields include student name, ID number, class, change type, date, and signature. When the three categories of materials enter the conversation record function, their roles differ: student status records serve as the static base roster, transfer applications serve as the trigger evidence for changes, and suspension/resumption materials serve as the basis for status changes. Each leaves question and answer records in the session for subsequent registration and review.
Configuration and implementation checks
| Object | Check | Verification action |
|---|---|---|
| Student registration file | Student name, national student ID, class, and effective date are consistent between the file and the transfer application, with complete signatures and receipts | Retrieve records by application and session identifiers, verify the fields and dates of the referenced file within the session corresponding to chatId, page through to get all records, then compare the total record count total with response code of 200 |
| Transfer application | The names of the transferring-out and receiving schools, the number of changes, and the application date match, and the receiving party's signature or receipt is not missing | Locate the entry referencing the transfer application in the record list, open the single entry to verify the referenced information and role fields, and confirm that message roles correspond to the original conversation |
| Leave and return-to-school materials | The leave and return dates, handler signature, receipt number, and student registration file status are consistent, and versions are synchronized | Pull two consecutive pages by offset, verify the contents of the dataId and value fields, and check that the number of referenced entries is recorded separately according to the array length |
Three common errors
- Symptom: the name and date of the same transfer application do not match across two materials. Cause: during registration, fields were not checked item by item against the student status record, and the signature or receipt is missing.
- Symptom: the interface returns empty but there is a session in the UI. Cause: the application and session identifiers were not synchronized, or the pagination offset did not start from zero.
- Symptom: exported records lack citations and duration. Cause: only the first page was retrieved, and pagination was not continued according to the total record count to retrieve everything; the version was not synchronized.
How to verify the setup
This function's acceptance: paginate according to the total record count to retrieve everything, sample one record to check the role, citation information, and time, and confirm that the message identifiers and content fields _id, dataId and value correspond consistently.
Business test: check item by item once according to the handover form, see which record item is missing, and focus on checking the fields, dates, and signatures of student status records, transfer applications, and suspension/resumption materials.
- Paginate by application and session dimension, compare the total record count with the offset, and confirm response
codeof 200. - Open a single record to check the role, citation array length, and duration; record the citation count separately.