What this category's data looks like
Vocational college program establishment filing materials are centered on the program establishment filing form, accompanied by two types of attachments: talent demand justification and a faculty and equipment list. The sources are the college's academic affairs and human resources departments and industry research institutions, and the update cadence rolls forward with the enrollment year and the competent authority's receipt cycle. When the three types of materials enter the conversation log and auditing function, their roles differ: the filing form carries the main fields such as program name, program length, and enrollment scale; the talent demand justification carries job correspondence, research date, and justification signature; the faculty and equipment list carries teacher count, equipment units/sets, and asset date. Field characteristics are concentrated in four categories: name, quantity, date, and signature, and the same record must be aligned item by item across the three materials. The conversation record interface retains question-and-answer traces by application and session dimension, providing session evidence for the version ledger and change records.
Configuration and implementation checks
This step is executed by the conversation record interface (by application and session dimension), outputting a session message list and total record count, including role and reference information. The "version ledger and change records" are then completed manually or by an external system.
| Object | Check | Verification action |
|---|---|---|
| Program establishment filing form | Fields, dates, and signatures must be aligned item by item with the talent demand justification and faculty and equipment list, and the current version must be unique | Page through by application and session dimension to retrieve all records, verify the source of chatId and dataId, and compare the total record count total with response code of 200 |
| Talent demand justification | Research date, job names, and quantities must be consistent with the filing form, and justification signatures and receipts must be complete | Open a single record and verify the reference and elapsed-time fields in value, confirm that the number of justification references equals the array length, and that reference text tokens are recorded separately |
| Faculty and equipment list | Teacher count, equipment units/sets, and asset date must be consistent with the filing form, old versions must be traceable, and references must be synchronized | Pull two consecutive pages and compare the offset and total count, check that the two role types, question and answer, appear alternately, and that exported records include references |
| Version ledger and change records | The current version must be unique, old versions must be traceable, references must be synchronized, and after a change the version number and references must be updated in sync | After changing one piece of content, re-pull the session records and check whether the version number and references are synchronized; separately mark entries missing signatures or receipts |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match between the filing form and the faculty and equipment list. Cause: the two materials are registered separately, without field-level comparison and signature/receipt verification for the same record.
- Symptom: the version is not synchronized, and the old version is still referenced. Cause: after a change, only one material was modified, and the session records were not re-pulled to check whether the version number and references were updated in sync.
- Symptom: the interface returns empty but there are sessions in the UI, or only the first page is retrieved. Cause: the sources of the application and session identifiers are inconsistent, the pagination offset is not continuous, and the total record count is confused with the number of messages.
How to verify the setup
Acceptance for this feature: page through by total record count to retrieve all records, sample one record to check the role, reference information, and time, verify the message identifiers and content fields _id, dataId and value, and recognize only the total record count total and response code of 200 as status values.
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 dimension, compare the offset and total record count, and confirm that the two role types, question and answer, appear alternately and that the reference and elapsed-time fields are readable.
- Hand the exported session message list to a person or external system to register the version ledger, and verify item by item the name, quantity, date, and signature/receipt of the filing form, talent demand justification, and faculty and equipment list.