What this category's data looks like
This page focuses on exception tracing and manual review in journal publication licenses and annual verification. Category materials include journal publication licenses, annual verification forms, and rectification reports. These materials are usually updated by year or by rectification batch, and their fields involve journal name, publication number, publication date, signature, and receipt. When entering the knowledge base retrieval function, the license provides subject qualification and licensed scope, the annual verification form carries annual data and verification conclusions, and the rectification report records issues and handling results. The three serve as cross-references for comparing whether the name, quantity, and date of the same record are consistent, whether versions are synchronized, and whether signatures or receipts are complete. The retrieval service recalls candidate snippets from these materials for subsequent nodes or manual review to form an exception list and review conclusions.
Configuration and implementation checks
This step is performed by the knowledge base retrieval service (retrieval node and search test), outputting candidate snippets and similarity scores (after mode, merge, rerank, filter, and limit truncation). The exception list and review conclusions are then completed by subsequent nodes or manual review.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Whether fields, dates, and signatures are consistent with the annual verification form | In the search test, switch searchMode and check whether the publication number and sponsor unit in the license correspond to the records in the verification form |
| Annual verification form | Whether the name, quantity, and date of the same record match the rectification report | Use synonymous questions to retrieve the annual verification form and rectification report, compare candidate snippets and similarity scores, and check whether dates and signatures are complete |
| Rectification report | Whether versions are synchronized and receipts are complete | Compare the order of the top few candidates before and after enabling usingReRank, and confirm whether the rectification report version and receipt fields are recalled |
| Knowledge base retrieval service | Whether candidate snippets and similarity scores have undergone merge, rerank, filter, and limit truncation | Observe the number of returned candidates and the limit setting, and check that cited text tokens and array counts are recorded separately |
Three common errors
- Symptom: The same journal name is written differently in the license and the annual verification form. Cause: No unified standard was applied during entry or versions are not synchronized, causing retrieval candidates to point to different records.
- Symptom: Dates and quantities in the annual verification form and rectification report do not match. Cause: The two materials are updated at different paces, old versions were not replaced, and both are recalled during retrieval.
- Symptom: The rectification report lacks a signature or receipt, but retrieval still returns candidates. Cause: Material scanning or entry is incomplete, and similarity filtering does not cover signature fields.
How to verify the setup
Acceptance for this function: test once each with synonym-rewritten questions, compare candidate snippets and similarity scores, then toggle usingReRank on and off to observe changes in the order of the top few results, and confirm that searchMode and limit behave as expected.
Business test: create an exception record, see whether the source material can be traced, and check the name, quantity, date, and signature in the license, annual verification form, and rectification report.
- In the knowledge base search test, switch
searchModeand retrieve the same exception record using semantic, full-text, and hybrid modes respectively, recording the number of candidates and scores. - Enable and disable
usingReRank, compare the order of the top few candidates, check cited text tokens and array counts, and confirm that key snippets have not been truncated or lost.