What this category's data looks like
Continuing education credit hour recognition involves three types of materials: course filing forms, study certificates, and credit hour recognition forms. Course filing forms come from course providers and record the course name, filing date, and course number; study certificates are generated by the learning platform and include the learner, course name, completion date, and certificate number; credit hour recognition forms are filled out by the recognizing organization and include the learner, recognized course, recognized quantity, recognition date, and signature. When these three types of materials enter the deployment, operations, and application handover function, the course filing form serves as the course source, the study certificate serves as the learning fact, and the credit hour recognition form serves as the recognition result, together forming a handover-ready deployment state and operation records. The update rhythm is submission by batch and handover by shift, and the field characteristics are that names, quantities, dates, and signatures must be aligned item by item.
Configuration and implementation checks
This step is handled by the connection configuration of the deployment environment (server side), not by the capability execution of a model node, and outputs whether the connection is available (service startup result and connection logs). "Handover-ready deployment state and operation records" are then completed by deployment handover and subsequent business processing. Connection addresses are configured through environment variables: the main business database, log database, cache, and vector database can point to different instances respectively; if the log database is not configured separately, it will reuse the main database.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | The course name, filing date, and course number must be aligned item by item with the study certificate and credit hour recognition form; the name, quantity, and date of the same record in the two materials must not mismatch | Compare the course filing form with the study certificate, check whether the course name, number, and filing date are consistent, and check whether the signature and receipt are complete |
| Study certificate | The learner, course name, completion date, and certificate number must be consistent with the course filing form and credit hour recognition form; when versions are not synchronized, the latest filed version shall prevail | Check the course name, quantity, and date of the study certificate and credit hour recognition form item by item according to the handover sheet, and check which record is missing |
| Credit hour recognition form | The recognized course, recognized quantity, recognition date, and signature must be consistent with the course filing form and study certificate; handover is not allowed when the signature or receipt is missing | Check the signature and receipt of the credit hour recognition form, confirm that the recognized quantity is consistent with the completed quantity in the study certificate, and record missing items |
| Deployment connection status | The connection variables for the main business database, log database, cache, and vector database are consistent with the actual instances, and the startup log has no connection timeout | In the deployment environment, check that the variable values are consistent with the database addresses, connect once to the cache with a client, and check the selected vector database and address against the deployment instructions |
Three common errors
- Symptom: The course name, quantity, and date of the same record in the course filing form and study certificate do not match. Cause: The two materials are entered separately and are not checked by batch, and during handover only the total is looked at without item-by-item comparison.
- Symptom: The credit hour recognition form lacks a signature or receipt, and the study certificate version is not synchronized. Cause: The handover sheet does not list the signature item, and after the course filing form is updated it is not synchronized to the study certificate and recognition form.
- Symptom: After startup, the log continuously reports connection timeouts, business data and logs are mixed in the same place, and retrieval reports a vector database error. Check: The connection variables are inconsistent with the actual instances. Logs use the primary database when no separate log database is configured; inspect the actual log destination separately.
How to verify the setup
Acceptance for this function: connect once item by item to the main business database, log database, cache, and vector database, and check the connection results in the startup log; in the deployment environment, check that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the database addresses, and confirm that the log database is configured separately or left empty to reuse the main database according to the instructions.
Business test: check once item by item according to the handover sheet to see which record is missing; check the fields, dates, and signatures of the course filing form, study certificate, and credit hour recognition form, and confirm that the version, connection, and task records are consistent.
- In the deployment environment, check that the connection variable values for the main business database, log database, cache, and vector database are consistent with the database addresses, check the connection results in the startup log, and record missing items.
- Check the names, quantities, dates, and signatures of the course filing form, study certificate, and credit hour recognition form item by item according to the handover sheet, and confirm version synchronization and complete receipts.