What this category's data looks like
Materials for district and county teaching research activities and classroom observation and evaluation mainly come from three types: teaching research activity notices, classroom observation records, and classroom evaluation minutes. They are updated by week or activity batch, and the fields include activity name, date, teaching or observing personnel, signatures, and receipts. When entering the progress record and statistics verification function, the notice serves as the source for activity initiation and dates, the classroom observation record serves as the source for session and personnel details, and the classroom evaluation minutes serve as the source for evaluation conclusions and signature evidence. The three are grouped by the same activity number, and the progress table summarizes the number of records accordingly. The statistical scope description is written in the table header, noting the inclusion scope, exceptional circumstances, and signature requirements. In the deployment environment, the materials are organized by the business side and then entered into the database. The functional side is only responsible for whether the connection and read/write channels are available, and does not make business judgments on whether the names, quantities, and dates in the two materials match.
Configuration and implementation checks
This part is executed by the connection configuration of the deployment environment (server side), not by the capability of the model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope description" is completed by deployment handover and subsequent business processing. 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 |
|---|---|---|
| Teaching research activity notice | Fields include activity name, date, batch number, and signature; the name and date must be consistent with the classroom observation record and classroom evaluation minutes | In the deployment environment, check that the value of this variable is consistent with the database address, and confirm that the notice record is written to the main business database |
| Classroom observation record | Fields include session, teaching personnel, observing personnel, and signature; the number of records must match the statistical count | Use the client to connect once to the cache instance and check the return; check the selected vector database and address against the deployment instructions |
| Classroom evaluation minutes | Fields include evaluation conclusion, signature, and receipt; the version must be synchronized with the notice and classroom observation record | Check whether the log database variable is set, and check the database to which logs are written; if not configured separately, reuse the main database |
| Progress table and statistical scope description | The table header states the inclusion scope, exceptions, and signature requirements; the total must be verifiable item by item against one week's records | Check that the main business database connection variable points to the main business database actually in use and is connectable |
Three common errors
- Symptom: The name and date of the same activity do not match between the notice and the classroom observation record. Cause: The two materials are entered separately, not grouped by activity number, and the versions are not synchronized.
- Symptom: The classroom evaluation minutes lack a signature or receipt, but the statistics still include them in the total. Cause: The scope description does not state the exceptional circumstances in the table header, and the signature column is not checked item by item during verification.
- Symptom: After startup, the logs continuously report connection timeouts, and retrieval reports vector database errors. Cause: The connection address is inconsistent with the actual instance, or the log database and the main database are mixed in the same place.
How to verify the setup
For this function'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 check that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the database addresses.
Business test: use one week's records to verify the total, see whether the scope and exceptions are clearly written, and check the names, quantities, dates, and signatures of the notices, classroom observation records, and classroom evaluation minutes item by item.
- Check the selected vector database and address against the deployment instructions, and confirm that the connection variables point to the instance actually in use
- Check whether the log database variable is set, and check the database to which logs are written; if not configured separately, reuse the main database according to the instructions