What this category's data looks like
This category's data looks like this: In material verification and discrepancy localization, university admissions physical examination organization mainly handles three types of materials: physical examination forms, re-examination applications, and restricted-major notifications. Physical examination forms come from the physical examination department and are submitted centrally by batch; fields include name, gender, ID number, physical examination conclusion, restriction conclusion, date, and signature. Re-examination applications come from the admissions office or the candidate and are submitted sporadically by re-examination batch; fields include name, ID number, original physical examination conclusion, re-examination items, application date, and approval signature. Restricted-major notifications come from the admissions office and are updated periodically by restricted-major list; fields include name, ID number, restricted major, notification date, and receipt signature. When these three types of materials enter this function, the physical examination form serves as the primary material and takes the role of baseline record, the re-examination application serves as supplementary material and takes the role of change record, and the restricted-major notification serves as notification material and takes the role of confirmation record. After material parsing and chunking, data rows are immediately persisted as visible data for subsequent retrieval and discrepancy comparison.
Configuration and implementation checks
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.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Name, gender, ID number, physical examination conclusion, restriction conclusion, date, and signature are complete within the physical examination form and consistent with the ledger | Check whether the data row status is parsed, indexing, or indexed, and compare the physical examination form fields with the ledger fields |
| Re-examination application | Name, ID number, original physical examination conclusion, re-examination items, application date, and approval signature are complete within the re-examination application and consistent with the corresponding record in the physical examination form | Check whether the name, quantity, and date of the same object in the re-examination application and the physical examination form are consistent, and check whether the approval signature is missing |
| Restricted-major notification | Name, ID number, restricted major, notification date, and receipt signature are complete within the restricted-major notification and consistent with the restriction conclusion in the physical examination form | Check whether the restricted-major notification and the restriction conclusion in the physical examination form are consistent, and check whether the receipt signature is missing |
| Data row | Is in one of the three states parsed, indexing, or indexed and consistent with the interface display; file records and data row identities are distinguishable | Open the data row to check the status, separately verify the file record and the data row, and check whether the data rows covered by the rebuild task contain only indexed data |
Three common errors
- Symptom: a just-uploaded physical examination form cannot be found. Cause: the data row is in parsed or indexing status, and data pending indexing is naturally isolated at the retrieval layer and is not recalled.
- Symptom: the name, quantity, or date of the same candidate does not match between the physical examination form and the re-examination application. Cause: the two material versions are not synchronized, or fields were not aligned during entry.
- Symptom: the restricted-major notification lacks a receipt signature, or the re-examination application lacks an approval signature. Cause: the signature page was not collected during material circulation, and the receipt was not submitted together with the material.
How to verify the setup
How to verify the setup: Acceptance for this function: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, and confirm that the status passes through parsed, indexing, and indexed in sequence, and that the rebuild task covers only indexed data rows.
Business test: use one real record to find a field inconsistent with the ledger, verify the name, quantity, date, and signature of the same object in the three materials—physical examination form, re-examination application, and restricted-major notification—record the discrepancy, and submit it to the reviewer to confirm write-back.
- Check whether the data row status is parsed, indexing, or indexed, and separately verify the file record and data row identifiers
- Check whether the data rows covered by the rebuild task contain only indexed data, confirm the model-switch rebuild scope, and verify the correspondence between settings related to
chunkSize,chunkSplitter, andtrainingTypeand the data rows