What this category's data looks like
Compulsory education dropout prevention and school retention materials center on dropout risk ledgers, return-to-school persuasion records, and home visit records. Their sources are routine reporting, special verification, and transfer handovers by schools, townships, and education authorities, and their update cadence rolls with semesters, persuasion milestones, and home visit cycles. Ledgers focus on students' basic information, risk levels, and responsible teachers; persuasion records focus on persuasion time, method, participants, and return-to-school results; home visit records focus on visit date, visit target, problem description, and parent signature. When these materials enter the document parsing and chunking feature, each plays a different role: ledgers provide students and risk identifiers, persuasion records provide process and result fields, and home visit records provide household evidence and signed receipts, together forming the data foundation for the version ledger and change records.
Configuration and implementation checks
This stage is executed by parsing and training tasks (server-side tasks), outputting data rows and index status (parsed, indexing, indexed). The "version ledger and change records" are then completed by retrieval and subsequent processing. After parsing is complete, parsing and chunking immediately persist to the database as visible data rows and bind a unique data identifier; indexing flows through the three states parsed, indexing, and indexed, and data pending indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Fields include student name, risk level, responsible teacher, date, and signature, and are consistent with the name, quantity, and date in the persuasion records | Open the data row to check whether the status is parsed, indexing, or indexed, and check whether the identifiers of the file record and the data row are distinguishable |
| Persuasion records | Persuasion time, method, participants, and return-to-school result are consistent throughout the same batch of materials, with no missing signature or receipt | Check the file record and the data row separately, and check whether the data row status under the processing mode corresponding to trainingType is consistent with the interface display |
| Home visit records | Home visit date, visit target, problem description, and parent signature are traceable, the old version is traceable, and references are synchronized | Check whether the data rows covered by the rebuild task include only data whose indexing is completed, and check the chunking results related to chunkSize and chunkSplitter |
| Version ledger and change records | The current version is unique, the old version is traceable, references are synchronized, and the name, quantity, and date of the same record match across the two materials | After changing one piece of content, check whether the version number and references are updated synchronously, and confirm that data pending indexing did not participate in the rebuild |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the ledger and the persuasion records. Cause: After parsing and chunking, fields were not aligned by unique data identifier, and versions were not synchronized.
- Symptom: Home visit records lack a signature or receipt, and persuasion records lack a return-to-school result. Cause: Fields are missing from scanned copies of materials, and the persisted data rows were not marked as pending supplementation.
- Symptom: Newly uploaded materials cannot be found, or empty data rows remain after a training failure. Cause: The index status did not transition to completed, and data pending indexing does not participate in recall.
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 only parsed, indexing, and indexed appear as statuses and that the rebuild covers only data whose indexing is completed.
Business test: Change one piece of content, and check whether the version number and references are updated synchronously.
- Open the data row to check whether the status is parsed, indexing, or indexed, and whether it is consistent with the interface display.
- Check the file record and the data row separately, and confirm that the identities of the file record and the data row are distinguishable.