What this category's data looks like
Admissions enrollment filing materials for general higher education institutions mainly consist of enrollment plans, filing rules, and admission rosters. The sources are provincial examination authorities and university admissions offices, and the update cadence changes with batch progression, plan adjustments, and changes in volunteer collection. Enrollment plans include institution-major groups, selected examination subjects, planned numbers, tuition, and campus location; filing rules include filing ratios, tie-breaking ranking, major allocation, and withdrawal conditions; admission rosters include candidate number, name, score, major, and admission status. After these three types of materials enter the knowledge base, each assumes a different role: enrollment plans and filing rules serve as rule bases to support retrieval, while admission rosters serve as result records to support verification. Fields, dates, signatures, and receipts must be aligned item by item. The name, quantity, and date of the same record in two materials must be consistent. Version changes must leave a trace, old versions must be traceable, and citations must be updated in sync.
Configuration and implementation checks
This step is executed by the indexing service and vector database, outputting vectors and index status (whether recall is possible and 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 |
|---|---|---|
| Enrollment plan | Check institution-major groups, selected examination subjects, planned numbers, tuition, and campus location, and confirm that fields are consistent with dates and signatures | In the knowledge base settings, check the indexing model, open a data row to check the index fields, and confirm that multiple vector identifiers for one data record are all present and the status is indexed |
| Filing rules | Check filing ratios, tie-breaking ranking, major allocation, and withdrawal conditions, and confirm that the version number and citations are updated in sync | View the data scope covered by the rebuild task, and confirm that after changing the model, it is triggered only for data that has already been indexed, and that old versions are traceable |
| Admission roster | Check candidate number, name, score, major, and admission status, and confirm that names, quantities, and dates match | Run a retrieval to see whether data in the same group is merged. If duplicate entries appear, return to the original data to check the index fields |
| Version ledger and change records | Confirm that the current version is unique, old versions are traceable, and citations are updated in sync, and record the change date and signature receipt | After changing one piece of content, check whether the version number and citations are updated in sync, and verify the coverage scope in the rebuild task records |
Three common errors
- Symptom: the name, quantity, and date of the same record in two materials do not match. Inspect the following: enrollment plans and admission rosters are maintained separately, changes are not synchronized, and versions are not unified.
- Symptom: duplicate entries appear in retrieval results. Inspect the following: one data record corresponds to multiple vector identifiers, data in the same group is not merged by highest score, and index field records are incomplete.
- Symptom: a data row has content but cannot be retrieved. Inspect the following: after changing the model, recall quality decreases, the rebuild task covers only data that has already been indexed, and old versions are not traced.
How to verify the setup
This feature's acceptance: sample a data row to check the index fields, confirm that multiple vector identifiers are all present and the status is indexed, then run a retrieval to see whether the same group is merged; check that limit are only for budget reference, and the number of citations is recorded separately by array length.
Business test: change one piece of content, see whether the version number and citations are updated in sync, and verify the coverage scope in the rebuild task records.
- In the knowledge base settings, check that the indexing model is consistent with the vector model actually used by the knowledge base, open a data row to check the index fields, and confirm that the status is indexed.
- View the data scope covered by the rebuild task records, and confirm that after changing the model, it is triggered only for data that has already been indexed, old versions are traceable, and citations are updated in sync.