What this category's data looks like
In the exam administration and violation handling scenario, materials come from three categories: exam administration manuals, examination room record sheets, and violation fact records. The exam administration manual defines the process and field definitions, the examination room record sheet carries the actual situation of that examination room, and the violation fact record focuses on specific behaviors and signature receipts. These materials are updated with each exam batch, and versions iterate frequently. Fields include candidate name, examination room number, violation items, quantity, date, signature, and receipt status. After the materials enter the parsing and training tasks, the exam administration manual serves as the rule baseline for field definition comparison, while the examination room record sheets and violation fact records serve as the objects to be verified and are stored row by row, each bound to a unique data identifier for subsequent retrieval and discrepancy localization.
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 discrepancy list is then completed by retrieval and subsequent processing; parsing itself does not produce a discrepancy list or business documents.
| Object | Check | Verification action |
|---|---|---|
| Exam administration manual | Fields, dates, and signature definitions must be consistent with the examination room record sheet and violation fact record | Verify the fields and signature receipts of the parsed data rows, and confirm the status is parsed, indexing, or indexed |
| Examination room record sheet | The same record matches the violation fact record in name, quantity, and date | Verify the file record and the data row identifier separately, and compare the fields of the same object in the two materials |
| Violation fact record | The version is in sync with the exam administration manual, and signatures or receipts are not missing | Check the data row status and the coverage scope of the rebuild task, and confirm that only indexed data is rebuilt |
| Parsed chunked data rows | The three-state flow is consistent with the interface display, and data pending indexing does not participate in recall | Use chunkSize, chunkSplitter, and trainingType to verify chunking and training type |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the examination room record sheet and the violation fact record. Cause: The versions of the two materials are not in sync, and the field definitions have not been unified according to the exam administration manual.
- Symptom: The violation fact record lacks a signature or receipt, and review cannot confirm it. Cause: The signature status was not written back during the material circulation step, and the data row remains in the pending-indexing state.
- Symptom: Newly uploaded materials cannot be found. Cause: Successful parsing does not equal a retrieval hit; the index status has not reached completed, and data pending indexing is naturally isolated at the retrieval layer.
How to verify the setup
This feature acceptance: Upload one material, observe the data row status flow and the coverage scope of the rebuild task, and confirm that only data with completed indexing is rebuilt, while data pending indexing does not participate in the rebuild chain.
Business test: Use one real record to find fields inconsistent with the ledger, record the discrepancy list, and submit it to the reviewer for confirmation and write-back.
- Open the data row to verify the status, and confirm it is in one of the three states and consistent with the interface display
- Verify the file record and the data row separately, and confirm that the identities of the two can be distinguished