What this category's data looks like
This page focuses on journal publication licenses and annual verification, organizing three types of materials: journal publication license, annual verification form, and rectification report. The license records the licensed entity, publication number, validity period, and issue date; the annual verification form records the verification year, publication frequency, publishing unit, and signed receipt; the rectification report records problem items, rectification measures, completion date, and approval signature. When the three enter the knowledge base retrieval node, their roles differ: the license and verification form are the primary basis, used to answer the scope of licensing and the status of annual verification; the rectification report is the supplementary basis, used to answer rectification progress and remaining issues. The material update rhythm is synchronized with the annual verification cycle and rectification batches, and the field characteristics are concentrated in names, quantities, dates, signatures, and receipts. The same record may show inconsistencies in name, publication frequency quantity, and dates between the license and the verification form; between the rectification report and the verification form, there may be unsynchronized versions, missing signatures, or missing receipts. These differences need to be compared item by item against the original text, and conclusions cannot be drawn based only on cited fragments.
Configuration and implementation checks
This part is executed by the citation output of the knowledge base retrieval node, which outputs an array of cited content, each item containing the original text fragment and source identifier, and the length can be 0. Even if no content is retrieved, the output chain will still run through. The basis items that can be traced back to the original text are then completed by subsequent AI nodes, code nodes, or manual work.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Fields: licensed entity, publication number, validity period, issue date; whether dates and signatures are complete | Open the original license, check the fields and issue date item by item, confirm that signatures and receipts exist, and record the original text passages that can be traced back |
| Annual verification form | Fields: verification year, publication frequency, publishing unit, signed receipt; whether the name, quantity, and dates of the same record match the license | Compare the license and the verification form, check the name, publication frequency quantity, and dates item by item, mark inconsistencies, and trace back to both original texts |
| Rectification report | Fields: problem items, rectification measures, completion date, approval signature; whether the version is current and whether signatures or receipts are missing | Check the rectification report version and approval signature, confirm consistency with the verification form record, inspect for missing signatures or receipts, and trace back to the original text |
| Cited content output | The number of returned items matches the hit materials, and being empty is also normal; cited fragments correspond to the original text passages | Run a test with a question that has no matching materials, and see that the output is empty while the chain continues; open the citation marker to compare against the source document |
Three common errors
- Symptom: the name, publication frequency quantity, and dates of the same record do not match between the license and the verification form. Cause: the two materials are filled in separately without cross-checking, and only a single fragment is taken when citing.
- Symptom: the rectification report version is not synchronized, and the verification form still cites the old version item. Cause: the material update rhythms differ, the knowledge base does not replace the old version in time, and the citation hits the old fragment.
- Symptom: the verification form or rectification report is missing a signature or receipt, but the answer still gives a basis item. Cause: field verification does not cover signatures and receipts, and the citation array only reflects hits, not material completeness.
How to verify the setup
This feature acceptance: ask a question with original text basis, and check whether the citation array and citation marker can trace back to the original text; then ask a question with no matching materials, and confirm that the array is empty while the chain runs through. The number of citations is the array length, and quoteMaxToken is the citation content budget; the two are not compared for equality; if a citation upper limit is involved, check the tokens of the cited text, and record the array item count separately.
Business test: ask a cross-material basis question, see whether the answer gives a traceable source, and check the cited fragments and source identifiers in responseData (non-streaming module results returned with detailed output enabled) and quoteList.
- In the node, check the selected knowledge base collections and their vector models, and confirm that the selected knowledge bases use the same vector model.
- Open the search parameter panel and check the values item by item, keeping them consistent with the values set in the knowledge base retrieval section.