What this category's data looks like
This page addresses the scenario of self-taught examination registration records and graduation review, involving three types of materials: registration records, course qualification certificates, and graduation application forms. Registration records use the candidate's identity, examination registration number, major name, course scores, and seal date as core fields; they are sourced from provincial registration record database exports and are updated with each examination session. Course qualification certificates record the course code, name, credits, qualification time, and the seal of the examining institution, and are generated by batch. Graduation application forms aggregate the information from the first two types and attach the candidate's photo, ideological and moral character assessment, and three-level signatures. When materials enter the knowledge base retrieval service, they serve respectively as candidate fragment sources: registration records provide the identity and score ledger, course qualification certificates provide single-subject qualification evidence, and graduation application forms provide aggregated fields and the signature chain. The retrieval results are used by subsequent nodes to draft issuable material drafts and handover records; only when fields are complete, responsible parties are clear, and versions and dates are consistent can they pass.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate fragments and similarity scores (after mode, merge, re-rank, filter, and limit truncation). The "issuable material drafts and handover records" are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Registration records | The identity fields, examination registration number, major name, course scores, and seal date must correspond item by item with the course qualification certificates and graduation application forms | In the search test, switch searchMode to semantic, full-text, and hybrid, check whether the candidate fragments cover the identity and score fields, and record the number of candidates and scores |
| Course qualification certificates | The course code, name, credits, qualification time, and seal of the examining institution must be consistent with the registration records, and the quantity and dates must not conflict | Compare the order of the top few items before and after enabling re-ranking, and confirm that after usingReRank is enabled, certificate fragments are prioritized over irrelevant records |
| Graduation application forms | The aggregated fields, photo, assessment opinion, and three-level signatures must be complete, and the version number and date must be synchronized with the registration records and course qualification certificates | Adjust limit to observe whether key fragments for signatures and dates are still retained after reference limit truncation, and separately record the number of array items |
| Retrieval output | Candidate fragments and similarity scores are delivered after mode, merge, re-rank, filter, and limit truncation | Check the candidate score distribution under the similarity filter threshold, and confirm that the reference text tokens are within budget |
Three common errors
- Phenomenon: The same candidate's name is written differently in the registration records and the graduation application form. Cause: The name characters were not unified when entered in the two places, the retrieval candidate fragments each match different spellings, and the fields do not align during handover.
- Phenomenon: The number of course qualification certificates is inconsistent with the number of score entries in the registration records. Cause: Qualification certificates are generated by batch while registration records are updated by examination session, versions are not synchronized, and there are differences in the number of candidate fragments returned by retrieval.
- Phenomenon: The graduation application form lacks the signature or receipt of the examining institution. Cause: The signature step was not completed before entering retrieval, the signature field in the candidate fragments is empty, and the handover record cannot confirm the responsible party.
How to verify the setup
Acceptance of this function: test once each with synonym-rewritten questions, compare candidates and scores, then toggle re-ranking on and off to observe the order of the top few items; switch searchMode and usingReRank, and record changes in the number of candidates and scores.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the knowledge base search test, fix the same question, switch respectively to semantic, full-text, and hybrid modes, record the number of candidates and similarity scores, and confirm that material fields are covered.
- Compare the order of the top few items before and after enabling re-ranking, and adjust the reference limit, check the reference text tokens and the number of array items, and confirm that signature, date, and version fields have not been truncated.