What this category's data looks like
This page addresses journal publishing licenses and annual verification. Materials include journal publishing licenses, annual verification forms, and rectification reports. Fields include name, quantity, date, signature, and receipt. License records cover the entity and scope of permission; annual verification forms record annual matters and conclusions; rectification reports record issues and handling results. Materials enter the knowledge base retrieval node by year or verification batch, each participating as an independent source in citation output. The update cadence advances with the verification cycle and the archiving of rectification receipts; older versions of materials may remain in the same knowledge base. When materials enter this feature, licenses and verification forms are used to compare field names and quantities, while rectification reports are used to check dates and signature receipts. Together, the three support a handover-ready deployment state and operation records.
Configuration and implementation checks
This step is executed by the citation output of the knowledge base retrieval node, which outputs a citation content array, each entry containing an original text snippet and a source identifier, and the length can be 0. The "handover-ready deployment state and operation records" are completed subsequently by AI nodes, code nodes, or manual work.
| Object | Check | Verification action |
|---|---|---|
| Journal publishing license | The name, quantity, date, and signature must match the corresponding fields in the annual verification form; if the signature or receipt is missing, it does not pass | In the citation output, point back to the original license snippets one by one, check the name, quantity, date, and signature fields, and record the number of citations |
| Annual verification form | The name, quantity, and date of the same record must be consistent across both materials, and the versions must be synchronized | Use the same question to hit the license and the verification form separately, compare the fields and dates, and confirm that versions are not mixed |
| Rectification report | The date and signature receipt must correspond to the conclusion of the verification form; if the receipt is missing, mark it as pending supplementation | Open the citation superscript to compare against the original rectification report, check the date, signature, and receipt, and separately record the array length |
| Associated knowledge base and search parameters | The selected collection must use the same vector model, and the search parameter values must be consistent with the knowledge base retrieval section | In the node, check the selected collection and vector model, open the search parameter panel and check each item, and confirm that the citation content is output as an array and that the length can be 0 |
Three common errors
- Symptom: The name and quantity of the same record do not match between the license and the verification form. Cause: The two materials were entered in different batches and were not compared using the same field definitions; the citation snippets each point back to their own original text.
- Symptom: The date in the rectification report is inconsistent with the conclusion date in the verification form. Cause: Versions are not synchronized, older materials remain in the knowledge base, and retrieval hits old snippets without checking the version.
- Symptom: There is no citation superscript in the answer, or there is an answer but the citation array is empty. Cause: An empty citation array does not mean retrieval failed; an empty array is a normal output. If the superscript is missing, first check whether this round hit any materials, then look at trimming.
How to verify the setup
Acceptance for this feature: ask a question with source support, check whether the citation content array and citation superscripts can point back to the original paragraphs, and check the source identifiers in responseData (non-streaming module results returned with detailed output enabled) and quoteList; then ask a question with no matching materials, confirm that the array is empty while the pipeline still runs, that the citation count is the array length, and that quoteMaxToken is the citation content budget, and do not compare the two for equality.
Business test: check each item once according to the handover checklist, see which record is missing, and focus on checking the name, quantity, date, and signature receipt of the license, verification form, and rectification report, and confirm that the version, connection, and task record are consistent.
- In the node, check the selected knowledge base collections and their vector models, open the search parameter panel, and check each value item by item
- Run a trial with a question that has no matching materials, see that the citation content output is empty while the pipeline continues, and separately record the array length