What this category's data looks like
This page addresses progress records and statistical reconciliation in graduate training process management. The source materials are three types of process materials: training plans, proposal reports, and mid-term assessment forms. The update cadence is weekly recording, monthly aggregation, and archiving by assessment milestone. Training plans carry course and segment arrangements, proposal reports carry topic selection and time nodes, and mid-term assessment forms carry stage conclusions and signature receipts. When these three types of materials enter this feature, they serve respectively as the basis for progress entries, the source of node dates, and the reconciliation draft for statistical criteria. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. The same record often appears in two types of materials with different name spellings, different quantity criteria, and different date values. Statistical reconciliation requires that the record count and the statistical count match, that the criteria be written in the header, and that exceptions be explained separately.
Configuration and implementation checks
This step is executed by the connection configuration of the deployment environment (server side), not by the capability of a model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical criteria description" is then completed by deployment handover and subsequent business processing. Connection addresses are configured via 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 reuses the main database.
| Object | Check | Verification action |
|---|---|---|
Main business database connection variable MONGODB_URI | Points to the main business database actually in use and is connectable; records of training plans, proposal reports, and mid-term assessment forms are stored in this database | In the deployment environment, check that the variable value matches the database address; after startup, check the connection logs for errors |
| Log database connection variable | Configured separately, or left empty per the instructions to reuse the main database; the log write location and the business data location are checked separately | Check whether the variable is set and verify the database to which logs are written; when left empty, confirm the instructions for reusing the main database |
Cache connection variable REDIS_URL | The cache instance is connectable and is used for streaming recovery mirroring and memory watermark detection | Connect once with a client and verify the return; check whether the memory ratio and detection interval affect mirror creation |
Vector database connection variable PG_URL | Matches the vector database actually in use; retrieval uses the full-text and vector channels of the selected vector database | Check the selected vector database and address against the deployment instructions; when retrieval errors occur, check this variable first |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the training plan and the mid-term assessment form. Cause: The two materials are maintained separately, are not backfilled according to the same criteria, and are directly added together during statistics.
- Symptom: The proposal report has been updated, but the progress table still shows the old node date. Cause: The version was not synchronized, the old version continues to participate in statistics, and the version source was not marked during reconciliation.
- Symptom: The mid-term assessment form lacks a signature or receipt but is still counted as completed. Cause: The statistical criteria do not list signature and receipt as completion conditions, and exceptions are not clearly written in the header.
How to verify the setup
Feature acceptance: connect once to the main business database, log database, cache, and vector database item by item, and check the connection results in the startup logs; for the main business database and log database, check MONGODB_URI and the log database variable respectively; for the cache, check REDIS_URL; for the vector database, check PG_URL.
Business test: use one week of records to reconcile the totals and see whether the criteria and exceptions are clearly written; compare the name, quantity, and date of the same record in the two materials item by item, and list those missing signatures or receipts separately.
- In the deployment environment, check the connection variable values and instance addresses of the main business database, log database, cache, and vector database item by item, and record the connection results in the startup logs.
- Extract progress records by week, compare the names, quantities, dates, and signatures against the training plans, proposal reports, and mid-term assessment forms, and write the criteria and exceptions into the header.