What this category's data looks like
This category's data involves three types of materials: school-enterprise cooperation agreements, order class training plans, and mentor apprenticeship records. Agreements are signed by both the school and the enterprise, training plans are updated by the academic affairs office and departments each semester, and apprenticeship records are submitted weekly by mentors. When the materials enter the progress records and statistical reconciliation function, agreements provide the cooperating entities and terms, training plans provide courses and rotation milestones, and apprenticeship records provide attendance, work hours, and skill items. Field characteristics include record number, student name, mentor name, date, quantity, signature, and receipt. The update rhythm is: agreements by academic year, plans by semester, and apprenticeship records by week. The progress table uses the record number as the key, and the statistical scope must state the counting unit, date range, and exception handling method in the header, so that record counts and statistical counts can be reconciled item by item.
Configuration and implementation checks
This part is executed by the deployment environment's connection configuration (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 scope description" is then completed by deployment handover and subsequent business processing. Connection addresses are configured by 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 | Points to the main business database actually in use and is connectable | In the deployment environment, check that the variable value matches the database address, and connect once with a client |
| Log database connection variable | Configured separately, or left empty per the instructions to reuse the main database | Check whether the variable is set, and verify whether the database written to by logs is separate from the main database |
| Cache connection variable | The cache instance is connectable | Connect once with a client, check the return; compare against the REDIS_URL value |
| Vector database connection variable | Matches the vector database actually in use | Compare against the deployment instructions to check the selected vector database and address; verify the instance corresponding to PG_URL or MONGODB_URI |
Three common errors
- Symptom: the quantity of the same apprenticeship record does not match between the progress table and the statistics table. Cause: the two materials have different update rhythms, versions are not synchronized, and the statistical scope is not written in the header.
- Symptom: student names and dates in the agreement and training plan do not match. Cause: the names and dates of the same record are not unified across the two materials, and signatures or receipts are missing.
- Symptom: after startup, logs continuously report connection timeouts. Cause: the connection variable is inconsistent with the actual database address, or the log database and main database are mixed in the same place, causing write failures.
How to verify the setup
This feature's acceptance: 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 record whether the values of MONGODB_URI, REDIS_URL, and PG_URL match the database addresses.
Business test: use one week of records to reconcile the totals, and see whether the scope and exceptions are clearly stated; the number of citations is the array length, quoteMaxToken is the citation content budget, and the two are not compared for equality. If a citation upper limit is involved, check the tokens of the citation text, and record the array count separately.
- In the deployment environment, check item by item that the connection variable values for the main business database, log database, cache, and vector database match the database addresses, and save the startup logs.
- Use one week of apprenticeship records and the progress table to reconcile the totals, and check whether the header states the counting unit, date range, and exception handling method.