What this category's data looks like
Laboratory hazardous chemical procurement and ledgers: the materials include three documents—procurement applications, usage registrations, and inventory ledgers. The sources are daily laboratory circulation and month-end summaries, with an update cadence of weekly records and monthly verification. Procurement applications contain item name, specification, quantity, application date, and approval signature; usage registrations contain the person taking the item, usage date, quantity, purpose, and receipt; inventory ledgers contain balance quantity, inbound/outbound dates, and custodian signature. When the materials enter knowledge base retrieval and recall, procurement applications, usage registrations, and inventory ledgers are each indexed as independent chunks. Fields and signatures participate in recall as text features within candidate chunks. The three documents are presented side by side in the retrieval results for subsequent nodes or manual comparison of whether names, quantities, dates, and signatures are consistent.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate chunks and similarity scores (after pattern, merge, re-rank, filter, and limit truncation). The progress table and statistical scope description are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Procurement application | Item name, specification, quantity, application date, and approval signature are aligned item by item | In the knowledge base search test, search with synonymous questions, view candidate chunks and the similarity score, and check whether the application date and signature appear in the same chunk |
| Usage registration | Person taking the item, usage date, quantity, purpose, and receipt are aligned item by item | Switch searchMode to semantic, full-text, or hybrid, compare the number of candidates and scores, and check whether the usage date and receipt are complete |
| Inventory ledger | Balance quantity, inbound/outbound dates, and custodian signature are aligned item by item | Enable or disable usingReRank, compare the ranking of the top few candidates, and check whether the balance quantity and inbound/outbound dates are consistent with the application and usage records |
| Statistical scope description | Record counts and statistical counts match, and the scope is written in the header | Use one week of records to verify the totals, check whether candidate chunks cover names, quantities, dates, and signatures, and record the number of candidates after limit truncation |
Three common errors
- Symptom: The name and quantity of the same record do not match between the procurement application and the inventory ledger. Cause: The two documents use different field formats, and the retrieval candidates do not cover the same chunk.
- Symptom: The dates in the usage registration and inventory ledger are misaligned, and versions are not synchronized. Cause: The material update cadences are inconsistent, and the recall results come from old-version chunks.
- Symptom: The approval signature or usage receipt is missing, and statistical verification cannot be closed. Cause: The material circulation step was not backfilled, and there is no signature text in the candidate chunks.
How to verify the setup
Acceptance for this feature: test once each with synonymously rewritten questions, compare candidates and similarity scores, then toggle usingReRank to see the ranking of the top few.
Business test: use one week of records to verify the totals, check whether the scope and exceptions are clearly written, verify the number of candidates and the tokens of the cited text, and record the array count separately.
- In the knowledge base search test, switch
searchModeand compare the number of candidates and scores under the semantic, full-text, and hybrid modes. - Verify the names, quantities, dates, and signatures of the three documents—procurement applications, usage registrations, and inventory ledgers—and record the number of candidates after
limittruncation.