What this category's data looks like
This category's data involves three types of materials: the master timetable, the teacher assignment table, and the after-school service project table, which come respectively from the academic affairs office, the grade group, and the after-school service management post, and are updated on three rhythms: the start of the semester, the end of the month, and after adjustments. The master timetable records class, period, course name, and assigned teacher; the teacher assignment table records teacher, class, subject, and weekly class hours; the after-school service project table records project name, number of participating students, venue, time slot, and signed receipt. When the three types of materials enter this function, the master timetable and the teacher assignment table are used to check the assignment and class-hour fields, and the after-school service project table is used to check the project count, dates, and signatures. The field characteristic is that the name, quantity, and date of the same record in different materials must be aligned item by item, and the version must be marked as current or historical.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), which outputs data rows and index status (parsed, indexing, indexed). The basis entries that can be traced back to the original text are then completed by retrieval and subsequent processing. After parsing is completed, parsing and chunking immediately persist to the database as visible data rows and bind a unique data identifier; the index transitions through three states; data pending indexing does not participate in recall; changing the model only rebuilds data whose indexing is already completed.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | The class, period, course name, and assigned teacher fields align item by item with the teacher assignment table, and the version is current and includes a signature | Open the data row to check the status, confirm that the parsing and chunking parameters chunkSize and chunkSplitter are recorded consistently, and that the status is one of parsed / indexing / indexed |
| Teacher assignment table | The teacher, class, subject, and weekly class hours match the same record's name, quantity, and date in the master timetable; missing signatures or receipts must be flagged | Check the file record and the data row separately, confirm that trainingType matches the processing mode, and that the rebuild task only covers data rows whose indexing is already completed |
| After-school service project table | The project name, number of participating students, venue, and time slot match the after-school time slot in the master timetable; if the version is not synchronized, it must be traced back to the original text | View the data rows covered by the rebuild task, confirm that the initial training covers data pending indexing and data indexing, and that the rebuild targets only data whose indexing is already completed |
Three common errors
- Symptom: materials just uploaded cannot be found. Cause: successful parsing does not equal a retrieval hit; data pending indexing is naturally isolated at the retrieval layer, and you must wait for the index status to transition to completed.
- Symptom: the name, quantity, and date of the same record do not match across two materials. Cause: the versions of the master timetable and the teacher assignment table are not synchronized, signatures or receipts are missing, and the entry cannot be traced back to the original text.
- Symptom: empty data rows are left after training fails. Cause: the initial training covers data pending indexing, failed data is not edited or deleted in time, and the index status does not return to completed.
How to verify the setup
This function's acceptance: upload one material and observe the data row status transitions and the coverage scope of the rebuild task. Check that the data row is in one of parsed / indexing / indexed and is consistent with the interface display, confirm that the rebuild covers only data whose indexing is already completed, that the initial training covers data pending indexing and data indexing, and check the records of chunkSize, chunkSplitter, and trainingType.
Business test: ask a cross-material basis question and see whether the answer gives a traceable source. For example, ask whether the assigned teacher for the same class and same course is consistent between the master timetable and the teacher assignment table; the answer must give the material name, version, and original text location.
- Open the data row to check the status, confirm it is consistent with the interface display, check the file record and the data row identity separately, and view the data rows covered by the rebuild task.
- Check the fields, dates, and signatures of the master timetable, the teacher assignment table, and the after-school service project table, compare the name, quantity, and date of the same record across the two materials item by item, and flag items whose versions are not synchronized and items missing signatures or receipts.