What this category's data looks like
In the journal publishing license and annual verification scenario, materials usually include three types: journal publishing licenses, annual verification forms, and rectification reports. The license states the entity name, publication number, publishing scope, and validity period; the annual verification form records data such as publication frequency, print run, personnel, and assets by year; the rectification report records issue items, rectification measures, and completion dates. The three types of materials corroborate each other on fields, dates, and signatures, and the names, quantities, and dates must be consistent. When materials enter the knowledge base, the license and verification form serve as the basis for the current version, and the rectification report serves as the source of changes, with the update rhythm advancing according to annual verification and rectification milestones. Vector models and indexes serve as the retrieval foundation for version and change maintenance, enabling multiple materials for the same record to be merged by index fields, so that old versions can be traced and citations can be synchronized.
Configuration and implementation checks
This part is executed by the index service and vector database, outputting vectors and index status (whether recall is possible and whether data in the same group is merged). The "version ledger and change records" are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Journal publishing license | The entity name, publication number, publishing scope, and validity period must be consistent with the annual verification form, and signatures and receipts must be complete | Open the data row to check the index fields, confirm that multiple vector identifiers are present, and run a retrieval once to see whether the same group is merged |
| Annual verification form | The publication frequency, print run, personnel, assets, and other quantities and dates must match the license and rectification report | Check that the index model is consistent with the vector model actually used by the knowledge base, and inspect the data scope covered by the rebuild task |
| Rectification report | The issue items, rectification measures, and completion dates must be synchronized with the verification form records; missing signatures or receipts are regarded as inconsistent | Sample one data row to inspect the index fields, then run a retrieval once to see whether the same group is merged; for status values, only indexed and rebuild task records are recognized |
| Data row index fields | Multiple vector identifiers for one piece of data are all present, and data in the same group is merged by taking the highest score | Check limit, and the tokens of the cited text; record the array length separately |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: the names, quantities, and dates of the same record in two materials do not match, and the vector identifiers are not merged into the same group of data.
- Symptom: recall quality drops after changing models. Inspect the following: rebuild is triggered only for data that has already been indexed, and versions are not synchronized, so the old version can still be recalled while the new version is not covered.
- Symptom: a data row has content but cannot be retrieved. Inspect the following: the index fields are missing multiple vector identifiers, or materials missing signatures and receipts have not entered the index, so the original data cannot be merged by identifier.
How to verify the setup
Acceptance for this feature: sample one data row to inspect the index fields, then run a retrieval once to see whether the same group is merged; for status values, only indexed and rebuild task records are recognized, and check defaultToken and maxToken.
Business test: change one piece of content and see whether the version number and citations are updated synchronously; the number of citations is the array length, and quoteMaxToken is the citation content budget, so the two are not compared for equality.
- In the knowledge base settings, check that the index model is consistent with the vector model actually used by the knowledge base, and inspect the data scope covered by the rebuild task.
- Open a data row to check the index fields, confirm that multiple vector identifiers are present, then run a retrieval once to see whether data in the same group is merged by taking the highest score.