What this category's data looks like
This page focuses on progress records and statistical reconciliation for off-campus training compliance filing and penalty response. The materials include three categories: school operation licenses, course filing materials, and fee disclosure. The school operation license states the institution name, license number, validity period, and issuance date; the course filing materials include the course name, number of class hours, filing date, and handler signature; the fee disclosure includes fee items, amounts, disclosure date, and receipt. The sources are original documents or scanned copies of each material, collected weekly and summarized monthly, with fields mainly consisting of names, quantities, dates, and signatures. When entering this function, the school operation license serves as the subject qualification record, the course filing materials serve as the course detail records, and the fee disclosure serves as the fee and disclosure records. Together, the three support the reconciliation of the progress table and the statistical scope statement.
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, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope statement" is then completed by the deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| School operation license | The institution name, license number, validity period, issuance date, and signature are complete, and the institution name is consistent with that in the course filing materials | In the deployment environment, check that the value of this variable is consistent with the database address, connect once to the main business database item by item, and view the connection result in the startup logs |
| Course filing materials | The course name, number of class hours, filing date, and handler signature are complete, and the course name and quantity match those in the fee disclosure | Connect once to the log database item by item, check whether the variable is set and verify the database to which logs are written, and check the selected vector database and address against the deployment instructions |
| Fee disclosure | The fee items, amounts, disclosure date, and receipt are complete, and the date and quantity match those in the course filing materials | Use the client to connect once to the cache, check the returned result, connect once to the vector database item by item, and check the connection result in the startup logs |
Three common errors
- Symptom: The name and quantity of the same course do not match across two materials. Cause: During collection, registration was not performed according to a unified scope, and the table header did not specify the statistical scope and exceptions.
- Symptom: The versions of the school operation license or fee disclosure were not synchronized. Cause: Old versions of the materials are still in circulation, and after updating they were not replaced and marked with an effective date.
- Symptom: The course filing materials lack the handler signature or the fee disclosure lacks the receipt. Cause: During the handover step, signatures and receipts were not checked item by item, and the records directly entered the summary.
How to verify the setup
This function's acceptance: connect once to the main business database, log database, cache, and vector database item by item, and check the connection results in the startup logs; check whether the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the database addresses.
Business test: use one week of records to check the totals and see whether the scope and exceptions are clearly stated; the number of records and the statistical count should match, and the scope should be written in the table header.
- Check that
MONGODB_URIis consistent with the main business database address, and view the connection result in the startup logs. - Check that the
REDIS_URLcache instance is connectable, and use the client to connect once to verify the returned result.