What this category's data looks like
This page focuses on the external service entry points and authorization scope for student status changes and graduation eligibility review. The materials come from three types of records: leave-of-absence and return-to-study applications, major transfer applications, and graduation review checklists. Leave-of-absence and return-to-study applications provide the reason for the change, effective date, and approval signature; major transfer applications provide the names of the transfer-in and transfer-out programs, course counts, and dates; graduation review checklists provide the graduation eligibility conclusion and receipt. The three types of materials update at different rhythms: change applications follow the approval workflow, major transfer applications follow semester batches, and graduation review checklists are generated in a concentrated way during graduation season. After the materials enter the knowledge base retrieval service, each plays a different role: leave-of-absence and return-to-study applications and major transfer applications serve as candidate fragments for the basis of the change, while graduation review checklists serve as candidate fragments for the eligibility conclusion. If the name, count, or date of the same record do not match across two materials, if versions are not synchronized, or if a signature or receipt is missing, the externally visible scope and authorization determination will deviate.
Configuration and implementation checks
This step is performed by the knowledge base retrieval service (retrieval node and search test), which outputs candidate fragments and similarity scores (after pattern, merge, rerank, filter, and limit trimming). The externally available entry points and authorization scope are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Leave-of-absence and return-to-study application | Whether the reason for the change, effective date, and approval signature are complete, and whether the name and date of the same record match those in the major transfer application | In the knowledge base search test, test once each with synonymous questions, switch searchMode to semantic, full-text, or hybrid, record the number of candidates and scores, and check the signature and receipt fields |
| Major transfer application | Whether the transfer-in and transfer-out names, course counts, and dates match the graduation review checklist, and whether versions are synchronized | Compare the ranking of the top few results before and after enabling usingReRank, check whether the candidate fragments include both semantic and full-text results, and record the number of candidates after similarity filtering |
| Graduation review checklist | Whether the graduation eligibility conclusion, receipt, and signature are complete, and whether the tokens of the quoted text still retain key passages after limit trimming | Access once with a restricted identity, see whether the visible scope matches the setting, record the number of items in the citation array separately, and do not compare the number of items as equal to the citation content budget |
Three common errors
- Symptom: The name and date of the same student do not match between the leave-of-absence and return-to-study application and the major transfer application. Cause: The two materials are generated by different nodes, and hit and association checks were not performed, causing the externally visible scope to deviate.
- Symptom: The version of the graduation review checklist is not synchronized, and an old receipt is still recalled. Cause: The materials update at different rhythms, and retrieval did not filter by the latest version, so historical records were mixed into the candidate fragments.
- Symptom: The major transfer application lacks a signature or receipt, but the external service still shows it as queryable. Cause: The authorization determination only checked identity and not material completeness, so the unauthorized visible scope was not blocked.
How to verify the setup
This feature acceptance: test once each with synonymously rewritten questions, compare candidates and scores, then toggle rerank to see the ranking of the top few results; switch searchMode and similarity, and record the number of candidates and scores.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and ensure unauthorized content is not visible.
- In the knowledge base search test, switch
searchModeto semantic, full-text, or hybrid, compare candidate results, and record the number of candidates and scores. - Compare the order of the top few results before and after enabling
usingReRank, and check whether the tokens of the quoted text afterlimittrimming retain key passages.