What this category's data looks like
This page focuses on university employment contract signing and graduation destination statistics. The materials include employment agreements, graduation destination registration forms, and employer certificates. The employment agreement carries the signing parties, position, and signatures/seals; the graduation destination registration form records the destination category, employer name, and date; the employer certificate provides hiring and acceptance information. When these materials enter the knowledge base retrieval and recall function, each participates as an independent source in candidate generation and does not directly become a statistical table or authorization result. The update cadence changes with graduation batches and signing progress, and the field characteristics center on names, quantities, dates, signatures, and receipts. When versions are not synchronized or signatures/seals are missing, the same record is prone to mismatches in names, quantities, and dates across different materials. Authorized access and external services require first clarifying the visitor identity and visible scope, and then using retrieval results to support subsequent nodes or manual generation of externally available entry points and authorization scope.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate chunks 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 |
|---|---|---|
| Employment agreement | Whether the signing parties, position, date, and signature are consistent with the registration form | In the search test, test once each with synonymous questions, check the candidate chunks and similarity scores, and record the number of array entries |
| Graduation destination registration form | Whether the destination category, employer name, quantity, and date match the agreement | Switch searchMode to semantic, full-text, or hybrid, and compare whether the candidates simultaneously include both types of recall results |
| Employer certificate | Whether the hiring information, acceptance date, and receipt signature are complete | Turn usingReRank on or off, and compare the order of the top few candidates and what remains after filtering by the similarity threshold |
| Authorized access scope | Whether the visitor identity matches the visible scope, and whether unauthorized access is invisible | Access once with a restricted identity, check whether the returned candidates fall only within the set scope, and separately record the tokens of the cited text |
Three common errors
- Phenomenon: The same graduate's employer name, quantity, and date do not match between the agreement and the registration form. Cause: The two materials are entered separately and versions are not synchronized, so retrieval candidates are independent of each other.
- Phenomenon: An employer certificate missing a signature or receipt is still recalled as a complete source. Cause: The material status was not verified before ingestion, and candidate chunks are not marked with missing fields.
- Phenomenon: There are many candidates, but the ones ranked first are all irrelevant, and the answer lacks key paragraphs. Cause: The retrieval mode was not selected according to the material form, and rerank and similarity filtering were not adjusted in coordination.
How to verify the setup
Acceptance for this function: test once each with synonymously rewritten questions, compare candidates and scores, then toggle rerank to inspect the ordering of the top few, and check the effects of searchMode, similarity, limit, and usingReRank.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, whether unauthorized content is invisible, and separately record the number of citations and the tokens of the cited text.
- In the knowledge base search test, switch
searchMode, run the same question in semantic, full-text, and hybrid modes respectively, and record the number of candidates and scores. - Run once each with
usingReRankenabled and disabled, compare the ordering of the top few candidates, and check whether the chunks retained aftersimilarityfiltering contain key fields.