What this category's data looks like
This category of pre-departure training and overseas safety reminders includes three types of materials: pre-departure training courseware, safety reminder checklists, and accommodation contact sheets. The courseware carries the training topics and schedule, the safety checklist carries risk items and response actions, and the accommodation sheet carries contacts, addresses, and check-in dates. Material sources are dispersed: the courseware is maintained by the training team, the checklist by the safety team, and the accommodation sheet by the logistics team, and the three often reference the same set of student names, flight numbers, and emergency phone numbers. The update cadence follows semesters and batches: each batch is finalized two weeks before departure, and patches are applied after departure according to change orders. Field characteristics center on names, quantities, dates, signatures, and acknowledgments: the same student must have the same name and date in the courseware roster, the checklist acknowledgment, and the accommodation sheet. After entering the knowledge base retrieval node, the courseware, checklist, and accommodation sheet are each selected as independent knowledge bases, and the node is only responsible for returning the hit original text fragments and source identifiers as an array; it is not responsible for comparing fields or writing ledgers.
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 can be 0. The "version ledger and change records" are then completed by subsequent AI nodes, code nodes, or manual work.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Whether the student roster, flight dates, and signature fields in the courseware have the same names and dates as the accommodation contact sheet | Open the citation corner mark to compare against the original courseware paragraphs, and compare names, quantities, dates, and signatures item by item |
| Safety reminder checklist | Whether the signature and date on the checklist acknowledgment are consistent with the courseware schedule and the accommodation sheet check-in date | Use a question to hit a checklist fragment, and check whether the original text fragment in responseData (non-streaming module results returned with detailed output enabled) can point back to the checklist paragraph |
| Accommodation contact sheet | Whether the contact person, address, and check-in date on the accommodation sheet are synchronized with the version numbers of the courseware and checklist | After changing one date, rerun and see whether the number of citation array entries and the quoteList source identifier point to the new version |
| Knowledge base retrieval node | Whether the selected knowledge bases use the same vector model, and whether the citation array length is consistent with the hit materials | Try running a question with no matching materials, see whether the output is empty while the chain runs through, and check the quoteMaxToken budget |
Three common errors
- Symptom: the same student's name is written differently in the courseware roster and the accommodation sheet. Cause: the two materials are maintained by different teams, were not entered according to the same field template, and the versions were not synchronized.
- Symptom: the safety checklist acknowledgment is missing a signature or the date is left blank. Cause: after the acknowledgments were collected, they were not written back to the ledger, and the old checklist version is still being hit in the knowledge base.
- Symptom: the cited fragment does not match the original text. Cause: first check whether this round hit anything and which material was hit, then check trimming, and do not directly attribute it to length trimming.
How to verify the setup
Acceptance for this feature: ask a question with original-text support and check whether the citation array and corner marks can point back to the original text; then ask a question with no matching materials, confirm that the array is empty while the chain runs through, record the count separately, and only check the tokens of the cited text for quoteMaxToken.
Business test: change one piece of content and see whether the version number and citations update synchronously
- In the node, check the selected knowledge base collections and their vector models, open the search parameter panel, and verify the values item by item
- In the conversation, open the citation corner marks, compare against the source documents, and confirm that each citation can point back to the original text paragraph