What this category's data looks like
Vocational school student internship management is structured around three types of materials: internship agreements, internship plans, and internship logs. Agreements define rights, responsibilities, and signatures; plans define positions, cycles, and batches; logs record daily attendance, tasks, and mentor receipts. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures, and the same record often appears across materials. The material update rhythm is: agreements and plans are finalized before batch launch with signature pages retained; logs are appended daily or weekly as attendance occurs; receipts and annotations are backfilled later. When materials enter the knowledge base retrieval node, their respective roles are: agreements as the basis for rights, responsibilities, and deadlines; plans as the basis for positions and batches; logs as the basis for processes and receipts. Together, the three support citation sources and traceability.
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 snippet and a source identifier, and the length can be 0. "Handover-ready deployment status and operation records" are completed subsequently by AI nodes, code nodes, or manual work.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | The three items of name, date, and signature must match the internship plan and internship log | In the node, check the selected collection and its vector model, open each citation marker one by one, and trace back to the original agreement paragraph |
| Internship plan | Position, quantity, and batch date must be consistent with the agreement and log | Run a test with a question that has no matching materials, see whether the citation array is empty while the chain continues, and record the array length |
| Internship log | Attendance date, task name, and mentor receipt must be consistent with the plan and agreement | Open the search parameter panel and check item by item, and verify the tokens of the cited text against the quoteMaxToken budget |
| Citation content output | The number of returned entries matches the hit materials; being empty is also normal | In the conversation, open the citation markers, compare against the source documents, and verify the source identifiers in responseData (non-streaming module results returned with detailed output enabled) and quoteList |
Three common errors
- Symptom: The same student's name and position title do not match between the agreement and the log. Cause: The two materials were entered separately without field comparison, and the name format was not unified.
- Symptom: The plan batch date and the log attendance date are misaligned, and the handover form lacks a date item. Cause: Versions were not synchronized, and old batch materials are still in the knowledge base participating in retrieval.
- Symptom: The log lacks a mentor signature or receipt, and the cited snippet does not match the original text. Cause: Receipts were backfilled late, and the materials hit in the current round were not checked first before attributing the issue to truncation.
How to verify the setup
Acceptance for this feature: ask a question with original-text support and check whether the citation array and markers can trace back to the original text; then ask a question with no matching materials and confirm that the array is empty while the chain still runs through; the number of citations is the array length, and quoteMaxToken is the citation content budget, and the two are not compared for equality.
Business test: check item by item according to the handover form to see which record is missing; verify whether the version, connection, and task records are consistent, and confirm that there are no missing signatures or receipts.
- In the node, check the selected knowledge base collections and their vector models, and confirm that the selected knowledge bases use the same vector model.
- Open the search parameter panel and check item by item, keep them consistent with the values set in the knowledge base retrieval section, and record the array length and the tokens of the cited text.