What this category's data looks like
In the course selection, scheduling, and classroom resource allocation category, material sources include course offering plans, scheduling tables, course selection rules, and multilingual reference drafts, with update cadence rolling with semester rounds and version revisions. Course offering plans carry course code, credits, and offering unit fields; scheduling tables carry classroom, time slot, week, and instructor fields; course selection rules carry selection target, capacity, and prerequisite fields; multilingual materials carry terminology translations and mapping relationships. When these materials enter document parsing and chunking, each plays a different role: course offering plans and course selection rules serve as stable sources for terminology extraction, scheduling tables serve as the verification draft for date and classroom fields, and multilingual reference drafts serve as the reference for mapping translated names back to the source text. Field characteristics manifest as the same term appearing repeatedly in course offering plans, scheduling tables, and course selection rules, with dates and signature fields distributed across different materials, requiring item-by-item comparison according to the category's verification dimensions.
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 unified terminology table and reference drafts are then completed by retrieval and subsequent processing. After parsing is complete, parsed chunks are immediately persisted as visible data rows and bound to a unique data identifier; the index transitions through three states; data pending indexing does not participate in recall; and when the model is changed, only data with completed indexing is rebuilt.
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | Verify course code, credits, and offering unit fields; the name, quantity, and date of the same record in the scheduling table and course selection rules must match | Verify the file record and the data row separately, confirm the chunkSize and chunkSplitter settings, then check whether the data row status is parsed or indexed |
| Scheduling table | Verify classroom, time slot, week, and instructor fields; when versions are not synchronized, the date of the same record in the two materials does not match | Open the data row to verify the status, and confirm that the training mode corresponding to trainingType is consistent with the three index states |
| Course selection rules | Verify selection target, capacity, and prerequisite fields; when a signature or receipt is missing, the record must not enter external release | Sample three terms and check whether their spelling is consistent throughout the document, and verify whether the data rows covered by the rebuild task are only indexed |
| Multilingual reference draft | Verify that translated names can refer back to the source text, that the same term is consistent throughout, and that entries in the terminology table and reference draft correspond one by one | Verify the respective identities of the file record and the data row, and confirm that the file record and the data row can be distinguished |
Three common errors
- Symptom: The name, quantity, and date of the same course do not match between the course offering plan and the scheduling table. Cause: The two materials' versions are not synchronized, and after parsing they are not merged under the same data identifier.
- Symptom: Course selection rules lack a signature or receipt but still enter the external release process. Cause: Material sources are not compared item by item according to the category's verification dimensions, and the receipt field is not verified.
- Symptom: Newly uploaded materials cannot be found. Cause: Successful parsing does not equal a guaranteed retrieval hit; when a data row is in parsed or indexing status, it does not participate in recall.
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, and confirm that the status transitions among parsed, indexing, and indexed and that rebuild covers only indexed data rows.
Business test: Sample three terms and check whether their spelling is consistent throughout the document, and verify that translated names can refer back to the source text.
- Open the data row to verify the status, confirm it is consistent with the interface display, and verify the file record and the data row separately.
- Check the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and that initial training covers data pending indexing and indexing.