What this category's data looks like
This page addresses the category of investigation and handling of academic misconduct reports. Materials include report materials, investigation reports, and expert appraisal opinions. Report materials come from intake channels and are updated according to the pace of case intake; investigation reports are written by the investigation team and updated as the investigation progresses; expert appraisal opinions are issued by experts and updated according to the appraisal schedule. Field characteristics center on names, quantities, dates, and signatures: report materials require reporter information, the matter reported, and the submission date; investigation reports require the investigation process, findings and conclusions, the report date, and signatures; expert appraisal opinions require the appraisal matter, appraisal conclusion, expert signature, and date. When the materials enter the deployment, operations, and application handover function, each participates as an independent record in the handover verification, and their ownership does not change due to a shared connection.
Configuration and implementation checks
This part is handled 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 the deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Report materials | Names, quantities, dates, and signatures must correspond item by item with the investigation report and expert appraisal opinions; the same record must not have inconsistent names or quantities | Verify the material fields in the deployment environment, confirm that the names, quantities, and dates in the report materials are consistent with the investigation report and expert appraisal opinions, and check whether signatures or receipts are complete |
| Investigation report | The version must be synchronized with the expert appraisal opinions, and the report date and signatures must be complete; signatures or receipts must not be missing | Verify the investigation report version, date, and signatures item by item according to the handover form, confirm that it is synchronized with the version of the expert appraisal opinions, and record any missing items |
| Expert appraisal opinions | The appraisal matter, conclusion, expert signature, and date must correspond with the investigation report; dates or quantities must not fail to match | Verify the appraisal matter, conclusion, signature, and date of the expert appraisal opinions, compare them item by item with the investigation report, and confirm that there are no inconsistencies in names, quantities, or dates |
| Primary business database connection variable | Points to the primary business database actually in use and can connect; the value of MONGODB_URI is consistent with the database address | Verify in the deployment environment that the value of this variable is consistent with the database address, and check the connection result in the service 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 materials are entered independently, and fields and dates are not verified item by item according to the handover form.
- Symptom: The version of the investigation report is not synchronized with the version of the expert appraisal opinions, and the old version is still used during handover. Cause: After the version update, it was not synchronized to the handover record, and a version verification step is missing.
- Symptom: The report materials or investigation report lack signatures or receipts, and the handover form cannot be closed. Cause: Signatures and receipts were not archived together with the materials, and they were not checked item by item during handover.
How to verify the setup
This function's acceptance: connect once item by item to the primary business database, log database, cache, and vector database, and check the connection results in the startup logs; verify that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the deployment instructions, and confirm whether the connections are available.
Business test: verify once item by item according to the handover form, and see which record is missing, including the names, quantities, dates, and signatures of the report materials, investigation report, and expert appraisal opinions.
- In the deployment environment, verify that the values of
MONGODB_URI,REDIS_URL, andPG_URLare consistent with the database addresses, and check the connection results in the service startup logs. - Verify the names, quantities, dates, and signatures of the report materials, investigation report, and expert appraisal opinions item by item according to the handover form, record missing items, and hand them over to the next shift.