What this category's data looks like
Course scheduling and course consumption materials at training institutions include class schedules, course consumption records, schedule change requests, as well as deployment status and operation records. Class schedules contain course name, class, teacher, classroom, week number, and period; course consumption records contain student, course, date, number of class hours, and signature; schedule change requests contain the original class session, target class session, reason, and approval receipt. Sources are academic affairs system exports and paper signed documents; the update cadence advances by scheduling week and course consumption day, and version numbers and export times must be kept in sync. When entering the knowledge base retrieval and recall feature, class schedules and course consumption records serve as candidate chunk sources, schedule change requests serve as the association basis, and deployment status and operation records serve as handover form check items. Field characteristics are three types: date, quantity, and signature. If the name, quantity, or date of the same record do not match across two materials, the version is not synchronized, or the signature or receipt is missing, all of these will enter the candidate and cited content, and must be checked item by item in the retrieval node and search test.
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 pattern, merge, rerank, filter, and limit trimming). The handover-ready deployment status and operation records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Fields contain course name, class, teacher, classroom, week number, and period; date and signature must be consistent with the schedule change request | In the search test, switch searchMode to semantic, full-text, or hybrid, compare the number of candidates and scores, and check the class schedule date and signature |
| Course consumption record | Fields contain student, course, date, number of class hours, and signature; quantity and date must correspond one by one with the class schedule | Test once each with synonym-rewritten questions, see whether the candidates include both semantic and full-text results, and check the course consumption quantity and signature |
| Schedule change request | Fields contain original class session, target class session, reason, and approval receipt; receipt and date must be synchronized with the class schedule | Turn usingReRank on and off, compare the ordering of the first few items, and check the schedule change receipt and version number |
| Deployment status and operation records | Version, connection, and task records are consistent, serving as item-by-item check items on the handover form | Check item by item once according to the handover form to see which record is missing; record the number of candidates and scores, and when the citation limit is involved, check the tokens of the cited text, recording the number of array items separately |
Three common errors
- Symptom: The name, quantity, or date of the same record do not match between the class schedule and the course consumption record. Cause: The two export times differ, the versions are not synchronized, and candidate chunks are mixed.
- Symptom: The schedule change request lacks a signature or receipt, and the handover form is missing an item. Cause: The approval process is not closed-loop, paper documents are not collected, and retrieval still returns candidates.
- Symptom: The same question cannot be recalled when rephrased, and although there are many candidates, the ones ranked at the front are all irrelevant. Cause:
searchModedoes not match the material form,usingReRankis not enabled, or thesimilaritythreshold is inappropriate.
How to verify the setup
Acceptance of this feature: test once each with synonym-rewritten questions, compare the number of candidates and scores, then turn rerank on and off to see the ordering of the first few items, and check searchMode, similarity, usingReRank, and limit.
Business test: check item by item once according to the handover form to see which record is missing, and confirm that version, connection, and task records are consistent.
- In the knowledge base search test, switch
searchModeto semantic, full-text, or hybrid, compare candidate results, and record the number of candidates and scores. - Turn
usingReRankon and off, compare the order of the first few items, and check the trimming effect ofsimilarityandlimit.