What this category's data looks like
The materials for the establishment and annual reports of Chinese-foreign cooperative education institutions come from establishment applications, cooperation agreements, articles of association, and annual report receipts, updated by batch, with fields including institution name, number of programs, enrollment date, signatures, and receipts. The establishment application provides the institution name and education level, the cooperation agreement provides programs and student numbers, the articles of association provide governance and signature pages, and the annual report receipt provides annual data. When the materials enter progress records and statistical verification, each assumes the comparison role for the four types of fields: name, quantity, date, and signature, forming a progress table and a statement of statistical criteria.
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 statement of statistical criteria are then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | Institution name, number of programs, date, and signature are consistent within the application; when compared with the cooperation agreement and articles of association, the same name, same number, and same date | Check the application fields one by one, and compare side by side with the cooperation agreement and articles of association for name, quantity, date, and signature pages |
| Cooperation agreement | Programs and student numbers, signing date, and signature are consistent within the agreement; when compared with the application and articles of association, there are no discrepancies in name or quantity | Check the agreement's programs and student numbers, cross-compare dates and signatures with the application and articles of association, and record inconsistencies |
| Articles of association | Governance clauses and signature pages are complete; when compared with the application and cooperation agreement, the institution name and date are consistent | Check the articles' signature pages and receipt, compare names and dates with the application and cooperation agreement, and mark items whose versions are not synchronized |
| Annual report receipt | Annual record counts match the statistical counts; criteria are written in the header, and exceptions are clearly stated | Use one week of records to check the totals, check the receipt against the progress table criteria, and inspect the exception notes |
Three common errors
- Phenomenon: The institution name, number of programs, or date of the same record do not match between the application and the cooperation agreement. Cause: The two materials were filled out separately without cross-checking, causing the statistical criteria to diverge.
- Phenomenon: The articles' signature page is missing or the receipt has not been returned, yet the progress table still records it as complete. Cause: Versions are not synchronized, and signature and receipt statuses are not updated with the materials.
- Phenomenon: After startup, the logs continuously report connection timeouts, and business data and logs are mixed in the same place. Check: The instance pointed to by the connection variable is unreachable. Logs use the primary database when no separate log database is configured; inspect the actual log destination separately.
How to verify the setup
Acceptance of this feature: connect once to the primary business database, log database, cache, and vector database item by item, and check the connection results in the startup logs; check that the values of MONGODB_URI, REDIS_URL, and PG_URL match the database addresses, and when the log database is not configured separately, confirm that it reuses the primary database.
Business test: use one week of records to check the totals, and see whether the criteria and exceptions are clearly stated.
- In the deployment environment, check that the variable value matches the database address, check whether the log database variable is set, and check the database to which logs are written.
- Connect once to the cache with a client, check the return, and check the selected vector database and address against the deployment instructions.