What this category's data looks like
This page focuses on the business basis query for journal publication licenses and annual verification. The materials include journal publication licenses, annual verification forms, and rectification reports. These materials come from this park's material library and are updated annually. The fields cover license number, publication period, sponsoring organization, verification year, rectification items, date, and signature. When entering this function, the license provides the subject qualification and publication scope, the annual verification form provides the annual compliance status and verification conclusion, and the rectification report provides the issue items and closed-loop records. Together, the three form a pool of basis entries, which is used for retrieval and citation trimming to extract supporting materials, to reply to parents or to write into proposals.
Configuration and implementation checks
This step is executed by the indexing service and vector database, and outputs vectors and index status (whether recall is possible and whether data in the same group is merged). "Basis entries that can be traced back to the original text" are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only extract supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | The fields include license number, publication period, sponsoring organization, validity period, and signature; the date is consistent with the annual verification form | Check the index model in the knowledge base settings, open the data row and verify whether the index field contains multiple vector identifiers |
| Annual verification form | The fields include verification year, verification conclusion, date, and signature; the name and quantity of the same record match the license | View the data scope covered by the rebuild task, and confirm that after changing the model, it is triggered only for data whose indexing has been completed |
| Rectification report | The fields include rectification items, rectification date, receipt, and signature; the version is current and corresponds to the verification form conclusion | After retrieval, verify whether data in the same group is merged; for status values, only indexed and rebuild task records are recognized |
| Data row index field | Multiple vector identifiers for one data row are all present and consistent with the vector model actually used by the knowledge base | Open a data row and check the index field, and confirm that defaultToken and maxToken do not participate in determining index status |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the license and the annual verification form. Inspect the following: The versions of the two materials were not synchronized, and the same field definitions were not checked during entry.
- Symptom: Duplicate entries appear in retrieval results. Inspect the following: Multiple vector identifiers for data in the same group were not merged, or the coverage scope of the rebuild task is inconsistent with the data whose indexing has been completed.
- Symptom: The rectification report lacks a signature or receipt, and recall quality drops after changing the model. Inspect the following: The materials were not closed-loop, and the rebuild is triggered only for data whose indexing has been completed, missing some data rows.
How to verify the setup
This function's acceptance check: sample one data row and inspect the index field to confirm that multiple vector identifiers are all present; then retrieve once to see whether the same group is merged. For status values, only indexed and rebuild task records are recognized. The number of citations is recorded by array length, and the citation content budget is based on quoteMaxToken; the two are not compared for equality.
Business test: ask a cross-material basis question, for example whether a certain year's verification conclusion corresponds to the rectification receipt, and see whether the answer provides a traceable source.
- Check the index model in the knowledge base settings, and confirm it is consistent with the vector model actually used by the knowledge base
- View the data scope covered by the rebuild task, and confirm that after changing the model, it is triggered only for data whose indexing has been completed