What this category's data looks like
This page is intended for kindergarten operation behavior and quality self-assessment materials, covering three core document types: self-assessment reports, issue lists, and rectification plans. The material sources are kindergarten self-assessment submissions, responsible inspector verification records, and rectification receipts, and the update cadence follows the semester assessment cycle and rectification deadlines. Field characteristics include kindergarten name, assessment indicator, issue description, rectification measure, responsible person, completion date, and signature field. When entering the deployment, operations, and application handover function, the self-assessment report is written as the main business data into the main business database, the issue list and rectification plan are stored synchronously as associated records, and the log database separately records operation traces and connection status. During handover, the three types of materials need to be checked for consistency among version, connection, and task records, ensuring that the kindergarten name, issue count, and rectification date of the same record match across the report, list, and plan, and that signatures and receipts are complete, avoiding handover interruption caused by unsynchronized versions or missing fields.
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 then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Self-assessment report | Fields, dates, and signatures: the kindergarten name, assessment indicator, completion date, and signature field must be consistent with the issue list and rectification plan | Check the report records in the database pointed to by the main business database connection variable MONGODB_URI, compare whether the kindergarten name, issue count, and dates in the report and list are consistent, and check whether the signature field and receipt are complete |
| Issue list and rectification plan | The name, count, and date of the same record do not match between the two materials; versions are not synchronized; signatures or receipts are missing | Check the values of the log database connection variable and the cache connection variable REDIS_URL, view the version numbers and update times of the issue list and rectification plan in the database, and confirm that the issue items, rectification measures, and completion dates in the two materials correspond item by item |
| Vector database connection | Consistent with the vector database actually used; when retrieval reports a vector database error, the address needs to be checked | Check the vector database connection variable PG_URL against the deployment instructions and the selected vector database address, confirm that there is no vector database connection error after the retrieval service starts, and that full-text search uses the retrieval path of the corresponding database |
Three common errors
- Symptom: after startup, the logs continuously report connection timeouts. Cause: the address pointed to by the main business database or log database connection variable is unreachable, or the cache instance has not started, so the service cannot establish a connection.
- Symptom: the name, count, and date of the same issue do not match between the self-assessment report and the rectification plan. Cause: the two materials were not updated synchronously, or they were not associated by the same record identifier during entry, resulting in inconsistent fields.
- Symptom: during handover, the rectification plan is found to be missing signatures or receipts. Cause: the signature confirmation was not completed in the material circulation step, or the receipt was not archived, resulting in inconsistency among version, task records, and the three.
How to verify the setup
Acceptance for this function: 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 confirm that the instances corresponding to MONGODB_URI, REDIS_URL, and PG_URL all return an available status.
Business test: check item by item once according to the handover form, see which record is missing, and focus on checking whether the fields, dates, and signatures of the self-assessment report, issue list, and rectification plan are complete, and whether version, connection, and task records are consistent.
- In the deployment environment, check that the value of this variable is consistent with the database address, check whether the log database connection variable is set, and check the database to which logs are written.
- Use a client to connect once to the cache instance and check the return; check the selected vector database and address against the deployment instructions, and confirm that retrieval has no vector database errors.