What this category's data looks like
The materials of primary and secondary school admissions organizations mainly consist of admission plans, application material checklists, and admission lists, with fields including name, quantity, date, and signature. The admission plan explains the admission scope and process, the application material checklist lists the documents and forms that parents need to submit, and the admission list records student names, numbers, and admission results. When these three types of materials enter the knowledge base retrieval node, each is cited as an independent source: the plan provides the rule basis, the checklist provides the material verification criteria, and the list provides result traceability. In terms of update rhythm, the plan is revised when policies are adjusted, the checklist is supplemented with each application batch, and the list is released in batches according to admission progress. A common field characteristic is that the same record has inconsistent name spellings, quantity criteria, and date formats across different materials; when versions are not synchronized, the old version is still in the knowledge base, and missing signatures or receipts prevent the source from being closed-loop.
Configuration and implementation checks
This step is executed by the citation output of the knowledge base retrieval node, which outputs an array of cited content, each item containing the original text fragment and source identifier, and the length can be 0. "Externally available entry points and authorization scope" are completed subsequently by AI nodes, code nodes, or manual work.
| Object | Check | Verification action |
|---|---|---|
| Admission plan | Check whether the admission scope, process nodes, and signature fields in the plan are consistent with the names, quantities, and dates in the application material checklist and admission list | Open the citation marker to point back to the original paragraph of the plan, compare the plan version number with the checklist batch date; record the number of items in the citation array and the quoteMaxToken budget |
| Application material checklist | Check whether the document names, copy counts, submission dates, and receipt fields listed in the checklist are consistent with the plan requirements and list records | Access once with a restricted identity, check whether the checklist fragment is within the visible range; verify the source identifier of each citation in responseData (non-streaming module results returned with detailed output enabled) |
| Admission list | Check whether the student names, numbers, and admission dates in the list match the plan batch and checklist receipts | Open the citation marker to compare with the original text of the list, check whether signature or receipt fields are missing; check whether the cited fragments in quoteList and the original paragraphs point back to each other |
| Associated knowledge base | Check whether the selected knowledge bases use the same vector model, to avoid mixing sources from different models into the citation array | In the node, verify the selected collections and their vector models, and run a test question with no matching materials to see whether the output is empty while the chain continues |
Three common errors
- Phenomenon: The same student's name spelling or number does not match between the admission plan and the admission list. Cause: The two materials are maintained separately, no field-level comparison has been done, and versions are not synchronized.
- Phenomenon: The number of document copies listed in the application material checklist is inconsistent with the quantity required by the plan, and parents are rejected after submitting according to the checklist. Cause: After the checklist was revised, the old version of the plan is still in the knowledge base, and citations hit the old version.
- Phenomenon: The admission list lacks signatures or receipts, and the source cannot be closed-loop. Cause: When the list is released in batches, the signature fields are not synchronized and completed, and the cited fragments only cover the main text.
How to verify the setup
Acceptance for this feature: ask a question with an original text basis, and check whether the citation array and markers can point back to the original text; then ask a question with no matching materials, and confirm that the array is empty while the chain runs through.
Business test: access once with a restricted identity, see whether the visible range matches the setting, and unauthorized content is not visible.
- Open the search parameter panel and check the values item by item, record the number of items in the citation array, and separately check the tokens of the cited text and the
quoteMaxTokenbudget, without making an equality comparison. - Open the citation markers in the conversation, compare with the source documents, check whether each citation can point back to the original paragraph, and verify the source identifiers in
quoteListwithinresponseData.