What this category's data looks like
This page addresses progress records and statistical verification in the investigation and handling of academic misconduct reports. The materials come from three categories: report materials, investigation reports, and expert appraisal opinions. They are updated weekly or monthly, and the fields include name, quantity, date, and signature. When report materials enter the function, they serve as the original record source, providing the reported matter and preliminary facts; investigation reports serve as process records, carrying the investigation stages and conclusions; expert appraisal opinions serve as independent judgment materials, supplementing professional conclusions. The three categories of materials each occupy their own rows in the progress table. The statistical scope must state in the table header the correspondence between the number of records and the statistical count, and exceptional cases must be marked separately. The material version is based on the latest signature or receipt; versions that are not synchronized must be marked during verification.
Configuration and implementation checks
This step is performed by the connection configuration of the deployment environment (server side), not by the capability execution of a model node. It outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope description" is then completed by the deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Report materials | Name, quantity, date, and signature must be consistent with the investigation report | Compare the same record in the report materials and the investigation report item by item, verify the name, quantity, date, and signature, and state the statistical scope in the header of the progress table |
| Investigation report | Version is synchronized and date and signature are complete | Check the version and date of the investigation report against the expert appraisal opinions, check whether signatures or receipts are missing, and record exceptions |
| Expert appraisal opinions | Name, quantity, date, and signature must be consistent with the investigation report | Compare the same record in the expert appraisal opinions and the investigation report item by item, verify the name, quantity, date, and signature, and mark inconsistencies |
| Main business database, log database, cache, and vector database connections | Each connection address matches the actual instance in use and is connectable | In the deployment environment, verify that the values of MONGODB_URI, REDIS_URL, and PG_URL match the database addresses, and check the connection results in the startup logs |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the report materials and the investigation report. Cause: The two sets of materials were not organized under the same scope, and the progress table did not state the statistical scope and exceptions in the header.
- Symptom: The version of the investigation report is not synchronized, and the expert appraisal opinions cite conclusions from an old version. Cause: After the version update, it was not marked in the progress table, and the latest signature or receipt was not compared during verification.
- Symptom: The report materials or investigation report lack a signature or receipt, but the progress table still includes them in the total. Cause: The statistical scope did not list signature and receipt as inclusion conditions, and exceptions were not recorded separately.
How to verify the setup
In the deployment environment, verify the values of the connection variables for the main business database, log database, cache, and vector database, and check the service startup result and connection logs.
Use one week of records to compare the name, quantity, date, and signature of the report materials, investigation report, and expert appraisal opinions item by item, and verify the total and statistical scope.
- Connect once to the main business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and verify that the values of
MONGODB_URI,REDIS_URL, andPG_URLmatch the database addresses. - Use one week of records to verify the total and see whether the scope and exceptions are clearly stated.