What this category's data looks like
In the course of data versioning and change maintenance, peer review organizations handle materials including review invitations, expert review comments, and author revision notes. These materials come from the editorial office and the review process, and their update cadence advances with review rounds. A review invitation contains the manuscript title, the date sent for review, expert information, and a receipt signature; expert review comments contain comment items, dates, and signatures; author revision notes contain revision items, the corresponding comments, and the submission date. When the materials enter the vector model and indexing function, each becomes an independent data row, and the indexing service generates vectors and records index fields to support subsequent retrieval and citation trimming.
Configuration and implementation checks
This step is executed by the indexing service and the vector store, 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).
| Object | Check | Verification action |
|---|---|---|
| Index model | Consistent with the vector model actually used by the knowledge base; after switching models, rebuild is triggered only for data that has already been indexed | Check the index model in the knowledge base settings; inspect the data scope covered by the rebuild task |
| Review invitation | The manuscript title, date sent for review, expert information, and receipt signature are consistent across the three materials; if the signature or receipt is missing, it is considered not closed-loop | Compare item by item the names, quantities, dates, and signatures in the review invitation against those in the expert review comments and author revision notes |
| Expert review comments | The comment items, dates, and signatures match the review invitation and author revision notes; if the version is not synchronized, mark it as pending update | Check whether the names, quantities, and dates of the same record are consistent across the two materials; check whether the version number and citations are synchronized |
| Author revision notes | Revision items correspond one-to-one with the corresponding comments, and the submission date and receipt are complete; the old version is traceable and the current version is unique | Open a data row and check the index fields; use limit to check the citation text budget, and record the array item count separately |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the review invitation and the expert review comments. Inspect the following: The two materials were entered separately and were not merged under the same version number.
- Symptom: The author revision notes have been updated, but citations still point to the old version's content. Inspect the following: The version was not synchronized, and the index fields were not triggered to rebuild when the source data changed.
- Symptom: A review invitation is still indexed even though it lacks a signature or receipt. Inspect the following: The material closed-loop check is missing, and the status was not marked as pending supplementation.
How to verify the setup
Acceptance for this feature: sample a data row and look at the index fields to confirm that multiple vector identifiers for one data row are all present; then run a retrieval to see whether data in the same group is merged and whether recall is possible; for status values, only recognize indexed and rebuild task records.
Business test: change one piece of content and see whether the version number and citations are updated in sync; use limit to check the citation text tokens, and record the array item count separately.
- Check the index model in the knowledge base settings, and inspect the data scope covered by the rebuild task, to confirm that after switching models, rebuild is triggered only for data that has already been indexed.
- Open a data row and check the index fields to confirm that multiple vector identifiers are all present; after retrieval, check whether data in the same group is merged and whether recall is possible; for status values, only recognize indexed and rebuild task records.