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. Sources include school academic affairs, internship units, and supervising instructors. The update cadence adjusts with internship cycles, position adjustments, and signed receipts. When materials enter parsing and training tasks, their roles differ: internship agreements carry unit names, positions, start and end dates, and signatures; internship plans carry batches, headcounts, supervising instructors, and schedules; internship logs carry daily records, quantities, and signed receipts. Field characteristics center on names, quantities, dates, and signatures. The same record easily fails to match across two materials, with versions not synchronized or receipts missing. Parsing and chunking split by chunkSize and chunkSplitter, training types are distinguished by trainingType, and after being stored in the database they form data rows and index statuses for subsequent retrieval and version ledgers.
Configuration and implementation checks
This stage is executed by parsing and training tasks (server-side tasks), outputting data rows and index statuses (parsed, indexing, indexed). The version ledger and change records are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Whether the unit name, position, start and end dates, signature, and receipt are consistent with the internship plan | Check the file records and data rows separately, and confirm that the agreement fields align item by item with the plan fields |
| Internship plan | Whether the batch headcount, supervising instructor, schedule, and internship log quantities and dates match | Open the data rows to check the status, and see whether the fields are complete after splitting by chunkSize and chunkSplitter |
| Internship log | Whether the daily records, quantities, dates, and signatures are synchronized with the agreement and plan | Check whether the log data row status is parsed, indexing, or indexed, and compare the signed receipts |
| Data row | Is in one of the three states and consistent with the interface display, and the identities of the file record and the data row are distinguishable | Look at the data rows covered by the rebuild task, and confirm that only data with completed indexing is covered |
Three common errors
- Symptom: The names, quantities, and dates of the same internship record do not match between the agreement and the plan. Cause: The two materials are parsed and stored separately, the fields are not cross-checked, and the version ledger is not synchronized.
- Symptom: An old version of the internship plan is still hit by retrieval, and the current version is not unique. Cause: The version is not synchronized, the rebuild task does not cover data with completed indexing, and the old data rows are still within the recall scope.
- Symptom: The internship log lacks a signature or receipt, but retrieval shows it as parsed. Cause: Successful parsing does not mean retrieval will necessarily hit; the index status has not reached indexed, and data pending indexing does not participate in recall.
How to verify the setup
This feature's acceptance: Upload one material, observe the data row status transitions and the coverage scope of the rebuild task, check only parsed, indexing, and indexed statuses, and confirm the processing mode corresponding to trainingType.
Business test: Change one piece of content, and see whether the version number and references are updated synchronously.
- Open the data rows to check the status, and confirm that the identities of the file record and the data row are distinguishable.
- Look at the data rows covered by the rebuild task, and confirm that changing the model only rebuilds data with completed indexing.