What this category's data looks like
When kindergarten operation behavior and quality self-assessment enters the progress record and statistical verification stage, the materials include three categories: self-assessment reports, issue lists, and rectification plans. The self-assessment report carries the overall conclusions and indicator scores, the issue list itemizes matters to be improved one by one, and the rectification plan corresponds to responsible persons, completion dates, and signed receipts. The three categories of materials are aggregated from different positions and updated weekly or monthly, with fields concentrated in record name, quantity, date, signature, and version number. After entering this function, the self-assessment report serves as the source of the statistical scope, the issue list serves as the source of the number of records, and the rectification plan serves as the source of exceptions and completion status; the progress table merges the three under the same scope, and the statistical scope description is written into the table header, indicating the number of records, the statistical count, exception items, and version.
Configuration and implementation checks
This step 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). The "progress table and statistical scope description" is then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Self-assessment report | Name, quantity, date, and signature must be consistent with the issue list, and the version number must be synchronized | In the deployment environment, check the main business database pointed to by MONGODB_URI, and compare the number of records and dates of same-named records between the report and the list |
| Issue list | The number of records must correspond to the rectification items in the rectification plan; missing signatures or receipts are marked separately | Connect once to REDIS_URL with a client and check the cache return; then check the signatures and receipts of the rectification plan item by item against the list |
| Rectification plan | Completion dates must match the statistical count in the header of the statistical scope description, and exceptions must be clearly stated | Check against the deployment instructions that PG_URL is consistent with the actual vector database address, then check the plan totals against the scope weekly |
| Statistical scope description | The header states the number of records, statistical count, exception items, and version, consistent with the three materials | Check the weekly record totals item by item according to the header, and confirm consistency in the three places: name, quantity, and date |
Three common errors
- Phenomenon: the name and quantity of the same issue do not match between two materials. Cause: each position fills in separately, without merging under the same scope, and versions are not synchronized.
- Phenomenon: the rectification plan lacks signatures or receipts. Cause: completion status is recorded only in the progress table, receipts are not archived, and it cannot be confirmed during verification.
- Phenomenon: after startup, the logs continuously report connection timeouts, and business data and logs are mixed in the same place. Check: the connection variables are inconsistent with the actual database addresses. Logs use the primary database when no separate log database is configured; inspect the actual log destination separately.
How to verify the setup
Acceptance of this function: connect once item by item to the main business database, log database, cache, and vector database, and check the connection results in the startup logs.
Business test: use one week of records to check the totals, and see whether the scope and exceptions are clearly stated.
- In the deployment environment, check that the value of the main business database connection variable is consistent with the database address, and check whether the log database variable is set or left empty to reuse the main database.
- Connect once to the cache with a client and check the return; check the selected vector database and address against the deployment instructions.