What this category's data looks like
This category's data covers three core types of materials: the college entrance examination registration form, household registration and student status proof, and materials for children accompanying migrant workers. Sources are candidate submission, school preliminary review, and examination authority re-review, and the update rhythm changes with registration batches, correction notices, and policy interpretation adjustments. The registration form carries the candidate's basic information and examination subjects, with fields including name, ID number, graduating school, signature, and date; the household registration and student status proof carries household registration address, continuity of student status, start and end dates of enrollment, and school seal; the materials for children accompanying migrant workers carry residence permit, social insurance payment records, parents' employment proof, and receipt. After these three types of materials enter the document parsing and chunking stage, each is split into retrievable data rows, and fields, dates, and signatures become the anchors for subsequent comparison and version maintenance. The material roles differ, but all must maintain consistent references under the same version chain.
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 version ledger and change records are then completed by retrieval and subsequent processing. After parsing is completed, parsed chunks are immediately persisted as visible data rows and bound to a unique data identifier. The index transitions through the three states parsed, indexing, and indexed. Data pending indexing does not participate in recall, and changing models only rebuilds data that has completed indexing.
| Object | Check | Verification action |
|---|---|---|
| College entrance examination registration form | Check whether name, ID number, graduating school, signature, and date are consistent with the household registration and student status proof | Check the file record and the data row separately, and confirm that the dataId binding and the parsed, indexing, and indexed status displays are consistent |
| Household registration and student status proof | Check whether household registration address, student status start and end dates, school seal, and receipt are complete | Look at the data rows covered by the rebuild task, confirm that only indexed data is covered, and check trainingType and the processing mode |
| Materials for children accompanying migrant workers | Check whether the names, quantities, and dates of the residence permit, social insurance records, and parents' employment proof match | Check the chunk boundaries under the chunkSize and chunkSplitter configurations, and confirm that fields are not cut off |
| Version ledger and change records | Check that the current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, and confirm that the old version is still traceable |
Three common errors
- Symptom: the same candidate's name or number of social insurance months does not match across two materials. Cause: field chunk boundaries differ, and comparison did not return to the same data row for verification.
- Symptom: after correction, the new version has been stored, but old-version references still point to the original content. Cause: the version was not synchronized, and references were not refreshed as the data row was updated.
- Symptom: materials for children accompanying migrant workers lack a signature or receipt, but retrieval still hits them. Cause: successful parsing does not equal a guaranteed retrieval hit; the index status and field completeness must also be checked.
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 three states parsed, indexing, and indexed are consistent with the interface, that rebuild covers only indexed data, and that initial training covers data pending indexing and data being indexed.
Business test: change one piece of content, check whether the version number and references are updated synchronously, and check the configurations and data rows corresponding to the three identifiers chunkSize, chunkSplitter, and trainingType.
- Open the data row to check the status, check the file record and the data row separately, and confirm that the unique data identifier is bound correctly.
- View the data rows covered by the rebuild task, and confirm that only data that has completed indexing is covered, and that data pending indexing does not participate in rebuild.