What this category's data looks like
In the compulsory education dropout prevention and control scenario, the materials entering this page's functionality are mainly of three types: dropout risk ledgers, persuasion-to-return records, and home visit records. Risk ledgers are usually registered student by student, with fields including name, student status number, risk level, determination date, and responsible person; persuasion-to-return records focus on the number of persuasion attempts, persuasion methods, parent signature, and receipt; home visit records include home visit time, participating teachers, family situation, and parent signature. These materials are mostly submitted weekly or monthly by schools or townships, and the update rhythm is tied to semester milestones and persuasion-to-return progress. When the materials enter the conversation logs and auditing functionality, each has a different role: risk ledgers provide student identity and risk status, persuasion-to-return records provide process and signature evidence, and home visit records provide household verification and receipts. Conversation records are only responsible for retaining conversation evidence and do not replace the above business ledgers; manual or external systems need to register, export, and review based on them, ensuring the current version is unique, old versions are traceable, and references are synchronized.
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. The "version ledger and change records" are then completed manually or by an external system.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Whether fields, dates, and signatures are complete, and whether the risk level and determination date match | Pull session records by chatId, verify the name, student status number, determination date, and responsible person's signature in the risk ledger, and confirm consistency with the current version |
| Persuasion-to-return record | Whether the number of persuasion attempts, persuasion methods, parent signature, and receipt are consistent with the ledger | Locate a single record by dataId, verify the number of persuasion attempts, date, and parent signature, and check whether the old version is traceable and whether references are synchronized |
| Home visit record | Whether the home visit time, participating teachers, family situation, and parent signature are consistent with the ledger | Open value to view the record details, verify the home visit time, participating teachers, and receipt, and confirm that the name, quantity, and date of the same record match across the two materials |
| Conversation record interface output | Whether the total record count and paginated item count match, and whether role and reference information are complete | Page through by total record count total to retrieve all, sample one record to verify role, reference information, and time; response code of 200 indicates the request succeeded |
Three common errors
- Symptom: The name, number of persuasion attempts, or date for the same student do not match between the risk ledger and the persuasion-to-return record. Cause: The two materials are registered separately and are not uniformly verified and synchronized against the current version.
- Symptom: An old version of a persuasion-to-return record is still referenced, and the current version and the old version coexist. Cause: The version was not synchronized, the old version was not marked invalid after the change, and references were not updated with the version.
- Symptom: The home visit record lacks a parent signature or receipt, and the persuasion-to-return record lacks a parent signature. Cause: Signature and receipt fields were not verified when the materials were archived, and the registration and review steps are disconnected.
How to verify the setup
This functionality's acceptance: page through by total record count total to retrieve all, sample one record to verify role, reference information, and time; response code of 200 indicates the request succeeded.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Pull records by application and session identifier, pull two consecutive pages and compare the total and offset, and confirm that the number of records matches the total.
- Open a single record to verify the role, reference, and elapsed time fields, and confirm that message roles correspond to the original conversation and that the reference and elapsed time fields are visible.