What this category's data looks like
University admissions physical examination organizations process three types of materials intensively during the admissions season: physical examination forms, re-examination applications, and restricted-major notifications. Sources include the campus hospital, the admissions office, and departmental receipts, and the update cadence rolls forward with batch progression and policy wording adjustments. Physical examination form fields include name, candidate number, past medical history, physical examination conclusion, date, and physician signature; re-examination applications include application reason, original conclusion, re-examination items, date, and applicant signature; restricted-major notifications include restricted major name, restricted basis, notification date, and candidate receipt. After these three types of materials enter this feature, they are stored separately by batch and version; the physical examination form serves as the main record, while re-examination applications and restricted-major notifications serve as its change and extension materials, jointly supporting status traceability for the same candidate.
Configuration and implementation checks
This part is executed by the index service and vector store, outputting vectors and index status (whether recall is possible, whether data in the same group is merged). The "version ledger and change records" are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Fields, date, and signature must be complete, and the name and candidate number must be consistent with the re-examination application and restricted-major notification | Open the data row to check the index fields, confirm that the vector identifiers for the same group are complete, and that the status is indexed |
| Re-examination application | The application reason, original conclusion, re-examination items, and date must be consistent with the corresponding record in the physical examination form, and the signature or receipt must not be missing | Retrieve the candidate's record, check whether the data in the same group is merged, and calculate the cited text according to limit |
| Restricted-major notification | The restricted major name, restricted basis, and notification date must be consistent with the physical examination conclusion, and the receipt must be retained | View the rebuild task records and confirm that after changing the model, rebuilds are triggered only for data that has already completed indexing |
| Version ledger and change records | The current version is unique, old versions are traceable, citations are synchronized, and the name, quantity, and date of the same record in each material must be aligned | After changing one piece of content, check whether the version number and citations are updated synchronously, and check the coverage scope of the rebuild task records |
Three common errors
- Symptom: The name and date of the same record do not match between the physical examination form and the re-examination application. Inspect the following: The two materials were stored separately and were not merged by the same candidate number, and the versions were not synchronized.
- Symptom: The restricted-major notification lacks the candidate receipt or signature. Inspect the following: The receipt material was not stored together with the notification.
- Symptom: After changing the model, recall quality decreases, and some data rows have content but cannot be retrieved. Inspect the following: The rebuild task only covers data that has completed indexing; data rows that have not completed indexing do not participate in recall, so indexing must be completed before rebuilding.
How to verify the setup
This feature's acceptance check: sample one data row to inspect the index fields, confirm that multiple vector identifiers are complete and the status is indexed, then retrieve once to see whether data in the same group is merged and whether the highest score is taken.
Business test: change one piece of content, see whether the version number and citations are updated synchronously, and check whether the rebuild task records cover that data row.
- In the knowledge base settings, check that the index model is consistent with the vector model actually used by the knowledge base.
- Open a data row to check the index fields, confirm that multiple vector identifiers for one piece of data are all present, and view the data scope covered by the rebuild task records.