What this category's data looks like
This category of data for school-enterprise education management in technical colleges covers materials such as student registration forms, teaching plans, and skills training records. Sources include exports from academic administration systems, scanned paper signed documents, and forms submitted by departments. The update cadence changes with semester registration, teaching adjustments, and skills assessment milestones. Field characteristics include the coexistence of names, student IDs, course names, quantities, dates, signature fields, and receipt numbers. When materials enter the document parsing and chunking function, student registration forms serve as the identity baseline, teaching plans serve as the basis for courses and class hours, and skills training records serve as process evidence; each material is split according to chunkSize and chunkSplitter to form its own data rows, and trainingType determines the subsequent training mode. The version ledger and change records depend on these data rows and index statuses, and are completed by retrieval and subsequent processing, ensuring that the current version is unique, old versions are traceable, and references are synchronized.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index statuses (parsed, indexing, indexed). The "version ledger and change records" are then completed by retrieval and subsequent processing. After parsing is completed, parsing and chunking are immediately persisted as visible data rows and bound to a unique data identifier. Indexing transitions through the three states parsed, indexing, and indexed. Data pending indexing does not participate in recall. Changing the model only rebuilds data that has already completed indexing.
| Object | Check | Verification action |
|---|---|---|
| Student registration form | Fields include name, student ID, registration date, and signature field; the name, quantity, and date of the same record in two materials must be consistent | Open the data row to check whether the status is parsed, indexing, or indexed, and compare whether signatures and receipts are complete |
| Teaching plan | Fields include course name, number of class hours, start and end dates, and approval signature; when the version is not synchronized, the old version is still traceable | Check the file record and the data row separately to confirm that fields are not misaligned after splitting by chunkSize and chunkSplitter |
| Skills training record | Fields include training item, quantity, date, and instructor signature; missing signature or receipt is regarded as inconsistent | Check whether the data rows covered by the rebuild task contain only indexed, and verify the training mode corresponding to trainingType |
| Data row status | Is one of parsed, indexing, or 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: Materials that were just uploaded cannot be found. Cause: The data row is in parsed or indexing status, 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 in two materials do not match. Cause: The version is not synchronized, the old version has not been traced back, and references have not been updated with the changes.
- Symptom: After training fails, empty data rows are left or signatures/receipts are missing. Cause: The initial training covers data pending indexing and data being indexed, and failed data is not edited or deleted in time.
How to verify the setup
This feature acceptance: Upload one material and observe the status transitions of the data row and the coverage scope of the rebuild task; confirm that chunkSize, chunkSplitter, and trainingType can be verified in the data row, and that only parsed, indexing, and indexed statuses appear.
Business test: Change one piece of content and see whether the version number and references are updated synchronously; check that the current version is unique, old versions are traceable, and references are synchronized, and verify signatures and receipts.
- Open the data row to check the status, confirm that the identities of the file record and the data row are distinguishable, and check that parsed, indexing, and indexed are consistent with the interface display.
- 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 the rebuild chain.