What this category's data looks like
Continuing education credit recognition materials typically include course filing forms, study certificates, and credit recognition forms. Their sources are scattered across training institutions, employers, and individual submission channels, and their update cadence rolls forward with training batches and recognition cycles. Course filing forms focus on course name, credit hours, filing date, and institutional signature; study certificates focus on learner name, course name, completion date, and issuing unit seal; credit recognition forms focus on recognized credit hours, recognition date, and review signature. After these three types of materials enter the parsing and chunking stage, each is stored as an independent data row. Course filing forms provide the course-dimension baseline, study certificates provide the fact of individual completion, and credit recognition forms provide the recognition conclusion. When fields, dates, and signatures are compared across materials, inconsistencies in names, quantities, and dates easily arise. If old-version references are not synchronized after a version change, the ledger and the knowledge base become disconnected.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), which output data rows and index status (parsed, indexing, indexed). The version ledger and change records are then completed by retrieval and subsequent processing. After parsing is complete, parsing chunks are immediately stored as visible data rows and bound to a unique data identifier. The index transitions through three states, and data pending indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | Fields, dates, and signatures must be aligned item by item with the study certificate and credit recognition form, and names and credit hours must not be mutually exclusive | Verify the course name, credit hours, filing date, and institutional signature, and compare against records with the same name in the other two materials |
| Study certificate | Learner name, course name, completion date, and issuing unit seal must be consistent with the filing form and recognition form | Verify the name, course name, completion date, and seal, and check whether the receipt or signature is missing |
| Credit recognition form | Recognized credit hours, recognition date, and review signature must form a closed loop with the filing form and study certificate | Verify the recognized credit hours, recognition date, and review signature, and check whether old-version references are synchronized |
| Data rows and index status | Must be in one of the three states and consistent with the interface display; rebuilds only cover data whose indexing has been completed | Open the data row to verify the status, and check chunkSize, chunkSplitter, trainingType, and the coverage scope of the rebuild task |
Three common errors
- Symptom: The name or credit hours of the same course do not match between the filing form and the study certificate. Cause: The two materials are stored separately, fields are not aligned across materials, and references are not updated synchronously after a version change.
- Symptom: The credit recognition form lacks a review signature or the study certificate lacks a receipt. Cause: Signature and receipt fields are not included in parsing and chunking validation, and missing items are not marked when materials enter the knowledge base.
- Symptom: Newly uploaded materials cannot be found, and failed training leaves empty data rows. Cause: Successful parsing does not equal a retrieval hit; data pending indexing does not participate in recall, and it is referenced before the index status is completed.
How to verify the setup
This feature acceptance: upload one material and observe the data row status transitions and the coverage scope of the rebuild task.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Open the data row to verify whether the status is parsed, indexing, or indexed, and confirm that it is consistent with the interface display.
- Verify the identity identifiers of the file record and the data row separately, and confirm that the rebuild task only covers data rows whose indexing has been completed.