What this category's data looks like
This page focuses on exception tracing and manual review in degree conferral and certificate information reporting. The core materials include three types: degree application forms, thesis review forms, and defense resolutions. The degree application form carries the applicant's basic information, course grades, and degree category fields; the thesis review form records the reviewers, review comments, and review dates; the defense resolution records the defense committee members, voting results, defense date, and signatures. Before reporting, the three types of materials must undergo consistency checks on fields, dates, and signatures. Common inconsistencies manifest as mismatches in names, quantities, and dates for the same record across two materials, versions not synchronized, and missing signatures or receipts. When materials enter this feature, each is associated with the knowledge base as an independent document. The retrieval node recalls original text fragments according to the set selected by the vector model. The citation output provides a traceable source basis for subsequent comparison. The exception list and review conclusions are generated by subsequent nodes or manually based on this. The update cadence depends on reporting batches and material revisions. Field characteristics center on names, student IDs, degree categories, dates, signatures, and receipt numbers.
Configuration and implementation checks
The citation output of the knowledge base retrieval node outputs only an array of cited content, each entry containing an original text fragment and a source identifier. The length can be 0. The exception list and review conclusions must be handled subsequently by AI nodes, code nodes, or manually. The cited content is output as an array, and the length can be 0; even if no content is found, the output pipeline still completes.
| Object | Check | Verification action |
|---|---|---|
| Degree application form | Check whether the applicant's name, student ID, degree category fields, signature date, and signature are complete | Open the citation marker, compare field by field against the source document, and record the discrepancy location and original text fragment |
| Thesis review form | Check whether the reviewer's name, review comments, review date, and signature are consistent with the application form | Check the citation array length and the source identifier in responseData (non-streaming module results returned with detailed output enabled), and trace back to the original paragraph to confirm the fields |
| Defense resolution | Check whether the defense committee members, voting results, defense date, signature, and receipt are complete | Expand the cited fragments one by one, and compare the names, quantities, and dates of the same record across the two materials |
| Citation output pipeline | Confirm that the number of citations matches the hit materials; empty is also normal | Run a test with a question that has no matching materials, observe that the array is empty while the pipeline continues, and check quoteMaxToken and quoteList |
Three common errors
- Symptom: The name and date of the same record do not match between the degree application form and the defense resolution. Cause: The two materials were entered separately without cross-checking, and versions were not synchronized.
- Symptom: The thesis review form is missing the reviewer's signature or receipt number. Cause: The signature page was not collected during material circulation, and item-by-item verification was not performed before reporting.
- Symptom: The answer has no citation marker, and the cited fragment does not match the original text. Cause: No corresponding material was hit in this round, or after hitting the material, the original paragraph was not traced back according to the source identifier.
How to verify the setup
Acceptance of 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 pipeline completes.
Business test: Create an exception record and see whether it can be traced to the source material
- In the node, check whether the selected knowledge base collections and their vector models are consistent, and open the search parameter panel to check the values item by item
- Run a test with a question that has no matching materials, confirm that the citation array is empty while the pipeline continues, and separately record the array length and the tokens of the cited text