What this category's data looks like
This page addresses knowledge base retrieval and recall in student disciplinary action and appeal handling scenarios. Material sources include disciplinary fact materials, disciplinary decision documents, appeal statements, and deployment status and operation records. Disciplinary fact materials provide the original facts and dates, disciplinary decision documents give conclusions and signatures, appeal statements carry objections and receipts, and operation records reflect versions and tasks. When materials enter the retrieval function, each participates in recall as a candidate fragment and does not directly generate statistical tables or business documents. The update cadence follows material archiving and version synchronization, and field characteristics center on whether names, quantities, dates, signatures, and receipts are consistent.
Configuration and implementation checks
This stage is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate fragments and similarity scores (after pattern, merge, re-rank, filter, and upper-limit trimming). The handover-ready deployment status and operation records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Disciplinary fact materials | Names, quantities, and dates correspond consistently with the disciplinary decision documents, and signatures are complete | In the search test, switch searchMode to semantic, full-text, or hybrid, compare candidate fragments and scores, and check the material fields |
| Disciplinary decision documents | The conclusion date does not conflict with the appeal statement receipt date, and signatures and receipts are not missing | Check whether the returned candidates include both semantic and full-text results, record the number of candidates and scores, and check signatures and receipts |
| Appeal statements | The name, quantity, and date of the same record are consistent across both materials, and the version has been synchronized | Compare the order of the top few results before and after enabling re-rank, verify with the usingReRank switch, and check the cited text tokens and array count |
| Deployment status and operation records | Versions, connections, and task records are consistent across all three, and missing items can be located | Check item by item against the handover list, record the number of candidates and scores, and check the returned content under the similarity and limit settings |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the disciplinary fact materials and the disciplinary decision documents. Cause: Field comparison was not performed during material archiving, and key fragments of the original text were not checked after candidate recall.
- Symptom: The appeal statement version is not synchronized, and receipts are missing. Cause: Operation records were not updated with the materials, old fragments were still recalled during retrieval, and similarity filtering did not expose the missing items.
- Symptom: There are many candidates, but the ones ranked at the top are all irrelevant. Cause: The retrieval mode does not match the material form, re-rank was not enabled, or the similarity filter and citation upper limit were not adjusted.
How to verify the setup
Acceptance for this feature: Test once each with synonym-rewritten questions, compare candidates and scores, then toggle re-rank on and off to observe the ordering of the top few results; check the number of returned candidates and scores under searchMode, usingReRank, similarity, and limit.
Business test: Check item by item against the handover list once to see which record is missing; confirm that versions, connections, and task records are consistent across all three, and document any missing items.
- In the search test, switch the retrieval mode, compare candidate fragments and similarity scores, and record the number of candidates and scores.
- Check the cited text tokens and array count, check whether signatures and receipts are complete, and after confirming version synchronization, hand over to operations or the next shift.