What this category's data looks like
This page focuses on three types of materials in the safety grading and classification of university laboratories: the laboratory grading and classification table, the hazard source list, and the safety responsibility statement. The grading and classification table is recorded by laboratory number, room, category, and level, and is usually updated with each round of inspection; the hazard source list lists name, quantity, storage, and date item by item by room and equipment, and its update cadence is synchronized with equipment changes; the safety responsibility statement is signed by level, including responsible person, date, and signature or receipt. When these three types of materials enter the material verification and discrepancy localization function, the grading and classification table serves as the baseline object, the hazard source list serves as the source for quantity and date comparison, and the safety responsibility statement serves as the source for signature and receipt verification; the function only compares the name, quantity, date, and signature of the same object across materials, outputs a discrepancy list, and does not replace the reviewer's judgment.
Configuration and implementation checks
This part is executed by application settings (response limit, etc.), which determine the length of a single answer and the range of context that can be accommodated. The "discrepancy list" is then completed by the model, and entry and authorization are handled by the publishing service and file permissions.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | The name, quantity, and date of the same laboratory are consistent in the two materials | Check the switch and slider position in application settings, confirm that maxResponse matches the answer length required by the page, and compare the room and level fields item by item |
| Hazard source list | The name, quantity, and date of the same hazard source are consistent in the list and the ledger | Ask a question that requires a long answer and look at the ending, confirm that the ending of a longer answer is complete, and check that maxContext can accommodate the field range of the two materials |
| Safety responsibility statement | The date and signature of the same responsible person are consistent in the responsibility statement and the receipt | Compare the usage of two runs, confirm the change in single-run usage after the limit is adjusted, and check whether the signature or receipt is complete |
| Quoted text | The number of quoted items and the quoted content budget are recorded separately | Check that the tokens of quoted text use quoteMaxToken, record the number of array items separately, and do not perform an equality comparison |
Three common errors
- Symptom: the name or quantity of the same record does not match between the grading and classification table and the hazard source list. Cause: the two materials are updated separately, and no field-level comparison is performed.
- Symptom: the date of the same laboratory is inconsistent in the two materials. Cause: the versions are not synchronized, and the old version of the material is still used as the comparison source.
- Symptom: the safety responsibility statement lacks a signature or receipt. Cause: the signing process is not closed-loop, and the signature field is not verified when the material is archived.
How to verify the setup
This function's acceptance: ask a question that requires a long answer and see whether the ending is complete; if it breaks off in the middle of a sentence, check the switch and slider position of the response limit.
Business test: use a real record to find fields inconsistent with the ledger, record the differences in name, quantity, date, and signature, submit them to the reviewer for confirmation, and write them back.
- Check the switch and slider position of the response limit in application settings, and confirm that they match the answer length required by the page.
- Compare the usage of two runs, confirm the change in single-run usage after the limit is adjusted, and check that the tokens of quoted text and the number of array items are recorded separately.