What this category's data looks like
District and county teaching research activity and lesson observation and evaluation materials include three categories: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices come from teaching research department scheduling, lesson observation records are filled in on the spot by the observer, and lesson evaluation minutes are summarized by the lesson evaluation group. The update rhythm advances by activity batch, typically producing one batch every one to two weeks. Field characteristics: notices contain the activity name, date, location, and participation scope; lesson observation records contain the instructor, class, subject, observation points, and observer signature; lesson evaluation minutes contain the evaluation date, speaking points, conclusion, group leader signature, and receipt. When the materials enter the deployment, operations, and application handover function, notices are used to check the activity batch and date, lesson observation records are used to check the quantity and signatures, and lesson evaluation minutes are used to check the version and receipt; together the three support item-by-item verification of the handover form.
Configuration and implementation checks
This link 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). "Handover-ready deployment status and operation records" are then completed by deployment handover and subsequent business processing. The main business database, log database, cache, and vector database can point to different instances respectively; when the log database is not configured separately, it reuses the main database.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | The activity name, date, location, and participation scope correspond item by item with the lesson observation records and lesson evaluation minutes, and dates within the same batch are consistent | Check the notice date against the lesson observation record date according to the handover form, and check whether signatures and receipts are complete |
| Lesson observation record | The instructor, class, subject, observation points, and observer signature are consistent with the quantity and date in the lesson evaluation minutes | Verify the quantity of lesson observation records against the quantity listed in the lesson evaluation minutes one by one, and check the signature fields |
| Lesson evaluation minutes | The evaluation date, speaking points, conclusion, group leader signature, and receipt are complete, and the version is synchronized with the notice batch | Check the minutes version against the notice batch, and check the receipt and signature |
| Deployment connection record | The main business database, log database, cache, and vector database connections are available, and the startup log has no connection timeouts | Connect once to each item, and check the values of MONGODB_URI, REDIS_URL, and PG_URL against the instance addresses |
Three common errors
- Symptom: The name, quantity, and date of the same lesson observation record do not match between the notice and the lesson evaluation minutes. Cause: Materials were entered in batches and were not checked uniformly by batch.
- Symptom: The lesson evaluation minutes version is not synchronized with the notice batch, and the receipt is missing. Cause: During handover, only the quantity was checked, not the version and signature.
- Symptom: After startup, the log continuously reports connection timeouts, and retrieval reports a vector database error. Cause: The connection variable values are inconsistent with the actual instances.
How to verify the setup
This function's acceptance: connect once to each of the main business database, log database, cache, and vector database, check the connection results in the startup log, and compare the values of MONGODB_URI, REDIS_URL, and PG_URL against the instance addresses.
Business test: check once item by item according to the handover form, see which record is missing, and confirm that the dates, quantities, and signatures of the notices, lesson observation records, and lesson evaluation minutes are consistent.
- In the deployment environment, check that the connection variable values of the main business database, log database, cache, and vector database are consistent with the instance addresses, and view the connection results in the startup log
- Check the dates, quantities, signatures, and receipts of the notices, lesson observation records, and lesson evaluation minutes item by item according to the handover form, and record missing items