What this category's data looks like
Student status establishment and changes in primary and secondary schools involve three core types of materials: student status records, transfer applications, and suspension/resumption materials. Student status records capture students' basic information and enrollment status; transfer applications carry the application and approval chain for cross-school mobility; suspension/resumption materials correspond to the supporting documents for status suspension and restoration. These materials usually come from academic affairs system exports, scanned paper forms, and external receipts, and their update cadence follows semester milestones, approval flows, and policy adjustments. Field characteristics center on name, student status number, class, date, signature, and receipt number. When entering this feature, all three types of materials leave interaction traces in the form of conversation messages and reference information, which are used for subsequent manual registration and review and do not directly serve as a business ledger.
Configuration and implementation checks
This part is executed by the conversation record interface (by application and session dimension), outputting a list of conversation messages and the 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 |
|---|---|---|
| Student status records | Fields, dates, and signatures must be aligned item by item with transfer applications and suspension/resumption materials | Pull records by application and session dimension, verify chatId and dataId, and confirm the reference information and response code of 200 |
| Transfer applications | The name, quantity, and date of the same record in the two materials must be consistent | Pull two pages in succession to compare the total record count total and offset, and sample one record to verify the role and reference information |
| Suspension/resumption materials | If signatures or receipts are missing, they must not enter version synchronization | Open a single record to verify the reference and elapsed time fields, and confirm that value is traceable |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, pull again to see whether the total record count and reference information change synchronously |
Three common errors
- Symptom: The name and date of the same record do not match between the student status record and the transfer application. Cause: The two materials are maintained separately, and fields and signatures are not compared against a unified version ledger.
- Symptom: Suspension/resumption materials lack signatures or receipts, and an old version is used as the current version. Cause: The version is not synchronized, and the change records do not register signature and receipt status.
- Symptom: The interface returns empty but there are sessions in the interface, and the exported records lack references. Cause: Pagination only retrieves the first page, and all pages are not retrieved according to the total record count.
How to verify the setup
Feature acceptance: paginate through all records according to the total record count total, sample one record to verify the role, reference information, and time, and confirm response code of 200 and that _id, dataId and value are traceable.
Business test: change one piece of content and see whether the version number and reference are updated synchronously.
- Paginate and pull by application and session dimension, pull two pages in succession to compare the total record count total and offset, and confirm that the number of records matches.
- Open a single record to verify the role, reference, and elapsed time fields, and check that the reference count and reference text tokens are recorded separately.