What this category's data looks like
This page is intended for primary and secondary school admissions organizations; the materials include admissions plans, application material checklists, and admission lists. Admissions plans are published by academic year or batch, and include admission targets, time nodes, and procedures; application material checklists are updated as policies are adjusted, and include fields such as household registration, property, and residence permit, as well as signature fields; admission lists are publicly announced by batch, and include name, last four digits of the ID number, admission result, and receipt. The three types of materials have different roles when entering the knowledge base: the admissions plan serves as the main retrieval backbone, the application material checklist serves as the basis for condition verification, and the admission list serves as the working draft for result comparison. The update rhythm is driven by notices from the education authorities; it is common for the same record to have inconsistent names, quantities, and dates across two materials, with versions not synchronized, and missing signatures or receipts. Field characteristics are concentrated in dates, quantities, signatures, and receipts; during retrieval, original text fragments need to be retained for item-by-item verification.
Configuration and implementation checks
This step is performed by the knowledge base retrieval service (retrieval node and search test), outputting candidate fragments and similarity scores (after pattern, merge, rerank, filter, and limit trimming). The version ledger and change records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Admissions plan | Whether the name, date, and signature of the same batch plan are consistent across the two materials | In the knowledge base search test, switch searchMode, and verify the plan name, publication date, and signature field in the candidate fragments |
| Application material checklist | Whether the checklist fields and quantities match across the two materials, and whether the versions are synchronized | Test once each with synonymous questions, compare the number of candidates and scores, and check whether the checklist fields and quantities are consistent |
| Admission list | Whether the names, quantities, dates, and receipts in the list match the plan and checklist | Verify the list records and receipt marks in the candidate fragments, and confirm that old versions are traceable and references are synchronized |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | Adjust similarity and limit, observe changes in the number of candidates and scores, then toggle usingReRank to compare the ranking of the top few results |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the admissions plan and the application material checklist. Cause: The versions are not synchronized, and old-version fragments are still recalled and enter the candidates.
- Phenomenon: The quantities and dates in the admission list and the plan are inconsistent, and signatures or receipts are missing. Cause: After the materials were updated, they were not written back to the knowledge base, and the referenced content was not synchronized.
- Phenomenon: There are many candidates, but the ones ranked at the front are all irrelevant, and the answer lacks key paragraphs. Cause: The retrieval mode does not match the material form, and reranking or similarity filtering was not performed.
How to verify the setup
This feature acceptance: test once each with synonymously rewritten questions, compare candidates and scores, then toggle reranking to observe the ranking of the top few results; record the number of candidates and scores, and when reference limits are involved, check the tokens of the referenced text, and record the number of array items separately.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the knowledge base search test, switch
searchMode, and compare the number of candidates and scores across the three modes: semantic, full-text, and hybrid. - Adjust
similarityandlimit, toggleusingReRank, and verify whether the candidate fragments retain the key original fields and signature receipts.