What this category's data looks like
Laboratory safety grading and classification materials at universities mainly consist of laboratory grading and classification tables, hazard source lists, and safety responsibility statements. They are sourced from each department and laboratory safety officer reporting by semester or special project, with an update cadence of weekly or monthly summary. The grading and classification table records laboratory name, room number, category level, and responsible person; the hazard source list records hazard source name, quantity, storage location, and control measures; the safety responsibility statement records the responsible person's signature and receipt date. When entering the progress records and statistical verification function, the grading and classification table provides the laboratory roster and grading results, the hazard source list provides quantity and location details, and the safety responsibility statement provides signature and receipt status. Together, the three support the compilation of the progress table and the statistical scope description.
Configuration and implementation checks
This step is performed 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). The "progress table and statistical scope description" are then completed by the deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | The name, room number, category level, and responsible person date fields must be consistent with the hazard source list | Check the laboratory name and room number in the two tables item by item, and compare the grading date with the responsible person's signature |
| Hazard source list | The hazard source name, quantity, storage location, and control measures must correspond to the grading and classification table | Merge by laboratory name, and check the quantity totals and storage location descriptions |
| Safety responsibility statement | The responsible person's signature and receipt date must be consistent with the responsible person in the grading and classification table | Check the signature field and receipt date, and mark records missing a signature or receipt |
| Deployment environment connection configuration | The connection addresses of the main business database, log database, cache, and vector database must be consistent with the actual instances | In the deployment environment, check the values of MONGODB_URI, REDIS_URL, and PG_URL and whether they match the database addresses |
Three common errors
- Symptom: The name or room number of the same laboratory does not match across the two materials. Cause: The reporting scope is not unified, and versions are not synchronized.
- Symptom: The hazard source quantity does not match between the list and the statistical table. Cause: The update cadence differs, and one side has not backfilled the changes.
- Symptom: The responsibility statement is missing a signature or receipt, but it is still counted as complete in the statistics. Cause: The signature and receipt were not marked as exceptions during verification.
How to verify the setup
This function's acceptance: connect once to the main business database, log database, cache, and vector database item by item, and check the connection results in the startup logs; in the deployment environment, check that the values of MONGODB_URI, REDIS_URL, and PG_URL match the database addresses, check whether the variables are set, and check the database to which logs are written.
Business test: use one week of records to check the totals, and see whether the scope and exceptions are clearly written.
- Check the laboratory name, room number, quantity, and dates in the grading and classification table and the hazard source list, and mark inconsistent items.
- Check the signature and receipt date in the safety responsibility statement, and list records missing a signature or receipt in the exception description.