What this category's data looks like
This page is for the kindergarten safety protection and emergency drills category. Materials include hazard items and rectification deadlines, drill participant counts and sign-ins, access control and school bus check items, and responsible person signatures. Sources are daily inspections, drill plans, and shift handover records, with updates rolling by shift and drill cycle. When materials enter the database and operations function, their roles differ: hazard items and rectification deadlines are business objects awaiting closure, drill sign-ins and plans are process evidence, access control and school bus check items are item-by-item verification checklists, and responsible person signatures are handover confirmations. This function only handles deployment status and operation records, keeping version, connection, and task records consistent, to facilitate handover to operations or the next shift.
Configuration and implementation checks
This link is determined 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). "Handover-ready deployment status and operation records" are completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Primary business database connection variable | Points to the primary business database actually in use and is connectable; business materials such as hazard items and rectification deadlines, drill sign-ins, etc. are stored in this database | In the deployment environment, check that the variable value matches the database address, and connect to it item by item once |
| Log database connection variable | Configured separately, or left empty per instructions to reuse the primary database; operation traces of missed check items and responsible person signatures are written here | Check whether the variable is set, and verify the database to which logs are written |
| Cache connection variable | The cache instance is connectable, used for streaming recovery mirroring and temporary state | Connect once with a client, and verify the return |
| Vector database connection variable | Consistent with the vector database actually in use; when retrieval reports a vector database error, check here first | Check the selected vector database and address against the deployment instructions |
Three common errors
- Symptom: Hazards are not closed, and the handover form still has unrectified items. Cause: Deployment status and operation records are not updated by shift, and hazard items and rectification deadlines lack responsible person signature confirmation.
- Symptom: Drill records do not match the plan, and the sign-in count does not add up. Cause: Drill participant counts and sign-in evidence are not handed over together with deployment status, and the next shift verifies against old records.
- Symptom: Access control and school bus check items are missed. Cause: The check item list is not written item by item into operation records, and at handover only connection results are checked, not task records.
How to verify the setup
Connect once to the primary business database, log database, cache, and vector database item by item, and check whether the connection results in the startup logs are consistent with the task records
Check the selected vector database and address against the deployment instructions, and confirm that the log database variable is set separately or left empty per instructions to reuse the primary database
- 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 the three connection variables
MONGODB_URI,PG_URL, andREDIS_URLare consistent with the deployment instructions - Verify once item by item according to the handover form, and see which record is missing