What this category's data looks like
This category's data involves three types of materials: daily life schedules, morning and afternoon check records, and child health observation records. They are filled in daily by class teachers and childcare workers, summarized weekly, and archived monthly. Fields include child name, activity segment, time point, quantity, date, and signature. When the materials enter this feature, the daily life schedule serves as the planning baseline, while the morning and afternoon check records and child health observation records serve as execution traces. Each is parsed into data rows and bound to a unique data identifier, for subsequent retrieval and comparison of whether names, quantities, and dates are consistent.
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.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Check whether the name, date, and signature for the same child and the same activity segment are consistent with the morning and afternoon check records | Open the data row to check the status, confirm the parsing chunking and the chunkSize and chunkSplitter settings, then retrieve and compare |
| Morning and afternoon check records | Check whether the quantity, date, and receipt for the same record are consistent with the child health observation records | Check the file records and data rows separately, and confirm trainingType and the three index states parsed, indexing, indexed |
| Child health observation records | Check whether the same object's name, quantity, and date match the daily life schedule | Look at the data rows covered by the rebuild task; only data with completed indexing is covered |
| Data row | Is in one of the three states parsed, indexing, indexed and is consistent with the interface display | Open the data row to check the status, and confirm that data pending indexing does not participate in recall |
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 two materials were parsed separately without field comparison.
- Symptom: empty data rows remain after training fails. Cause: the material lacks a signature or receipt, indexing was not completed after parsing and chunking, and it must be edited or deleted directly.
How to verify the setup
This feature's acceptance: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, and confirm that the three states parsed, indexing, indexed are consistent with the interface, and that rebuild only covers data with completed indexing.
Business test: use one real record to find fields inconsistent with the ledger, check the name, quantity, date, and signature, and submit to the reviewer for confirmation and write-back.
- Open the data row to check the status, and confirm that file records and data row identities can be distinguished
- Look at the data rows covered by the rebuild task, and confirm that only data with completed indexing is covered