What this category's data looks like
This page focuses on progress records and statistical verification for degree conferral and certificate information reporting, involving three types of materials: degree application forms, thesis review reports, and defense resolutions. The degree application form carries the applicant's basic information and degree category fields, and after entering this function serves as the source of the record primary key; the thesis review report provides the review conclusion and review date, used to verify whether the name and date of the same record are consistent; the defense resolution provides the defense conclusion, voting result, and signature field, used to verify whether the signature or receipt is complete. Materials are updated according to the batch reporting rhythm, and each batch contains newly added, changed, and revoked records. In terms of field characteristics, all three types of materials contain name, student ID, major, date, and signature field; the way names are written may differ across materials, and quantity fields need to be merged according to the statistical basis during aggregation. The progress table registers the number of records by batch, and the explanation of the statistical basis is written in the table header, clarifying the exceptions that are included and excluded.
Configuration and implementation checks
This part 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 basis explanation" is then completed by deployment handover and subsequent business processing. The connection address is configured by environment variables, and the main business database, log database, cache, and vector database can point to different instances respectively.
| Object | Check | Verification action |
|---|---|---|
| Degree application form | Whether the fields, dates, and signatures match the thesis review report and defense resolution | Verify the writing of name, student ID, major, and degree category; compare the dates of the same record; check whether the signature field is complete, and the connection variable uses MONGODB_URI |
| Thesis review report | Whether the review conclusion and review date are consistent with the defense resolution | Compare the name and quantity of the same record in the two materials; verify the order of the review date and defense date; confirm whether the versions are synchronized, and the connection variable uses PG_URL |
| Defense resolution | Whether the defense conclusion, voting result, and signature receipt are complete | Verify the defense conclusion and voting result; check whether the signature or receipt is missing; compare the name and quantity of the same record, and the connection variable uses REDIS_URL |
| Progress table and statistical basis explanation | Whether the number of records and the statistical count match, and whether the basis is written in the table header | Register the number of records by batch; write the included and excluded exceptions in the table header; use one week of records to verify the total |
Three common errors
- Phenomenon: The name, quantity, or date of the same record does not match between the degree application form and the defense resolution. Cause: The two materials were entered separately and were not merged and verified according to the same primary key.
- Phenomenon: The versions of the thesis review report and defense resolution are not synchronized, and the old version conclusion is included in the statistics. Cause: After changes, updates were not made by batch, and the progress table did not indicate the version.
- Phenomenon: The defense resolution lacks a signature or receipt but is still included in the total. Cause: The basis did not state the exception in the table header, and records without completed signatures were not excluded during statistics.
How to verify the setup
Acceptance of this function: connect once to the main business database, log database, cache, and vector database item by item, and verify the connection results in the startup logs.
Business test: use one week of records to verify the total, and see whether the basis and exceptions are clearly written.
- In the deployment environment, verify that the value of this variable is consistent with the database address, check whether the log database variable is set, and verify the database to which logs are written.
- Use the client to connect once to the cache instance and verify the return; check the selected vector database and address against the deployment instructions.