What this category's data looks like
This page addresses the primary and secondary school timetable and after-school service scheduling scenario. The materials come from the master timetable, teacher assignment tables, after-school service project tables, and their multilingual reference versions, with updates advancing alongside semester scheduling adjustments, project additions and removals, and version revisions. When the three types of materials enter the document parsing and chunking stage, their roles differ: the master timetable serves as the primary record for school-wide periods and class dimensions, the teacher assignment table provides the assigned teachers and period-hour attribution, and the after-school service project table records project names, participant counts, and start and end dates. Field characteristics center on course names, teacher names, classes, periods, dates, signatures, and receipts, and multilingual materials also need to preserve the correspondence between source text and translated names. After parsing and chunking, retrievable data rows are formed, providing a consistent chunking basis for the unified terminology table and reference versions.
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 "unified terminology table and reference versions" are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Check whether classes, periods, dates, and signature receipts correspond one by one with the teacher assignment table | Open the data rows to check the status, confirm whether they are in parsed, indexing, or indexed, and compare the course names and periods in the two materials |
| Teacher assignment table | Check whether the assigned teachers, period-hour counts, and signatures are consistent with the same record in the master timetable | Check the file records and data rows separately, confirm that the identities of the file records and data rows are distinguishable, and check whether the versions are in sync |
| After-school service project table | Check whether project names, participant counts, start and end dates, and receipts are consistent with the reference versions | View the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and spot-check whether translated names can refer back to the source text |
| Multilingual reference versions | Check whether the same term is written consistently throughout and whether translated names can refer back to the source text | After adjusting chunkSize, chunkSplitter, and trainingType, observe the data row status transitions and the rebuild scope |
Three common errors
- Symptom: The name, quantity, or date of the same course does not match between the two materials. Cause: Multilingual materials and terminology are not unified, each segment is stored independently after chunking, and there is a lack of reference-version back-reference checking.
- Symptom: The master timetable and teacher assignment table versions are not in sync, and the after-school service project table is still the old version. Cause: Materials enter parsing and training in batches, and the index status is not uniformly refreshed according to the completed scope.
- Symptom: The after-school service project table lacks signatures or receipts, which are only discovered before external release. Cause: Signature and receipt fields are not included in the chunking check dimensions, and retrieval results only cover the main text and not the attachments.
How to verify the setup
This feature's acceptance: upload one material and observe the data row status transitions and the coverage scope of the rebuild task.
Business test: sample three terms and check whether their writing is consistent throughout.
- Open the data rows to check the status, confirm whether they are in parsed, indexing, or indexed and consistent with the interface display.
- Check the file records and data rows separately, and confirm that the identities of the file records and data rows are distinguishable.