What this category's data looks like
The business basis query for primary and secondary school enrollment organizations involves three types of materials: enrollment plans, application material checklists, and admission lists. The enrollment plan specifies enrollment targets, scope, time nodes, and admission rules; the application material checklist lists the names, copies, and submission dates of documents such as household registration, real estate, and residence permits; the admission list records student names, admission categories, batches, and signed receipts. The three types of materials are updated annually, with version numbers and effective dates appearing in the header or signature block; the signature field and receipt field are key to determining current validity. After the materials enter this function, parsing and chunking convert each document into data rows and bind a unique data identifier. The enrollment plan provides the rule basis, the application material checklist provides the field and date basis, and the admission list provides the result and signature basis. Together, the three support basis entries that can be traced back to the original text.
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). "Basis entries that can be traced back to the original text" are then completed by retrieval and subsequent processing. Once parsing is complete, it is persisted as visible data rows; after training is complete, the vectors and index are written back to the same data row.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | The version is current and the clauses match the original text, and the signature or signature date is complete | Open the data row and check whether the status is indexed, compare the plan version number and effective date, and confirm that the signature field has no omissions |
| Application material checklist | The document names, copies, and submission dates are consistent with the enrollment plan requirements, with no missing items | Separately verify the identity of the file record and the data row, check that the checklist fields correspond item by item to the plan clauses, and confirm that the receipt has been signed |
| Admission list | Student names, admission categories, and batches have consistent names and quantities in the two materials | Verify the names, quantities, and dates in the list and the checklist, confirm that signatures and receipts are complete, and note that data cannot be recalled when the status is parsed or indexing |
| Parsing and training tasks | The data row is in one of the three states, and rebuilding only covers data with completed indexes | Inspect the data rows covered by the rebuild task, confirm that trainingType corresponds to the chunkSize and chunkSplitter configuration, and that data pending indexing does not participate in rebuilding |
Three common errors
- Symptom: newly uploaded materials cannot be found. Cause: the data row is in parsed or indexing, and data pending indexing is naturally isolated at the retrieval layer and is not recalled.
- Symptom: the names, quantities, and dates of the same record do not match across the two materials. Cause: versions are not synchronized, the old checklist and the new plan are mixed, and signatures or receipts are missing.
- Symptom: rebuilding takes abnormally long after changing models. Cause: rebuilding only targets data with completed indexes, data pending indexing does not participate in the rebuild chain, and the scope judgment is incorrect.
How to verify the setup
Acceptance for this function: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, and confirm that the status passes through parsed, indexing, and indexed in sequence, and that rebuilding only covers data rows with completed indexes.
Business test: ask a basis question that spans materials, and see whether the answer provides a traceable source, and whether the source matches the original text entries in the enrollment plan, application material checklist, or admission list.
- Open the data row and check whether the status is consistent with the interface display, and confirm that the identities of the file record and the data row are distinguishable.
- Inspect the data rows covered by the rebuild task, and confirm that it only covers data with completed indexes, and that data pending indexing does not participate in rebuilding.