What this category's data looks like
Materials for social evaluation of vocational skill level certification mainly consist of evaluation implementation plans, candidate registration forms, and assessor dispatch forms. The sources are filing institutions and evaluation organizations, and the update cadence follows batches and policy adjustments. The evaluation implementation plan contains the occupation name, level, assessment modules, and dates; the candidate registration form contains identity information, declared level, signature, and receipt; the assessor dispatch form contains the assessor's name, task date, and signature. After materials enter parsing and training tasks, they are first split according to chunkSize and chunkSplitter and stored as data rows, then enter index flow according to trainingType. The implementation plan serves as the master record, while the registration form and dispatch form serve as supporting evidence. The fields of the three must align on name, quantity, date, and signature. Old versions must be retained and traceable, and references must be updated in sync.
Configuration and implementation checks
This step 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 |
|---|---|---|
| Evaluation implementation plan | The occupation name, level, assessment modules, dates, and signature must be consistent with the registration form and dispatch form | Check the occupation name and level in the plan, compare the declared level in the registration form with the task date in the dispatch form, check whether the signature and receipt are complete, and record the data row status after splitting by chunkSize and chunkSplitter |
| Candidate registration form | If the name, quantity, or date for the same candidate does not match across the plan and dispatch form, it is inconsistent | Extract the identity information and declared level from the registration form, compare them item by item with the plan roster, confirm the signature and receipt, and check whether the data row status is parsed, indexing, or indexed |
| Assessor dispatch form | The assessor's name, task date, and signature must match the plan and registration form | Check the assessor's name and task date in the dispatch form, compare them with the records in the plan and registration form, check whether the signature is missing, and confirm whether the index flow corresponding to trainingType is complete |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are updated in sync | After changing one piece of content, check whether the version number and references are updated in sync, and verify that the rebuild task only covers data with completed indexes |
Three common errors
- Symptom: The name, quantity, or date for the same candidate does not match between the registration form and the plan. Cause: Materials are maintained separately, and field alignment and version comparison are not performed after parsing and chunking.
- Symptom: The old version of the plan is still hit by retrieval, and references are not updated in sync. Cause: The version ledger is not updated with changes, and the rebuild scope does not cover data with completed indexes.
- Symptom: The dispatch form lacks a signature or receipt, and the material cannot be found. Cause: Successful parsing does not equal retrieval hits; the data row is still in a pending-index state and has not completed index flow.
How to verify the setup
This feature acceptance: upload one material and observe the data row status flow and the coverage scope of the rebuild task.
Business test: change one piece of content and see whether the version number and references are updated in sync.
- Open the data row to check the status, and confirm it is one of parsed, indexing, or indexed and consistent with the interface display.
- Check the file record and the data row separately, and confirm that the identifiers of the file and the data row are distinguishable.