What this category's data looks like
Vocational school student internship management involves three core types of materials: internship agreements, internship plans, and internship logs. Internship agreements contain unit name, position, duration, insurance, and signature/seal fields; internship plans contain start and end dates, rotation arrangements, supervising teachers, and approval signatures; internship logs contain date, position, task description, and student and mentor signatures. Material sources are school academic affairs, internship units, and supervising teachers, and the update cadence changes with batches and months. When materials enter this feature, agreements and plans serve as rule bases, logs serve as process records, and each generates vector indexes to support subsequent retrieval and citation trimming for supporting materials.
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). "Version ledger and change records" are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Fields: unit name, position, duration, insurance, signature/seal; dates: signing date and effective date | Open a data row and check the index fields to confirm that multiple vector identifiers are all present; status is indexed |
| Internship plan | Fields: start and end dates, rotation arrangements, supervising teacher, approval signature; dates: plan date and approval date | Check the index model in the knowledge base settings and confirm it matches the vector model actually used by the knowledge base |
| Internship log | Fields: date, position, task description, student and mentor signatures; dates: log date and signature date | View the data scope covered by the rebuild task and confirm that after changing the model, it is triggered only for data whose indexing has already been completed |
| Data row | Multiple vector identifiers for one data item are all present, and the vector score takes the highest score | Retrieve once and see whether data in the same group is merged; record the tokens of the cited text and the number of array entries separately |
Three common errors
- Symptom: the unit name, position, and date of the same record do not match between the internship agreement and the internship log. Inspect the following: material sources are not synchronized, fields are not aligned.
- Symptom: after the internship plan is updated, the old version is still retrieved, and the version number and citation are not synchronized. Inspect the following: the version is not synchronized, data rows whose indexing has not been completed do not participate in recall, and indexing must be completed before rebuilding.
- Symptom: the internship log lacks a student or mentor signature, and the receipt is missing. Inspect the following: and duplicate entries appear in retrieval results.
How to verify the setup
Feature acceptance: sample one data row and look at the index fields to confirm that multiple vector identifiers are all present; then retrieve once to see whether the same group is merged, with the vector score taking the highest score.
Business test: change one piece of content and see whether the version number and citation are updated synchronously; record the tokens of the cited text and the number of array entries separately, and do not compare limit, and the number of citations for equality.
- Check the index model in the knowledge base settings and confirm it matches the vector model actually used by the knowledge base; open a data row and check the index fields to confirm that multiple vector identifiers are all present.
- View the data scope covered by the rebuild task and confirm that after changing the model, it is triggered only for data whose indexing has already been completed; retrieve once and see whether data in the same group is merged, with status indexed.