What this category's data looks like
Laboratory hazardous chemicals procurement and ledger materials come from three types of records: procurement applications, usage registrations, and inventory ledgers, and their update cadence changes with each procurement and usage action. Field characteristics are concentrated in name, quantity, date, and signature. If the same hazardous chemical has inconsistent name spellings, different quantity units, or dates spanning months across different materials, version differences will arise. When the materials enter the knowledge base retrieval and recall function, the procurement application form serves as the demand source fragment, the usage registration serves as the consumption basis fragment, and the inventory ledger serves as the balance verification fragment. Each assumes the role of candidate content, for subsequent nodes or manual comparison of whether the current version is unique, whether the old version is traceable, and whether references are synchronized.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate fragments and similarity scores (after mode, merge, rerank, filter, and upper-limit truncation). The version ledger and change records are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemicals procurement application | Whether the name, quantity, date, and signature are consistent with the usage registration and inventory ledger | In the knowledge base search test, switch searchMode, compare the semantic, full-text, and hybrid candidate routes, and see whether the name, quantity, date, and signature of the same procurement record match |
| Usage registration | Whether the usage quantity, usage date, and signature receipt are synchronized with the inventory ledger | Retrieve usage records with synonymous questions, see whether the candidates and scores are stable, and check whether the key fragments of signature and receipt are still retained after similarity filtering |
| Inventory ledger | Whether the balance quantity, date, and signature form a unique current version with the procurement application and usage registration | Compare the top few rankings before and after enabling usingReRank, confirm that ledger fragments rank among the top relevant candidates, and separately record the number of items in the returned array |
| Version ledger and change records | The current version is unique, the old version is traceable, and references are synchronized | After changing one piece of content, retrieve again and see whether the version number and references are updated synchronously; verify the reference text tokens and limit upper-limit truncation, and separately record the number of items in the array |
Three common errors
- Symptom: The name and quantity of the same hazardous chemical do not match between the procurement application and the inventory ledger. Cause: The two materials are maintained separately, and fields and date conventions are not unified according to the version ledger.
- Symptom: The usage registration has been updated, but the procurement application still references the old version. Cause: The version is not synchronized, the retrieval candidates still hit the old fragment, and no uniqueness check of the current version has been performed.
- Symptom: The usage record lacks a signature or receipt, and the inventory ledger cannot be closed. Cause: The signature field was not retained when the material entered the knowledge base, and key content is missing after candidate fragment truncation.
How to verify the setup
This function's acceptance: test once each with synonym-rewritten questions, compare candidates and similarity scores, then toggle rerank on and off to inspect the top few rankings; switch searchMode to check differences among semantic, full-text, and hybrid candidates, and separately record limit and the number of items in the returned array.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the knowledge base search test, switch
searchMode, retrieve the same hazardous chemical name using different expressions, record the number of candidates and scores, and check whether the current version fragment is unique. - Compare the top few rankings before and after enabling
usingReRank, check whether the reference text aftersimilarityfiltering retains the name, quantity, date, and signature; verify the reference upper limit in tokens, and separately record the number of items in the array.