What this category's data looks like
This page addresses the general college entrance examination registration qualification review scenario. Materials come from three categories: the examination registration form, household registration and student status certificates, and materials for children accompanying migrant workers. The registration form is filled out by the candidate, with fields including name, ID number, examination category, and graduating school; the household registration and student status certificates are issued by the public security authorities and the school, including household registration address, student status number, and start and end dates of enrollment; the materials for children accompanying migrant workers include residence permits, social insurance payment records, and parents' employment certificates. The three categories of materials are submitted together by registration batch, with the update rhythm bounded by review milestones, and supplementary submissions and corrections are common. When materials enter this feature, the registration form serves as the primary record, while the household registration and student status certificates and the materials for children accompanying migrant workers serve as comparison objects, each parsed into independent data rows for subsequent retrieval and verification.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), outputting data rows and index status (parsed, indexing, indexed). The discrepancy list is then completed by retrieval and subsequent processing. After parsing is completed, parsed chunks are immediately persisted as visible data rows and bound to a unique data identifier; the index transitions through the three states parsed, indexing, and indexed, and data pending indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Examination registration form | Name, quantity, date, and signature are complete, and field values can be compared item by item with the household registration and student status certificates | Check whether the data row status is parsed or indexed, and check whether fields are complete after chunking by chunkSize and chunkSplitter |
| Household registration and student status certificates | Household registration address, student status number, and start and end dates of enrollment are consistent with the registration form, and the issuing unit's signature or seal is not missing | Check the identifiers of the file record and the data row separately, and confirm that the dates and names of the same record match across the two materials |
| Materials for children accompanying migrant workers | The dates and quantities of the residence permit, social insurance payment records, and parents' employment certificates are consistent with the ledger, and the receipt is not missing | Check trainingType and the index status, confirm that data pending indexing does not participate in recall, and that rebuilding only covers indexed data |
Three common errors
- Symptom: The name or date of the same candidate does not match between the registration form and the household registration and student status certificates. Cause: The versions of the two materials were not synchronized, or they were not verified against the same record during data entry, and the discrepancy was not exposed during the parsing stage.
- Symptom: The materials for children accompanying migrant workers are missing a signature or receipt, which is only discovered during review. Cause: Material submission and parsed chunks are not bound to the same data identifier, and the missing item is not reflected in the data row status.
- Symptom: Newly uploaded materials cannot be found, or empty data rows remain after a training failure. Cause: Successful parsing does not mean retrieval will definitely hit; the index status must also be checked; data pending indexing is naturally isolated, and failed data can be edited or deleted.
How to verify the setup
This feature's acceptance: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, confirm that the three states parsed, indexing, and indexed are consistent with the interface display, and that rebuilding targets only data whose indexing has been completed.
Business test: use one real record to find fields inconsistent with the ledger, hand them to the reviewer for confirmation, and write the discrepancy list back.
- Open the data row to check the status, confirm that it is in one of the three states and consistent with the interface display, and check the identifiers of the file record and the data row separately.
- View the data rows covered by the rebuild task, confirm that it covers only data whose indexing has been completed, and that data pending indexing does not participate in the rebuild chain.