What this category's data looks like
This page focuses on university employment contract signing and graduation destination statistics. Materials include employment agreements, graduation destination registration forms, and employer certificates. The employment agreement contains the employer name, unified social credit code, position, signing date, and signatures of the graduate and the employer; the graduation destination registration form contains the destination type, employer name, reporting date, and signature of the registrar; the employer certificate contains the acceptance opinion, contact person, issuance date, and seal. Materials are summarized by the department and reviewed by the employment center, updated by graduation batch, and the version is based on the current registration criteria. When entering this function, the employment agreement and registration form provide signing and destination fields, and the employer certificate provides acceptance and date evidence; together, the three support the basis entry in referring back to the original text.
Configuration and implementation checks
This step is executed by the indexing service and vector database, outputting vectors and index status (whether recall is possible and whether data in the same group is merged). "Basis entries that can refer back to the original text" are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Employment agreement | Fields include employer name, position, signing date, and signatures of both parties; the date is consistent with the registration form | Check the signatures and date, and confirm the same name and number as in the registration form |
| Graduation destination registration form | Destination type, employer name, reporting date, and signature of the registrar are complete | Open the data row and check the index fields, and confirm that multiple vector identifiers are all present |
| Employer certificate | Acceptance opinion, contact person, issuance date, and seal can refer back to the original text | Check whether the issuance date matches the signing date in the agreement |
| Index model | Consistent with the vector model actually used by the knowledge base, and the status is indexed | Check the index model in the knowledge base settings and view the rebuild task records |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: the name or quantity of the same record does not match across the two materials, and the vectors are not merged by the same group.
- Symptom: recall quality drops after changing the model. Inspect the following: the version is not synchronized, and the rebuild task records only cover data whose indexing has been completed.
- Symptom: a data row has content but cannot be retrieved. Inspect the following: signatures or receipts are missing, the material has not entered the index, and the index fields have no vector identifiers.
How to verify the setup
This function's acceptance: take one data row and look at the index fields, confirm that multiple vector identifiers are all present and the status is indexed, then retrieve once to see whether the same group is merged, and view the rebuild task records.
Business test: ask a cross-material basis question, see whether the answer gives a source that can be referred back to, and check the number of citations and the tokens of the cited text; record limit according to the actual budget.
- Open a data row, check the multiple vector identifiers in the index fields, and confirm that data in the same group is merged during retrieval and the highest score is taken.
- After changing the model, view the data range covered by the rebuild task records, confirm that it is triggered only for data whose indexing has been completed, and check the
defaultTokenandmaxTokenbudgets.