What this category's data looks like
This page addresses exam organization and violation handling scenarios. Material sources include exam administration manuals, examination room record sheets, and violation fact records, with updates rolling forward according to exam batches and sessions. Exam administration manuals provide process and rule fields; examination room record sheets carry time, examination room, invigilation, and candidate behavior records; violation fact records describe facts, evidence, and handling opinions. When entering the knowledge base retrieval and recall function, exam administration manuals are split into candidate chunks as rule basis, while examination room record sheets and violation fact records are split into candidate chunks as factual materials. All three participate jointly in recall, but each has a different role: manual chunks are used for rule comparison, record sheet chunks are used for time and examination room verification, and violation record chunks are used for fact and signature verification. Field characteristics center on names, quantities, dates, and signatures. Versions update with batches, and item-by-item comparison is required during handover.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate chunks and similarity scores (after mode, merge, re-rank, filter, and limit trimming). The handover-ready deployment status and operation records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Exam administration manual | Fields, dates, and signatures must be consistent with the examination room record sheet, and versions must be synchronized | Switch searchMode in the search test, and verify the rule names, dates, and signature fields in the candidate chunks |
| Examination room record sheet | The name, quantity, and date of the same record must match across both materials | Test once each with synonymous questions, check the number of candidate entries and the similarity score, and record the array length |
| Violation fact record | If signatures or receipts are missing, it must not be used as a handover basis | Compare the top few rankings before and after toggling usingReRank, and verify the fact, evidence, and signature fields |
| Deployment status and operation records | Version, connection, and task records must be consistent | Verify item by item according to the handover sheet, and record the number of candidate entries, scores, and the quoted text after limit trimming |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match across the two materials. Cause: The examination room record sheet and violation fact record were entered separately, without item-by-item comparison against the exam administration manual fields.
- Symptom: Versions are not synchronized, and the manual and record sheet batches are inconsistent during handover. Cause: The deployment status and operation records were not updated with the batch, and retrieval candidates still come from old chunks.
- Symptom: Signatures or receipts are missing, so the violation fact record cannot serve as a handover basis. Cause: The signature fields and receipt fields were not retained when the materials entered the knowledge base, and retrieval candidates lack key chunks.
How to verify the setup
Acceptance for this function: test once each with synonymously rewritten questions, compare the candidate chunks and similarity scores, then toggle usingReRank to observe changes in the top few rankings.
Business test: verify item by item once according to the handover sheet, see which record is missing, and check whether version, connection, and task records are consistent.
- Switch
searchModein the search test, record the number of candidate entries and scores, record the array length separately, and do not compare the number of entries as equal to the citation budget. - Verify the tokens of the quoted text and the
limittrimming result, confirm that version, connection, and task records are consistent, then hand over to operations or the next shift.