What this category's data looks like
In the scheduling and class-consumption scenario of training institutions, there are three core types of materials: class schedules, class-consumption records, and schedule-change requests. Class schedules are generated by the academic affairs staff during scheduling, with fields including course name, class, teacher, class date, and time slot; class-consumption records are filled in by the subject teacher or academic affairs staff after class, with fields including student name, course name, consumed quantity, class date, and signature; schedule-change requests are initiated by the teacher or academic affairs staff, with fields including the original class date, adjusted date, reason for adjustment, and approval signature. The three types of materials update at different rhythms: class schedules are generated in batches weekly or monthly, class-consumption records are produced entry by entry per session, and schedule-change requests are submitted at any time as needed. When the materials enter the knowledge base retrieval node, each is indexed as an independent document or segment, and during retrieval the original text fragments and source identifiers are returned by vector similarity. For the same student, same course, and same date, the names, quantities, and dates in the class schedule, class-consumption record, and schedule-change request need to be compared field by field, with signatures and receipts serving as the basis for completeness.
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 entry containing an original text fragment and a source identifier, and the length may be 0. The discrepancy list is then completed by a subsequent AI node, code node, or manually. The citation array itself is not a discrepancy list, ledger, or report; the count is the array length, and quoteMaxToken is the citation content budget, and the two are not compared for equality.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Whether the course name, class, teacher, class date, and time slot are consistent with the class-consumption record | Locate the class schedule source fragment in the citation array, transcribe the course name, class, and date field by field, and compare with the class-consumption record citation fragment |
| Class-consumption record | Whether the student name, course name, consumed quantity, class date, and signature are consistent with the class schedule and schedule-change request | Open the citation superscript to point back to the original class-consumption record text, verify the consumed quantity and signature field, and record the fields inconsistent with the class schedule |
| Schedule-change request | Whether the original class date, adjusted date, reason for adjustment, and approval signature are synchronized with the class schedule and class-consumption record | Find the schedule-change request source identifier in the citation array, verify whether the adjusted date has been written back to the class schedule, and check the signature and receipt |
| Knowledge base retrieval node | Whether the associated knowledge bases use the same vector model, and whether the number of cited content outputs matches the hit materials | Open the node configuration to verify the selected knowledge base collections and vector model, run a test with a question that has no matching materials, and observe the citation array length in responseData (non-streaming module results returned with detailed output enabled) and quoteList |
Three common errors
- Symptom: The course name or consumed quantity for the same student does not match between the class schedule and the class-consumption record. Cause: The two materials are filled in by different roles at different times, and the naming conventions and counting conventions are not unified.
- Symptom: The schedule-change request has been submitted, but the class schedule still shows the original class date, and the class-consumption record is filled in according to the original date. Cause: The versions are not synchronized, the adjusted date has not been written back to the class schedule, and retrieval hits the old version fragment.
- Symptom: The class-consumption record lacks the teacher's signature or the schedule-change request lacks the approval receipt, and the citation fragment cannot prove that the operation was completed. Cause: The signature and receipt were not uploaded together with the materials or were not indexed, and the corresponding source identifier is missing from the citation array.
How to verify the setup
Acceptance of this feature: ask a question with original text evidence, and verify whether the citation array and superscripts can point back to the original text; then ask a question with no matching materials, and confirm that the array is empty while the pipeline runs through. Check the citation array length in responseData, record the count separately, and do not compare the count with quoteMaxToken for equality; open quoteList to verify the source identifier of each citation.
Business test: use a real record to find fields inconsistent with the ledger. Take a class-consumption record, locate the class schedule fragment and schedule-change request fragment in the citation array, compare the course name, consumed quantity, and class date field by field, write the mismatched fields into the discrepancy list, and submit it to the reviewer for confirmation and write-back.
- Open the knowledge base retrieval node, verify whether the selected knowledge base collections and their vector models are consistent, and check the values in the search parameter panel item by item.
- Open the citation superscripts in the conversation, check against the source documents whether the citation fragments correspond to the original paragraphs, and record the relationship between the citation array count and the hit materials.