What this category's data looks like
This category's data looks like Material verification and discrepancy localization for enterprise new employee onboarding training involves three types of materials: onboarding training plans, course sign-in sheets, and job descriptions. Onboarding training plans are updated by the training lead on a batch basis, with fields including course name, class hours, date, and instructor; course sign-in sheets are collected by on-site organizers per session, with fields including name, department, sign-in time, and signature; job descriptions are maintained by the hiring department per job version, with fields including job title, responsibility items, effective date, and approval signature. When the three types of materials enter the document parsing and chunking feature, each is stored as an independent file, and immediately after parsing and chunking is completed, it becomes a visible data row and is bound to a unique data identifier, for subsequent retrieval and discrepancy localization calls. The verification dimensions fall on fields, dates, and signatures. Common inconsistencies are that the name, quantity, or date of the same record does not match across two materials, versions are not synchronized, or signatures or receipts are missing.
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 is immediately stored as a visible data row 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 |
|---|---|---|
| Onboarding training plan | Course name, class hours, and date are consistent with the corresponding course items in the job description | Check whether the data row status is indexed, and compare the course name and date fields |
| Course sign-in sheet | Name, department, and sign-in time are consistent with the number of names in the onboarding training plan | Check the file record and the data row separately, and check whether the signature or receipt is missing |
| Job description | Job title, responsibility items, and effective date are consistent with the version referenced by the training plan | Check the data rows covered by the rebuild task, and confirm the chunk boundaries under chunkSize and chunkSplitter |
| Data row and file record | The identities of the file record and the data row are distinguishable, and the status is consistent with the interface display | Open the data row and check trainingType and the status values parsed / indexing / indexed |
Three common errors
- Symptom: Materials just uploaded cannot be found. Cause: The data row is still in the pending indexing state, and the retrieval layer is naturally isolated, so it has not entered the recall range.
- Symptom: The name, quantity, or date of the same record does not match across two materials. Cause: Versions are not synchronized, and an old-version job description is mixed with a new-batch training plan.
- Symptom: After training fails, an empty data row is left behind. Cause: Training interruption leaves orphan data, and the failed data row is not edited or deleted in time.
How to verify the setup
Acceptance for this feature: Upload one material, observe the data row status transitions and the coverage scope of the rebuild task, confirm that the status values parsed / indexing / indexed are consistent with the interface display, and that the rebuild covers only data whose indexing has been completed.
Business test: Use one real record to find a field inconsistent with the ledger, hand it to the reviewer for confirmation, and write back the discrepancy list.
- Open the data row to check the status, confirm that it is in one of the three states and consistent with the interface display, and check the file record and the data row separately.
- View the data rows covered by the rebuild task, confirm that it covers only data whose indexing has been completed, and that the initial training covers data that is pending indexing and indexing.