What this category's data looks like
This page addresses the degree conferral and certificate information reporting scenario; materials include degree application forms, thesis review forms, defense resolutions, etc. The degree application form records the applicant's basic information, discipline and major, and degree type; the thesis review form carries review comments and conclusions; the defense resolution reflects the voting result and signatures. After these materials enter the dialogue and retrieval functions, the degree application form serves as the identity and application basis, the thesis review form serves as the academic evaluation basis, and the defense resolution serves as the procedural compliance basis. The material update cadence is synchronized with degree conferral batches, and field characteristics are concentrated in name, student ID, thesis title, date, signature, quantity, etc. The same record may show inconsistent names, quantities, or dates across different materials, with versions not synchronized or missing signature receipts. Business basis query requires model access and configuration so that dialogue and retrieval can refer back to the original entries.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, which outputs model binding relationships and channel responses. The basis entries that can refer back to the original text are completed subsequently by AI nodes, code nodes, or manual work. Models are divided into five categories: language, indexing, reranking, speech synthesis, and speech recognition; different steps bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Degree application form | Whether fields, dates, and signatures correspond with the thesis review form and defense resolution | Check name, student ID, thesis title, date, and signature; check whether the name and quantity of the same record are consistent; confirm the version is current |
| Thesis review form | Whether review comments, conclusions, and dates are consistent with the defense resolution | Check the review conclusion, review date, signature or receipt; check whether the name and quantity of the same record match across the two materials |
| Defense resolution | Whether the voting result, date, and signature are complete and consistent with the application form | Check the voting result, defense date, and signature; check for missing signatures or receipts; confirm that when versions are not synchronized, the current material prevails |
| Model configuration | The model type corresponds to the step to be used, and the model identifier matches the name listed in the documentation | In the model configuration, check the type label; compare it against the model name returned by the channel; check whether maxContext, maxTokens, quoteMaxToken, and toolChoice are bound according to the step |
Three common errors
- Symptom: The name, quantity, or date of the same record do not match between the degree application form and the thesis review form. Cause: The materials are filled in separately, without cross-material verification.
- Symptom: The defense resolution version is not synchronized, and an old conclusion is cited. Cause: After the material was updated, the current version was not replaced, and retrieval still returns the old entry.
- Symptom: The thesis review form is missing a signature or receipt. Cause: The process is not closed-loop; signatures and receipts were not archived, resulting in incomplete basis.
How to verify the setup
This feature acceptance: run one dialogue and one retrieval, check the model identifier in the response, confirm the model type corresponds to the step, and check whether maxContext, maxTokens, quoteMaxToken, and toolChoice take effect as configured.
Business test: ask a cross-material basis question, see whether the answer provides a citable source, and check that the citation count and citation text tokens are recorded separately.
- Check the channel configuration and key source, confirm the channel is consistent with the connected service, and the model identifier matches the name listed in the documentation.
- Check the material fields, dates, and signatures, confirm the name, quantity, and date of the same record are consistent, the version is current, and signatures and receipts are complete.