What this category's data looks like
Vocational college program setup filing materials usually include three types: the program setup filing form, the talent demand justification report, and the faculty and equipment list. The filing form contains the program name, code, program length, enrollment number, signature, and date; the justification report contains industry job demand, survey data, and justification conclusions; the faculty and equipment list contains the number of teachers, title structure, equipment names, and number of units. Materials are updated by academic year or application batch, and the sources are the school's academic affairs office, secondary colleges, and practical training departments. After entering the parsing and training task, the three types of materials are each stored as data rows, bound to a unique data identifier, so that retrieval and subsequent processing can trace back to the original text by material source.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), which outputs data rows and index status (parsed, indexing, indexed). The basis entries that can be traced back to the original text are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Program setup filing form | Fields include program name, code, program length, enrollment number, signature, and date, and must be consistent with the justification report | Check the program name, code, date, and signature fields in the filing form and the justification report, and check whether the data row status is parsed or indexed |
| Talent demand justification report | Fields include job demand, survey data, justification conclusions, and date, and must correspond to the program name in the filing form | Check whether the program name in the justification conclusions is consistent with the filing form, and check trainingType and the index status transition |
| Faculty and equipment list | Fields include the number of teachers, title structure, equipment names, and number of units, and must match the enrollment scale in the filing form | Check whether the number of teachers and equipment units in the list match the filing form, and check whether entries after chunking by chunkSize and chunkSplitter can be traced back to the original text |
| Data row | Is in one of the three states and consistent with the interface display; data pending indexing does not participate in recall | Open the data row to check the status, and confirm that the index status is parsed, indexing, or indexed |
Three common errors
- Symptom: The same program name is written differently in the filing form and the justification report, so retrieval does not match. Cause: The two materials are filled in by different departments, without unified verification and version synchronization.
- Symptom: The number of teachers in the faculty and equipment list does not match the enrollment scale in the filing form, so the basis entries cannot corroborate each other. Cause: The list update lags, and the old version is still in the database and participates in recall.
- Symptom: The filing form lacks a signature or receipt, so the basis entries cannot confirm that it is currently valid. Cause: The scanned material does not include the signature page, so after parsing the entries lack a verifiable date and seal.
How to verify the setup
Acceptance of this feature: upload one material, observe the data row status transition and the coverage of the rebuild task, and confirm that the status is parsed, indexing, indexed, and that the rebuild only covers data that has completed indexing.
Business test: ask a cross-material basis question and see whether the answer gives a traceable source.
- Check the file records and data rows separately, confirm that the identifiers of files and data rows are distinguishable, and record the processing mode corresponding to
trainingType. - Check the data rows covered by the rebuild task, and confirm that it targets only data that has completed indexing, while data pending indexing does not participate in the rebuild.