What this category's data looks like
This page addresses pre-departure training and overseas safety reminder scenarios. Materials come from three types of documents: pre-departure training courseware, safety reminder checklists, and accommodation contact lists. The update cadence refreshes in sync with semester batches and destination adjustments. After the three types of materials enter parsing and training tasks, their roles differ: courseware carries process and specification descriptions, safety reminder checklists carry risk items and emergency wording, and accommodation contact lists provide structured fields such as contacts, addresses, and dates. Field characteristics concentrate on four types: names, quantities, dates, signatures, and receipts. The same record often appears in two materials with inconsistent name spellings, different quantity definitions, and misaligned dates; when versions are not synchronized, missing signatures or receipts are more obvious. After material parsing is complete, it is immediately persisted as visible data rows and bound to a unique data identifier, providing a verifiable data foundation for subsequent retrieval and discrepancy localization.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index status (parsed, indexing, indexed). The "discrepancy list" is then completed by retrieval and subsequent processing. Successful parsing does not mean retrieval will definitely hit; it also depends on whether the index status has reached completed.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Whether the name, date, and signature are consistent with the ledger | Open the data row to check whether trainingType and the status are parsed / indexing / indexed, then compare the courseware date and signature field |
| Safety reminder checklist | Whether the quantity and date match the accommodation contact list | Check the file record and the data row separately, and use chunkSize and chunkSplitter to check whether chunking has split items apart |
| Accommodation contact list | Whether the name, quantity, and date of the same record are consistent | Look at the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, then compare the contact fields one by one |
| File record and data row | The identities of the file record and the data row are kept separate | Check the file record and the data row separately, confirm that the unique data identifier is bound correctly and that the status matches what is displayed in the interface |
Three common errors
- Symptom: newly uploaded materials cannot be found. Cause: the data row is still in parsed or indexing, and data pending indexing is naturally isolated at the retrieval layer and is not recalled.
- Symptom: the name, quantity, and date of the same record do not match across two materials. Cause: versions are not synchronized, and the courseware and contact list were updated separately without field-level comparison.
- Symptom: empty data rows remain after a training failure. Cause: materials missing signatures or receipts were enqueued in advance, and the failed data was not edited or deleted in time.
How to verify the setup
This feature's acceptance: upload one material, observe the data row status transition parsed -> indexing -> indexed and the coverage scope of the rebuild task, and check whether trainingType, chunkSize, chunkSplitter, and the interface display are consistent.
Business test: use one real record to find a field inconsistent with the ledger, hand it to the reviewer for confirmation, and write it back.
- Open the data row to check the status, confirm it is in one of the three states and consistent with the interface display, then compare the name, quantity, date, and signature field.
- Look at the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and that after changing models the rebuild scope does not overreach.