What this category's data looks like
Admission and filing materials for general higher education institutions include enrollment plans, filing rules, and admission rosters, originating from provincial admissions and examination institutions and university admissions offices, updated on a rolling basis by batch and round, with fields including institution-major group, planned number, filing ratio, candidate number, score rank, admission status, and signature field. Enrollment plans and filing rules enter this feature as retrieval evidence, used to compare filing conditions and plan criteria; admission rosters serve as result materials, used to check whether filing results correspond to roster records. During the deployment, operations, and application handover stage, the three materials respectively assume the roles of rule source, plan baseline, and result voucher, and the retrieval node recalls candidate segments accordingly, for subsequent nodes or manual staff to generate handover-ready deployment status and operation records.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate segments and similarity scores (after pattern, merge, re-rank, filter, and limit trimming). The handover-ready deployment status and operation records are then completed by subsequent nodes or manual staff.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | Planned number, institution-major group name, date, and signature are consistent between the plan table and the filing rules | In the search test, run one search each with synonymous questions, check the planned number and date in the candidate segments, record the number of candidates and scores, and check whether searchMode is hybrid |
| Filing rules | Filing ratio, batch, and effective date match between the two materials, and the version has been synchronized | Switch searchMode to semantic and full-text and run one search each, see whether the candidates include both types of results, enable usingReRank and compare the order of the top few results |
| Admission roster | Candidate number, score rank, admission status, and signature or receipt are complete, and name, quantity, and date do not conflict | Check the roster against the filing results item by item according to the handover form, check the tokens of the quoted text after similarity filtering, record the array count separately, and do not write the three-state index |
| Deployment status and operation records | Version, connection, and task records are consistent, and missing items can be traced to specific materials | Check the retrieval node connection and task records, see whether the candidates and quoted content cover the key paragraphs, and record the number of candidates after limit trimming |
Three common errors
- Symptom: the name or date for the same candidate number does not match between the admission roster and the filing results. Cause: the two materials' versions are not synchronized, and retrieval recalls candidate segments from only one of them.
- Symptom: the planned number is inconsistent between the enrollment plan and the filing rules. Cause: the rule material was not updated after the plan adjustment, the signature or receipt is missing, and the candidate segments cannot corroborate each other.
- Symptom: the same question phrased differently cannot be recalled, and although there are many candidates, the top-ranked ones are all irrelevant. Cause: the retrieval mode does not match the material form, re-rank is not enabled, or similarity filtering is too tight.
How to verify the setup
This feature's acceptance: test once each with synonymously rewritten questions, compare candidates and scores, then toggle re-rank on and off to see the ordering of the top few results, and check the actual behavior of searchMode, similarity, usingReRank, and limit.
Business test: check once item by item according to the handover form, see which record is missing, and confirm whether the fields, dates, and signatures of the enrollment plan, filing rules, and admission roster are complete.
- In the knowledge base search test, switch retrieval modes, compare candidate results and scores, record the number of candidates, and check the tokens of the quoted text without comparing them for equality against the array count.
- Check the deployment status and operation records item by item according to the handover form, confirm that version, connection, and task records are consistent, and annotate missing items to the specific material and signature field.