What this category's data looks like
This page addresses the scenario of course scheduling and class cancellation in training institutions. Material sources include class schedules, class cancellation records, schedule change requests, signed receipts, and version ledgers. Class schedules carry fields for course, teacher, class, time slot, and classroom; class cancellation records carry fields for student, class hours, date, and signature; schedule change requests carry fields for original session, target session, reason, and approval; version ledgers carry fields for version number, effective date, change description, and reference location. The update rhythm rolls with scheduling adjustments, temporary schedule changes, supplementary signed receipts, and version releases. When materials enter parsing and training tasks, their roles differ: class schedules and class cancellation records serve as data row sources, schedule change requests and receipts serve as change evidence, and version ledgers serve as the verification draft for reference synchronization. Field characteristics concentrate in four categories: dates, names, quantities, and signatures. When the same record does not match across two materials, first locate the data row status, then verify the version number and reference location.
Configuration and implementation checks
Parsing and training tasks (server-side tasks) only output data rows and index statuses (parsed, indexing, indexed). Version ledgers and change records must be handled next 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: parsed, indexing, and indexed. Data pending indexing does not participate in recall. When changing models, only data with completed indexing is rebuilt.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Course name, class, teacher, time slot, classroom, and effective date are consistent between the class schedule and the schedule change request, and the version number points to the current version | Open the data row verification status, separately verify the file record and the data row, and confirm that the chunks produced by chunkSize and chunkSplitter cover the class schedule fields |
| Class cancellation record | Student, class hours, class cancellation date, and signed receipt match across the two materials; rows missing a signature or receipt are marked separately | Compare class cancellation records and receipts one by one by date and student, and check whether the index status is one of parsed / indexing / indexed and consistent with the interface display |
| Schedule change request | Original session, target session, reason for change, and approval signature are complete; when the version is not synchronized, the old version is traceable and the reference location points to the current version | Verify the dates and signatures of the schedule change request against the class schedule and class cancellation records, and confirm the processing mode corresponding to trainingType and the data rows covered by the rebuild task |
| Version ledger | The current version is unique, old versions are traceable, references are updated synchronously, and the version number and effective date are consistent between the ledger and external documents | After changing one piece of content, check whether the version number and references are updated synchronously, and verify that the rebuild task only covers data rows with completed indexing |
Three common errors
- Symptom: The same class cancellation record does not match in student name, class hours, or date between the class schedule and the class cancellation record. Cause: The two materials are persisted separately and fields are not compared by the same data identifier.
- Symptom: A schedule change request has been approved, but the class schedule still shows the old session, and the reference location points to the old version. Cause: The version was not synchronized, the rebuild only covers data with completed indexing, and the old version was not traced.
- Symptom: A class cancellation record missing a signature or receipt is still referenced as the current version. Cause: The signature field was not included in the version ledger verification, and rows missing a receipt were not marked separately.
How to verify the setup
Feature acceptance: Upload one material, observe the data row status transitions and the coverage of the rebuild task, and confirm that parsed chunks are immediately persisted as visible data rows after parsing is complete, the index transitions through the three states parsed / indexing / indexed, data pending indexing does not participate in recall, and when changing models only data with completed indexing is rebuilt.
Business test: Change one piece of content, check whether the version number and references are updated synchronously, and confirm that the current version is unique, old versions are traceable, and reference locations are synchronized.
- Open the data row verification status, separately verify the file record and the data row, and confirm that
chunkSize,chunkSplitter,trainingType, and the index status display are consistent. - Compare the fields, dates, and signatures of the class schedule, class cancellation records, and schedule change requests one by one, record rows missing signatures or receipts separately from rows with unsynchronized versions, and then decide whether to update the knowledge base or external documents.