What this category's data looks like
This page focuses on university employment contract signing and graduation destination statistics, handling three types of materials: employment agreements, graduation destination registration forms, and employer certificates. The employment agreement contains the employer name, unified social credit code, position, signing date, signatures and seals of both parties; the graduation destination registration form contains the destination type, employer name, reporting date, receipt and personal confirmation; the employer certificate contains the offered position, onboarding date, employer contact person and signature/seal. The material sources are departmental summaries, employment system exports and paper scans, and the update cadence advances with signing batches and destination changes. When materials enter this feature, the employment agreement serves as the primary basis for signing, the graduation destination registration form serves as the basis for destination classification, and the employer certificate serves as supplementary evidence; together the three support the version ledger and change records.
Configuration and implementation checks
This step is executed by the indexing service and vector database, outputting vectors and index status (whether recall is possible, whether data in the same group is merged). The "version ledger and change records" is then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials). Only when the indexing model is consistent with the vector model actually used by the knowledge base do the recall results correspond to the material versions.
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Employer name, position, signing date, signatures and seals are complete and consistent with the registration form | Open a data row and check the index fields, confirm that multiple vector identifiers are present, then run a retrieval again to see whether the same group is merged |
| Graduation destination registration form | Destination type, reporting date, receipt and personal confirmation have no missing items, and the dates match the agreement | Check the indexing model in the knowledge base settings, and use limit to record the citation text budget |
| Employer certificate | Offered position, onboarding date, employer contact person and signature/seal are complete, and the name and quantity match | Check the data scope covered by the rebuild task; for status values, only recognize indexed and the rebuild task record |
| Version ledger and change records | The current version is unique, old versions are traceable, and citations are updated in sync | After changing one piece of content, check whether the version number and citations are updated in sync |
Three common errors
- Symptom: For the same record, the employer name and signing date in the employment agreement and the graduation destination registration form do not match. Inspect the following: The two materials are updated separately, versions are not synchronized, and citations still point to the old version.
- Symptom: The employer certificate lacks a signature or receipt, but the destination registration form has already been marked complete. Inspect the following: Material collection and the registration step are disconnected, and progress is advanced before the supporting evidence is returned.
- Symptom: Duplicate entries appear in retrieval results, or a data row has content but cannot be retrieved. Inspect the following: Data in the same group is not merged, and after changing models, rebuilds are triggered only for data whose indexing is already complete, so coverage is incomplete.
How to verify the setup
This feature's acceptance check: sample one data row and look at the index fields to confirm that multiple vector identifiers are present; then run a retrieval again to see whether data in the same group is merged and whether the score takes the highest value.
Business test: change one piece of content and see whether the version number and citations are updated in sync; the number of citations is recorded by array length, and the citation content budget is checked separately by quoteMaxToken, not compared for equality with the number of citations.
- Check the indexing model in the knowledge base settings, confirm it is consistent with the vector model actually used by the knowledge base, and for status values only recognize indexed and the rebuild task record.
- Open a data row and check the index fields to confirm that multiple vector identifiers are present; after changing models, check the data scope covered by the rebuild task, and trigger only for data whose indexing is already complete.