What this category's data looks like
Materials for kindergarten health care and meal management are generated daily: ingredient names and specifications, retention sample times and batches, disinfection periods, and categorized causes of absence. Sources are health room morning checks, cafeteria procurement and retention sampling, and class disinfection and attendance registration. The update cadence is multiple times per day; morning checks and attendance are recorded as they occur, retention samples are recorded per meal, and disinfection is recorded per period. When entering the deployment, operations, and application handover function, these materials exist as objects to be verified in the primary business database, the log database handles operation records, the cache handles streaming recovery mirrors, and the vector database handles vectors for retrieval. The handover form lists ingredient specifications, retention sample batches, disinfection periods, and categorized causes of absence item by item, for the next shift to verify against the records.
Configuration and implementation checks
The connection configuration of the deployment environment (server side) is not a model node capability; it only outputs whether the connection is available (service startup result and connection logs). The handover-ready deployment status and operation records must be handled by the deployment handover and subsequent business processing. The connection address is configured by environment variables; the primary business database, log database, cache, and vector database can point to different instances respectively; if the log database is not configured separately, it reuses the primary database.
| Object | Check | Verification action |
|---|---|---|
| Primary business database connection variable | Points to the primary business database actually in use and is connectable; ingredient names and specifications, retention sample times and batches, disinfection periods, and categorized causes of absence all reside in this database | In the deployment environment, check that the variable value matches the database address, connect once with a client, and view the startup logs |
| Log database connection variable | Configured separately, or left empty per the instructions to reuse the primary database; operation records are written to the log database | Check whether the variable is set, and verify the database to which logs are written against the number of records in the handover form |
| Cache connection variable | The cache instance is connectable, and the streaming recovery mirror can be created | Connect once with a client, and check the connection result in the response and startup logs |
| Vector database connection variable | Matches the vector database actually in use, and retrieval goes through the corresponding database | Check the selected vector database and address against the deployment instructions, and confirm the retrieval connection is available |
Three common errors
- Symptom: the form and retention sample batches do not match, and the corresponding retention sample cannot be found during handover. Cause: retention sample times and batches were not recorded in sync with the form, and the operation records lack the batch field.
- Symptom: the menu and procurement categories are inconsistent, and meal preparation and procurement do not match. Cause: ingredient names and specifications were not entered under the same standard, and the two records are updated separately.
- Symptom: disinfection records lack periods, and the handover form cannot be verified item by item. Check: disinfection periods were not registered by shift. Logs use the primary database when no separate log database is configured; inspect the actual log destination separately.
How to verify the setup
This function's acceptance: 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; use MONGODB_URI, REDIS_URL, and PG_URL respectively to verify the connection addresses and responses of the primary business database, cache, and vector database.
Business test: verify once item by item according to the handover form, see which record is missing, and check whether ingredient names and specifications, retention sample times and batches, disinfection periods, and categorized causes of absence are complete.
- In the deployment environment, check that the connection variable values of the primary business database, log database, cache, and vector database match the instance addresses, and save the startup logs.
- Verify the records of ingredient specifications, retention sample batches, disinfection periods, and categorized causes of absence item by item according to the handover form, mark missing items, and hand them over to the next shift.