What this category's data looks like
School moral education and homeroom teacher work involves three types of materials: themed class meeting plans, student comprehensive quality records, and home visit records. A themed class meeting plan contains the activity name, meeting date, number of participants, and the homeroom teacher's signature; a comprehensive quality record contains the student's name, evaluation dimensions, quantity, and the parent's receipt; a home visit record contains the visited student, home visit date, communication items, and signatures of both parties. The material sources are the grade group, homeroom teachers, and the moral education office, updated weekly or monthly, with frequent version iterations. When entering parsing and training tasks, the three types of materials are each stored as independent data rows, 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), outputting data rows and index status (parsed, indexing, indexed). The discrepancy list is then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Themed class meeting plan | Name, quantity, date, and signature are consistent between the plan and the ledger | Verify the file record and the data row separately, confirm the data row status, and use chunkSize and chunkSplitter to check whether chunking covers the signature field |
| Student comprehensive quality record | Student name, evaluation quantity, date, and parent receipt are consistent between the two materials | Open the data row to verify the status, and confirm the flow of trainingType and the three index states parsed / indexing / indexed |
| Home visit record | Visited student, home visit date, communication quantity, and signatures of both parties are consistent | Look at the data rows covered by the rebuild task, and confirm that rebuild is triggered only for indexed data |
| Data row status | Is in one of the three states and is consistent with the interface display | Open the data row to verify the status, and confirm that parsed / indexing / indexed are consistent with 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: an empty data row remains after training fails. Cause: parsing completion immediately stores it as a visible data row, and the training interruption was not cleaned up, so it must be directly edited or deleted.
- Symptom: the name, quantity, and date of the same record do not match between the two materials. Cause: the version is not synchronized or chunking does not cover the signature field, and the signature or receipt is missing.
How to verify the setup
This feature's acceptance: upload one material, observe the data row status flow 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 covers only indexed data.
Business test: use one real record to find fields inconsistent with the ledger, and verify the name, quantity, date, and signature of the themed class meeting plan, student comprehensive quality record, and home visit record.
- Verify the file record and the data row separately, and confirm that the unique data identifier and the file record identity can be distinguished.
- Look at the data rows covered by the rebuild task, and confirm that rebuild is triggered only for data whose indexing has been completed.