What this category's data looks like
This page addresses university laboratory safety grading and classification materials, covering three types: laboratory grading and classification tables, hazard source lists, and safety responsibility statements. The grading and classification table contains the laboratory name, room number, hazard level, grading basis, and date; the hazard source list contains the name, quantity, storage location, risk category, and update date; the safety responsibility statement contains the responsible person, signature, receipt, and effective date. The materials come from the Laboratory Management Office and submissions from various departments, and are updated by semester or special inspection, with dates and signatures as the key fields. After entering the deployment, operations, and application handover function, the grading and classification table and the hazard source list are business data, and the responsibility statement is a signature receipt voucher; together, the three constitute a handover-ready deployment state and operation records.
Configuration and implementation checks
This step 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). "A handover-ready deployment state and operation records" are then completed by the deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | Whether the name, quantity, date, and signature are consistent with the hazard source list | Check the laboratory name, room number, hazard level, and update date item by item against the two materials; if a signature or receipt is missing, record it |
| Hazard source list | Whether the version is synchronized, whether the dates match, and whether the quantities are consistent | Check the list version number and the grading and classification table date against the handover form; if the names and quantities do not match, mark them |
| Safety responsibility statement | Whether the signature and receipt are complete, and whether the effective date covers the current period | Inspect the signature field and receipt one by one; if any item is missing, return it for supplementary signing |
| Deployment connection configuration | Whether the main business database, log database, cache, and vector database are connectable | Use a client to connect to MONGODB_URI, PG_URL, and REDIS_URL respectively, and check the connection results in the startup logs |
Three common errors
- Symptom: The name, quantity, and date of the same laboratory do not match between the grading and classification table and the hazard source list. Cause: The two materials were submitted separately by different departments, and no cross-check was performed.
- Symptom: The version of the hazard source list is not synchronized, and the old version is still in use. Cause: After the update, the version and date were not checked item by item against the handover form, and the receipt is missing.
- Symptom: The safety responsibility statement lacks a signature or receipt. Cause: During handover, only whether the materials were complete was checked, and the signature field and effective date were not inspected one by one.
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, check the connection results in the startup logs, and confirm that the instances corresponding to MONGODB_URI, PG_URL, and REDIS_URL are available.
Business test: check once item by item against the handover form, and see which item is missing from the records.
- In the deployment environment, check that the value of this variable is consistent with the database address, check whether the variable is set, and check the database to which the logs are written.
- Use a client to connect to the cache once, check the return, and check the selected vector database and address against the deployment instructions.