What this category's data looks like
This category covers university employment contract signing and graduation destination statistics. Materials include employment agreements, graduation destination registration forms, and employer certificates. Employment agreements contain the employer name, Unified Social Credit Code, signing date, graduate signature, and employer seal; graduation destination registration forms contain the destination type, employer name, reporting date, and department review comments; employer certificates contain the offered position, onboarding date, employer contact, and receipt confirmation. The three types of materials are submitted in batches by departments, employment centers, and employers, and are updated according to graduation batch and signing progress. Field names, date formats, and signature positions often differ across materials. When entering the knowledge base retrieval and recall function, employment agreements serve as the primary evidence of signing, graduation destination registration forms serve as the basis for destination classification, and employer certificates serve as supplementary corroboration. Each participates in candidate recall as fragments, for subsequent nodes or manual generation of handover-ready deployment status and operation records.
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 pattern, merge, rerank, filter, and limit trimming). The handover-ready deployment status and operation records are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Whether the employer name, signing date, graduate signature, and employer seal are complete, and consistent with the same items in the graduation destination registration form | In the search test, search using a combination of employer name and signing date, check the name, date, and signature fields in the candidate fragments, and record the number of candidates and scores |
| Graduation destination registration form | Whether the destination type, reporting date, and department review comments are consistent with the corresponding records in the employment agreement | Switch searchMode to semantic, full-text, and hybrid, testing each once, and compare whether the candidates cover both the destination type and date fields |
| Employer certificate | Whether the offered position, onboarding date, employer contact, and receipt confirmation match the same items in the other two materials | Compare the order of the top few results before and after enabling rerank, and check whether the receipt and contact fields appear in the candidate fragments |
| Retrieval parameters and records | Whether the number of candidates, scores, similarity, limit, usingReRank, and the handover form correspond item by item | Check the candidate count and score records against the handover form, and confirm that the cited text tokens and array count are registered separately |
Three common errors
- Symptom: The employer name or signing date for the same graduate does not match between the employment agreement and the graduation destination registration form. Cause: The two materials are entered at different stages, versions are not synchronized, and retrieval candidates each take one fragment.
- Symptom: The employer certificate lacks an employer seal or receipt confirmation, yet candidate fragments are still recalled. Cause: Signature and receipt fields are not validated when materials are ingested, and retrieval returns results only by text similarity.
- Symptom: There are many candidates, but the ones ranked at the top are unrelated to the signing record. Cause: Rerank is not enabled or the similarity filter setting is too loose, and no secondary sorting is performed after multi-route merging.
How to verify the setup
Acceptance for this function: test once each with synonym-rewritten questions, compare candidates and scores, then toggle rerank on and off to observe the ordering of the top few results; at the same time, switch searchMode to observe differences between semantic and full-text candidates, and record the status of the three items similarity, limit, and usingReRank.
Business testing: check item by item against the handover form once to see which record is missing; check whether the names, quantities, dates, and signatures in the employment agreement, graduation destination registration form, and employer certificate are consistent.
- In the knowledge base search test, fix the same question, retrieve once each in semantic, full-text, and hybrid modes, record the number of candidates and scores, and note the
searchModevalue. - Retrieve once each with rerank enabled and disabled, compare the order of the top few candidates, register the
usingReRankstatus and thesimilarityandlimitsettings, and confirm that the cited text tokens and array count are recorded separately.