What this category's data looks like
Vocational school student internship management involves three types of materials: internship agreements, internship plans, and internship logs. The sources are the academic affairs system, internship units, and supervising teachers, and the update cadence runs in parallel by batch and by month. Internship agreements contain the unit name, position, duration, insurance, and signatures; internship plans contain the batch, week number, tasks, supervising teacher, and review; internship logs contain the date, location, content, issues, and receipt. When these three types of materials enter the conversation log and auditing feature, agreements and plans serve as the comparison baseline for the version ledger, while logs serve as the day-by-day source of evidence, each taking on a different role.
Configuration and implementation checks
This step is performed by the conversation record interface (by application and session dimension), which outputs the session message list and the total record count, including role and reference information. The "version ledger and change records" are then completed manually or by an external system; the interface only retrieves session evidence and does not write to the business ledger.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Whether the fields, dates, and signatures are consistent with the current version | Page through by application and session dimension to retrieve all records, verify the total record count total and response code of 200, and sample one record to inspect the role, reference information, and time |
| Internship plan | Whether the name, quantity, and date of the same record match across the two materials | Pull two consecutive pages and compare the offset and total count, then open one record to verify dataId and the reference fields |
| Internship log | Whether the date, signature, and receipt are complete and the version is not misaligned | Locate the session by chatId, verify the alternating roles and the number of references in value, and record the array count separately |
| Version ledger | Whether the current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, retrieve the records again and see whether the version number and references are updated in sync |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the agreement and the log. Cause: The two materials are maintained separately and are not aligned by the same session identifier.
- Symptom: An old version is still referenced, and the current version is not synchronized. Cause: The version ledger was not updated along with the materials, and the references were not re-pointed.
- Symptom: The log is missing a signature or receipt. Cause: The registration step did not collect everything, and the records were not re-checked when exported.
How to verify the setup
Feature acceptance: Page through by total record count to retrieve all records, and sample one record to verify the role, reference information, and time.
Business test: Change one piece of content and see whether the version number and references are updated in sync.
- Pull two consecutive pages by application and session identifier, and compare whether the total record count and offset are consistent.
- Open one record, verify the number of references and the tokens of the reference text, and record the array count separately.