What this category's data looks like
This page addresses the grade entry and credit recognition scenario, and the materials include three types: transcripts, deferred examination applications, and make-up examination arrangements. The transcript is the primary evidence for credit recognition, and its fields include course name, credits, grade, instructor signature, and date; the deferred examination application records the student, course, reason for deferral, and approval signature; the make-up examination arrangement records the make-up examination time, location, invigilator, and receipt. When these three types of materials enter the deployment and operations function, each plays a different role: transcripts are used to check credits and grade fields, deferred examination applications are used to check the approval chain and dates, and make-up examination arrangements are used to check sessions and receipts. The material sources are academic affairs system exports and scans of paper signed documents, the update cadence advances by semester and examination cycle, and the field characteristics are multi-table intersection with signatures and dates coexisting. Deployment status and operation records need to align version, connection, and task records, and during handover each item is checked against the materials.
Configuration and implementation checks
This step is determined by the connection configuration of the deployment environment (server side), not by the capability execution of a model node, and it outputs whether the connection is available (service startup result and connection logs). "Handover-ready deployment status and operation records" are then completed by deployment handover and subsequent business processing. The connection address is configured by environment variables, and the primary business database, log database, cache, and vector database can point to different instances respectively.
| Object | Check | Verification action |
|---|---|---|
| Transcript | Course name, credits, grade, instructor signature, and date are consistent across the three materials | Compare the transcript with the credit recognition record, and check whether the fields, dates, and signatures are complete |
| Deferred examination application | Student, course, reason for deferral, approval signature, and date are traceable | Check whether the course names and dates in the deferred examination application and the make-up examination arrangement match |
| Make-up examination arrangement | Make-up examination time, location, invigilator, and receipt are complete, and the version is synchronized | Check the make-up examination arrangement and receipt item by item according to the handover form, and see which record is missing |
| Primary business database connection variable | Points to the primary business database actually in use and can be connected | In the deployment environment, check that the variable value is consistent with the database address, and view the startup logs |
Three common errors
- Symptom: The name, quantity, or date of the same course does not match across two materials. Cause: The transcript and the deferred examination application were entered separately and were not checked against the same record.
- Symptom: The make-up examination arrangement has been updated, but the transcript still shows the old version. Cause: The version was not synchronized, and the version and task records were not checked during handover.
- Symptom: The deferred examination application is missing an approval signature or receipt. Cause: Signatures were not collected during the material circulation step, and the handover form did not check the records item by item.
How to verify the setup
This function's acceptance: connect once to the primary business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and check that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the instance addresses.
Business test: check once item by item according to the handover form, and see which record is missing.
- In the deployment environment, check that the values of
MONGODB_URI,REDIS_URL, andPG_URLare consistent with the instance addresses, and view the connection results in the startup logs. - Check the fields, dates, and signatures of the transcripts, deferred examination applications, and make-up examination arrangements item by item according to the handover form, and record the missing items.