What this category's data looks like
During the admissions season, a college admissions physical examination organization centrally produces three types of materials: physical examination forms, re-examination applications, and restricted-major notifications. Their sources are the campus hospital, the admissions office, and departmental receipts, and their update cadence rolls forward with each batch. Physical examination forms carry past medical history, visual acuity and color vision, and physician conclusions; re-examination applications record re-examination items, appointment dates, and review signatures; restricted-major notifications list major names, the basis for restriction, and candidate acknowledgment. After these three types of materials enter the knowledge base retrieval service, each participates in recall as an independent fragment: physical examination form fragments answer field definitions, re-examination application fragments answer process and dates, and restricted-major notification fragments answer majors and basis, and they do not substitute for one another. The version ledger and change records are generated accordingly by subsequent nodes or manually.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate fragments and similarity scores (after mode, merge, rerank, filter, and upper-limit trimming). The version ledger and change records are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Whether fields, dates, and signatures are consistent with the current version | In the search test, test once each with synonymous questions, record the number of candidates and scores, and check whether the field-definition fragments remain stable after switching searchMode |
| Re-examination application | Whether re-examination items, appointment dates, and review signatures match | Compare the dates and signatures of the same record, observe changes in the ranking of the top few results before and after enabling usingReRank, and confirm that key fragments have not been trimmed out |
| Restricted-major notification | Whether major names, basis for restriction, and acknowledgment receipts are synchronized | Check the names, quantities, and dates in the notification fragments and receipt fragments, and record the number of candidates after similarity filtering |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, rerun retrieval to see whether the version number and references are updated synchronously, and record limit and reference text tokens separately |
Three common errors
- Phenomenon: The major name, quantity, or date for the same candidate does not match across two materials. Cause: The version was not synchronized, and old-version fragments are still recalled and mixed into the candidates.
- Phenomenon: The re-examination application lacks a review signature, or the restricted-major notification lacks a receipt. Cause: When the materials were archived, signed documents were not completed, and retrieval returns only the existing fragments.
- Phenomenon: The answer lacks key paragraphs, and although there are many candidates, the ones ranked at the front are all irrelevant. Cause: The mode does not match the material form, rerank is not enabled, or similarity filtering is too strict.
How to verify the setup
This feature's acceptance: test once each with synonymously rewritten questions, compare the number of candidates and scores, then toggle rerank on and off to observe the ranking of the top few results, and check the three settings searchMode, similarity, and usingReRank.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the knowledge base search test, run one synonymous question each for the physical examination form, re-examination application, and restricted-major notification, record the number of candidates and scores, and confirm that the current version is unique.
- After changing one major name or date, rerun retrieval, check the reference text tokens and array count, and confirm that old versions are traceable and references are synchronized.