What this category's data looks like
This category's data looks like this. For the deployment, operations, and application handover of general higher education admission enrollment and filing, materials come from three types: admission plans, filing rules, and enrollment rosters. Admission plans provide institution-major groups and planned numbers; filing rules provide batches, volunteer modes, and filing ratios; enrollment rosters provide candidates, scores, and admission results. The update cadence advances by batch; after each round of filing the roster is refreshed, and plans and rules are subject to the release of the current round. Field characteristics center on institution code, major group number, planned number, filing ratio, candidate number, total score, admission status, and signature column. When materials enter the conversation logs and auditing function, admission plans and filing rules serve as the verification baseline, and enrollment rosters serve as the result-side records; the three form a traceable chain by date and signature.
Configuration and implementation checks
Configuration and implementation checks. This step is executed by the conversation record interface (by application and session dimension), outputting the session message list and total record count, including role and reference information. "Handover-ready deployment status and operation records" are then completed by humans or external systems.
| Object | Check | Verification action |
|---|---|---|
| Admission plan | Institution code, major group number, and planned number are consistent with the current round's release, and the signature column is complete | Pull records by application and session dimension, verify the chatId source, and compare planned numbers and dates |
| Filing rule | Batch, volunteer mode, and filing ratio are consistent with the current round's rules, and versions are synchronized | Open a single record to verify references and elapsed time, and confirm that the rule version corresponds to the record time |
| Enrollment roster | Candidate number, total score, and admission status correspond item by item with plans and rules, and receipts are complete | Page through to retrieve all records, verify value and dataId, and compare the roster with the records |
| Deployment status and operation records | Version, connection, and task records are consistent, and the handover form is verifiable item by item | Page through by total record count total, confirm response code of 200, and mark missing items as pending supplementation |
Three common errors
- Symptom: the same candidate's name or quantity does not match between the roster and the records. Cause: the two materials were exported by different batches, and the dates were not aligned.
- Symptom: the filing rule version does not match the record time. Cause: after the rules were updated, they were not synchronized to the handover materials, and the old version is still in use.
- Symptom: the roster lacks signatures or receipts, and the handover form cannot be closed. Cause: the registration and review steps were not executed with item-by-item verification.
How to verify the setup
This function's acceptance: page through by total record count total to retrieve all records, sample one record to verify role, reference information, and time, and confirm response code of 200.
Business test: verify the handover form item by item once, and see which record item is missing.
- Pull records by application and session dimension, and verify the sources of the
chatIdandvaluefields. - Pull two consecutive pages and compare the total count and offset to confirm that the number of records is complete.