What this category's data looks like
This category's data involves three types of materials: the laboratory grading and classification table, the hazard source list, and the safety responsibility statement. The grading and classification table records the laboratory name, room number, hazard level, and hazard source category, and is updated by academic year or assessment cycle; the hazard source list records the hazard source name, quantity, storage location, responsible person, and update date; the safety responsibility statement contains responsibility clauses, a signature field, and a receipt date. The fields, dates, and signatures of the three types of materials must be consistent. When the materials enter this feature, the grading and classification table and the hazard source list serve as the text index sources, and the responsibility statement serves as the basis for signature and receipt verification. The update rhythm is revision every academic year or assessment cycle, and after revision the version number and references must be synchronized. If the name, quantity, or date of the same record in the grading and classification table and the hazard source list are inconsistent, or if the responsibility statement lacks a signature and receipt, the version ledger cannot be unique.
Configuration and implementation checks
This part is executed by the index service and the vector database, outputting vectors and index status (whether recall is possible, whether data in the same group is merged). The "version ledger and change records" are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and reference trimming take only supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | The name, room number, hazard level, and hazard source category align item by item with the hazard source list, and the date and version number are consistent | Open the data row to check the index fields, confirm that multiple vector identifiers for one piece of data are all present, and after retrieval check whether the same group is merged |
| Hazard source list | The hazard source name, quantity, storage location, responsible person, and update date are consistent with the grading and classification table, and the signature and receipt are complete | Check the indexed status of the data row, view the data range covered by the rebuild task record, and confirm that it has been rebuilt after changing the model |
| Safety responsibility statement | The responsibility clauses, signature field, and receipt date are synchronized with the version numbers of the grading and classification table and the hazard source list | When retrieving reference text, check limit, record the array count separately, and do not include the reference count in the comparison |
| Index model | It is consistent with the vector model actually used by the knowledge base, and after changing the model the rebuild task is triggered only for data that has already completed indexing | Check the index model in the knowledge base settings, view the rebuild task record, and confirm that the data row status is indexed |
Three common errors
- Symptom: The name, quantity, or date of the same laboratory in the grading and classification table and the hazard source list do not match. Inspect the following: The two materials are maintained separately and are not updated synchronously under the same version number.
- Symptom: The responsibility statement lacks a signature or receipt, and the version ledger cannot be unique. Inspect the following: Signatures and receipts are not included in the version records, and old versions of the responsibility statement are not archived.
- Symptom: After changing the model, recall quality decreases, and data rows have content but cannot be retrieved. Inspect the following: The rebuild task is triggered only for data that has already completed indexing and does not cover all data rows.
How to verify the setup
This feature's acceptance check: take one data row and look at the index fields, confirm that multiple vector identifiers for one piece of data are all present, then retrieve once to see whether the same group is merged, take the highest score, and the status is indexed.
Business test: change one piece of content, see whether the version number and references are updated synchronously, check limit, record the array count separately, and do not include the reference count in the comparison.
- Check the index model in the knowledge base settings, confirm that it is consistent with the vector model actually used by the knowledge base, and view the data range covered by the rebuild task record.
- Open a data row to check the index fields, confirm that multiple vector identifiers are all present, and after retrieval check whether data in the same group is merged, with the status being indexed.