What this category's data looks like
In the progress records and statistical verification of kindergarten play activity organization, the materials come from observation records, area plans, material placement lists, activity objectives, and reflections converted into next week's plan. Observation records correspond to area plans, material placement quantities and objective achievement corroborate each other, and reflections converted into next week's plan form a closed loop. The update rhythm advances weekly, summarizing the record count and statistical count once per week. Field characteristics include activity date, area, material name and quantity, observation points, objective achievement markers, and exception notes. When materials enter the database and operations functions, observation records and area plans are the verification baseline, material placement quantities are the counting objects of the statistical scope, activity objective achievement is the basis for judgment, and reflections converted into next week's plan are the starting point of the next round's progress table. The progress table and statistical scope description are completed by deployment handover and subsequent business processing, and are used for weekly or monthly reports.
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 completed by deployment handover and subsequent business processing. The connection address is configured by environment variables: 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 will reuse the main database.
| Object | Check | Verification action |
|---|---|---|
| Observation records and area plans | The record count and statistical count match, observation records correspond to area plans, and the scope is written in the table header | Use one week of records to verify the total, check the number of observation records item by item against the area plan, and check whether the table header states the statistical scope and exceptions |
| Material placement quantities | Material placement quantities are consistent with the statistical scope, and when materials are insufficient, exceptions are written in the table header | Verify the quantities in the material placement list against the statistical count, and check whether material insufficiency is written into the table header as an exception |
| Activity objective achievement | Objectives match observations, and activity objective achievement markers correspond to observation records | Verify activity objective achievement markers against observation records item by item, and check whether mismatches between objectives and observations are explained |
| Reflections converted into next week's plan | When the plan is not updated, note it in the table header, and reflections converted into next week's plan connect with this week's records | Verify whether reflections converted into next week's plan have been updated, and check whether failure to update the plan is written into the table header as an exception |
Three common errors
- Phenomenon: In the weekly report, the record count and statistical count do not match. Cause: Material insufficiency caused some activities not to be recorded, and material insufficiency was not written into the table header as an exception during statistics.
- Phenomenon: Activity objective achievement markers are inconsistent with observation records. Cause: Objectives do not match observations, and verification only looked at totals without checking item by item against area plans.
- Phenomenon: Next week's plan is disconnected from this week's records. Cause: The plan was not updated, reflections converted into next week's plan did not advance weekly, and the progress table was not refreshed in time.
How to verify the setup
Acceptance of this function: connect once to the main business database, log database, cache, and vector database item by item, and verify the connection results in the startup logs; in the deployment environment, verify that the value of MONGODB_URI is consistent with the main business database address, check whether the log database variable is set or left empty according to the instructions to reuse the main database, connect once to the cache with a client and verify the REDIS_URL return, and verify against the deployment instructions that the selected vector database is consistent with the PG_URL address.
Business testing: use one week of records to verify the total, and see whether the scope and exceptions are clearly written; the number of references is the array length, and quoteMaxToken is the reference content budget. The two are not compared for equality. If a reference upper limit is involved, verify the tokens of the reference text, and record the array count separately.
- In the deployment environment, verify that the value of the main business database connection variable is consistent with the database address, check whether the log database variable is set or left empty according to the instructions to reuse the main database, connect once to the cache with a client and verify the return, and verify against the deployment instructions that the selected vector database is consistent with the address.
- Use one week of observation records to verify the total, check item by item against the area plan and material placement list, check whether the table header states the statistical scope and exceptions, and confirm that reflections converted into next week's plan have been updated.