What this category's data looks like
Graduate training process management involves materials such as training plans, thesis proposals, and mid-term assessment forms. The training plan is jointly formulated by the supervisor and the school, and includes courses, credits, time arrangements, and signature fields; the thesis proposal records the topic selection, literature review, review comments, and date; the mid-term assessment form summarizes stage results, credit completion status, and assessment conclusions. These materials enter the knowledge base retrieval node in document form, serving as citation sources and the basis for traceability. In terms of update cadence, the training plan is adjusted at the beginning of each semester, the thesis proposal is finalized after the proposal defense, and the mid-term assessment form is archived after the assessment. Field characteristics include student name, student ID, course name, credits, date, signature, and receipt. When the materials enter this function, each plays a different role: the training plan provides the course and credit baseline, the thesis proposal provides the topic selection and review records, and the mid-term assessment form provides the stage conclusions and signature status. Together, the three support consistency verification of versions, connections, and task records in deployment, operations, and application handover.
Configuration and implementation checks
This step is executed by the citation output of the knowledge base retrieval node, which outputs an array of citation content, each containing an original text snippet and a source identifier, and the length can be 0. The handover-ready deployment status and operation records are then completed by subsequent AI nodes, code nodes, or manual work.
| Object | Check | Verification action |
|---|---|---|
| Training plan | Whether the course name, credits, date, and signature fields are consistent with the thesis proposal and mid-term assessment form | Open the citation marker and compare the course name, credits, date, and signature item by item; check whether the number of citations in responseData (non-streaming module results returned with detailed output enabled) matches the hit materials |
| Thesis proposal | Whether the topic title, review comments, date, and signature or receipt match the training plan and mid-term assessment form | Open the citation marker in the conversation and verify the topic title, review date, and signature against the source document; record the length of the citation array |
| Mid-term assessment form | Whether the stage results, credit completion status, assessment conclusion, and date are consistent with the training plan and thesis proposal | Check the mid-term assessment form fields, date, and signature item by item according to the handover checklist; check whether the citation snippets in quoteList can point back to the original paragraphs |
| Knowledge base retrieval node | Whether the associated knowledge base uses the same vector model; whether the search parameter values are consistent with the knowledge base retrieval section | Check the selected collection and vector model in the node; open the search parameter panel and verify each item; run a test query with no matching materials and see whether the output is empty while the chain continues |
Three common errors
- Symptom: The course name, credits, or date for the same record do not match between the training plan and the mid-term assessment form. Cause: The two materials were entered separately and no field comparison was performed; although the citation snippets can point back to the original text, the materials were not synchronized.
- Symptom: The thesis proposal version is not synchronized, and the citation marker points to an old version of the review comments. Cause: Multiple versions were retained in the knowledge base, retrieval hit the old version of the material, and verification was not performed against the latest version.
- Symptom: The mid-term assessment form lacks a signature or receipt, but the citation array still returns snippets. Cause: The signature field is empty but the text exists; after retrieval hit, the signature status was not checked item by item according to the handover checklist.
How to verify the setup
Acceptance of this function: ask a question with source-text support and check whether the citation array and citation markers can point back to the original text; then ask a question with no matching materials and confirm that the array is empty while the chain runs through. The number of citations is the array length, and quoteMaxToken is the citation content budget; the two are not compared for equality. If a citation limit is involved, check the tokens of the citation text, and record the array count separately.
Business testing: check item by item once according to the handover checklist and see which record is missing. Verify whether versions, connections, and task records are consistent, and confirm that the handover-ready deployment status and operation records are complete.
- Open the citation marker, check against the source document whether each citation can point back to the original paragraph, and record the citation array length and the count in
responseData. - Run a test query with no matching materials to confirm that the output is empty while the chain continues; open the search parameter panel and verify item by item whether the values are consistent with the knowledge base retrieval section.