What this category's data looks like
This category's data looks like this: Off-campus training compliance filing and penalty response involves three core types of materials: school operating licenses, course filing materials, and fee disclosure. The school operating license contains fields such as the approving authority, validity period, and school address; the course filing materials contain the course name, number of class hours, instructor, and filing date; the fee disclosure contains fee items, standards, refund rules, and disclosure date. These materials come from approval department receipts, internal institution ledgers, disclosure photos, and scanned copies, and their update cadence is driven by license renewal, course adjustments, and fee changes. When the materials enter the document parsing and chunking function, each has a different role: the license serves as the proof of subject qualification, the course filing materials serve as the basis for business scope, and the fee disclosure serves as evidence of price compliance. After parsing is completed, parsed chunks are immediately stored as visible data rows and bound to a unique data identifier for subsequent retrieval and version ledger use.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), outputting data rows and index status (parsed, indexing, indexed). The "version ledger and change records" are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| School operating license | Fields, dates, and signatures must be consistent with the approval receipt, and the name and address must not conflict with the course filing materials | Check the license number, validity period, and issuing authority signature or seal, and compare the institution name in the course filing materials character by character |
| Course filing materials | The course name, number of class hours, instructor, and filing date must correspond to the items in the fee disclosure | Check whether the course names and quantities are consistent in the two materials, and check whether the filing date is earlier than the fee disclosure date |
| Fee disclosure | The fee items, standards, refund rules, and disclosure date must match the course filing materials; missing signatures or receipts are considered incomplete | Check the signatures and receipts of the fee disclosure, and check whether the disclosure date and filing date are updated in sync |
| Data rows and index status | It is in one of the three states parsed / indexing / indexed and is consistent with the interface display; rebuild only covers data whose indexing has been completed | Open the data row to check the status, view the coverage scope of the rebuild task, and confirm the parsing and chunking parameters corresponding to chunkSize, chunkSplitter, and trainingType |
Three common errors
- Phenomenon: The same course name is written differently in the course filing materials and the fee disclosure. Cause: The two materials are maintained by different personnel, and no field-level comparison or version synchronization has been performed.
- Phenomenon: After the school operating license is renewed, the course filing materials still reference the old license number. Cause: The version ledger did not record the change, the old version was not marked invalid, and the references were not updated in sync.
- Phenomenon: The fee disclosure lacks a signature or receipt, so during penalty response it cannot be proven that the disclosure was delivered. Cause: The signature and receipt fields were not verified when the materials were archived, and change records are missing.
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 three states parsed, indexing, and indexed are consistent with the interface display, and that rebuild only covers data whose indexing has been completed.
Business test: Change one piece of content and see whether the version number and references are updated in sync.
- Open the data row to check the status, confirm that the identities of the file record and the data row are kept separate, and verify the file record and the data row separately.
- View the data rows covered by the rebuild task, confirm that only data whose indexing has been completed is covered, and that data pending indexing does not participate in recall.