What this category's data looks like
The application materials for social evaluation of vocational skill level certification usually include three types: the evaluation implementation plan, the candidate registration form, and the assessor dispatch form. The evaluation implementation plan is prepared by the evaluation institution by batch, stating the occupational direction, evaluation level, assessment method, and time and place; the candidate registration form is filled in by the applicant, containing name, ID number, declared occupation and level, education, and years of work experience; the assessor dispatch form is issued by the institution's examination affairs department, recording the assessor's name, certificate number, dispatched session, and signature confirmation. The three types of materials are submitted together by batch, and the update rhythm is synchronized with the certification batch, with common corrections, version replacements, and receipt collection. When the materials enter this function, the evaluation implementation plan assumes the role of the rule baseline, the candidate registration form assumes the role of object details, and the assessor dispatch form assumes the role of personnel and signatures; the three establish a correspondence based on the same batch and the same object, for subsequent retrieval and discrepancy localization.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), outputting data rows and index status (parsed, indexing, indexed). The "discrepancy list" is then completed by retrieval and subsequent processing. After parsing is completed, parsing and chunking are immediately persisted as visible data rows and bound to a unique data identifier; the index transitions through three states, and data pending indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | Whether the occupational direction, evaluation level, and assessment date under the same batch as the candidate registration form correspond item by item, and whether signatures and receipts are complete | Check the file records and data rows separately, and confirm that after the fields are persisted the status is parsed and enters indexing |
| Candidate registration form | Whether the name, declared occupation, and number of sessions on the same object as the assessor dispatch form are consistent, and whether dates conflict | Review the chunk boundaries according to chunkSize and chunkSplitter, and check the processing mode corresponding to trainingType |
| Assessor dispatch form | Whether it is consistent with the evaluation implementation plan on assessor name, certificate number, and dispatch date, and whether missing signatures or receipts are marked | Open the data row to check the status, and confirm that only after indexed does it enter retrieval and discrepancy localization |
Three common errors
- Phenomenon: the same candidate's name and declared level do not match between the registration form and the dispatch form. Cause: the two materials are submitted separately and the fields are not aligned to the same object, and the versions are not synchronized.
- Phenomenon: the evaluation implementation plan has been replaced with a new version, but the registration form still references the old assessment date. Cause: the version replacement was not written back to the ledger, resulting in deviations in dates and quantities among the materials.
- Phenomenon: the assessor dispatch form lacks a signature or receipt, but retrieval can still hit that row. Cause: successful parsing does not equal completed indexing; the data row status must be checked.
How to verify the setup
This function's acceptance: upload one material, observe whether the data row status transitions through parsed, indexing, and indexed, and check that the rebuild task only covers data rows whose indexing has been completed.
Business test: use one real record to find fields inconsistent with the ledger, form a discrepancy list for the reviewer to confirm and write back.
- Open the data row to check the status, confirm it is consistent with the interface display, and that data pending indexing does not participate in recall.
- Check the file records and data rows separately, and confirm that the rebuild scope only covers data whose indexing has been completed.