What this category's data looks like
When materials for journal three-review-three-proof and editorial quality enter the knowledge base, the three-review form, proofs, and proofreading records each play different roles: the three-review form records the fields, dates, and signatures of initial review, re-review, and final review; the proofs carry traces of layout and text changes; the proofreading records log the time, personnel, and receipt for each proofreading. The materials mostly come from internal circulation documents of the editorial office and pre-press archived documents. The update rhythm advances with each round of review and proofreading for each issue's manuscripts, and the field characteristics are concentrated in names, quantities, dates, signatures, and receipts. After these materials enter the vector model and indexing stage, they serve only as raw data to be indexed. The indexing service and vector database are responsible for converting text, image descriptions, etc. into vectors and building a recallable structure, and are not responsible for generating version ledgers and change records.
Configuration and implementation checks
This stage is executed by the indexing service and vector database, outputting vectors and index status (whether recall is possible, 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). Vectors are stored in the vector database, and raw data is stored in data tables in the business database, with index fields recording the corresponding multiple vector identifiers; retrieval first recalls vectors, then merges back to the raw data by identifier, and for the same group of data takes the highest score.
| Object | Check | Verification action |
|---|---|---|
| Index model | Consistent with the vector model actually used by the knowledge base; after changing the model, only trigger rebuild for data that has already been indexed | Check the index model in the knowledge base settings, and view the data range covered by the rebuild task records |
| Index field of the data row | Multiple vector identifiers for one piece of data are all present, and the status value is indexed | Open a data row and check the index field, confirming that multiple vector identifiers are complete and the status is indexed |
| Three-review form | Fields, dates, and signatures are complete, and the name, quantity, and date of the same record match among the three-review form, proofs, and proofreading records | Compare item by item the name, quantity, date, and signature among the three-review form, proofs, and proofreading records; register those missing signatures or receipts as pending supplementation |
| Proofs and proofreading records | Proof changes are consistent with proofreading record receipts, and entries whose versions are not synchronized can be traced to the old version | Check the proof change locations against the proofreading record receipts, confirming that the current version is unique, the old version is traceable, and citations are synchronized |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: the name, quantity, and date of the same record do not match between the three-review form and the proofreading records, so it is split into multiple groups of raw data and indexed separately.
- Symptom: recall quality drops after changing the model. Inspect the following: the rebuild task records only cover data that has already been indexed; data rows that fail to be rebuilt do not participate in recall, so indexing must be completed first, and versions are not synchronized.
- Symptom: a data row has content but cannot be retrieved. Inspect the following: the index field is missing or the status has not reached indexed, and materials missing signatures or receipts have not entered the recallable set.
How to verify the setup
Acceptance for this feature: take one data row and look at the index field, confirming that multiple vector identifiers are all present and the status is indexed; then perform a retrieval and see whether data in the same group is merged and whether the vector score takes the highest score.
Business test: change one piece of content and see whether the version number and citations are updated synchronously; when the citation upper limit is involved, check the tokens of the citation text, record the number of array entries separately, quoteMaxToken is the citation content budget, and limit are only for field verification.
- In the knowledge base settings, check whether the index model is consistent with the vector model actually used by the knowledge base, and view the data range covered by the rebuild task records.
- Open a data row and check the index field, confirming that multiple vector identifiers are complete and the status is indexed, then perform a retrieval to see whether data in the same group is merged.