What this category's data looks like
For peer review organizations, data versions and change maintenance revolve around three types of materials: review invitations, expert review comments, and author revision notes. A review invitation contains the manuscript number, invitation date, expert name, and reply status; expert review comments contain review dimensions, conclusions, and signatures; author revision notes contain revision items, corresponding page numbers, and receipts. The material sources are editorial office correspondence, review system exports, and author-submitted attachments. The update cadence follows the manuscript circulation stage. For the same record, the field names, counts, and dates must be consistent across the invitation, comments, and revision notes. When these three types of materials enter knowledge base retrieval and recall, they respectively serve the roles of invitation basis, review conclusion, and revision comparison. Retrieval nodes recall candidate snippets accordingly, for subsequent nodes or humans to generate the version ledger and change records.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate snippets and similarity scores (after mode, merge, re-rank, filter, and limit trimming). The version ledger and change records are then completed by subsequent nodes or humans.
| Object | Check | Verification action |
|---|---|---|
| Review invitation | The manuscript number, invitation date, expert name, and reply status must correspond item by item between the invitation and the comments materials | In the search test, switch searchMode, check whether the number and date within the candidate snippets are consistent, and record the number of candidates and the score |
| Expert review comments | The review dimensions, conclusions, and signatures must be complete, and the number of items in the comments and revision notes must be consistent | Compare the order of the top few items before and after enabling and disabling usingReRank, and check whether the signature and receipt fields are recalled together with the candidates |
| Author revision notes | The revision items, corresponding page numbers, and receipts must correspond item by item with the comments, and older versions must be traceable | Adjust similarity and limit, observe changes in the number of candidates and the score, and check and record the cited text tokens and the array item count separately |
| Version ledger and change records | The current version is unique, older versions are traceable, and citations are synchronized | After changing one piece of content, rerun the retrieval, see whether the version number and citations are updated synchronously, and check whether the candidate snippets still point to the current version |
Three common errors
- Symptom: The name, count, and date of the same record do not match between the invitation and comments materials. Cause: The materials are maintained separately and are not aligned to the same field definitions.
- Symptom: The revision notes have been updated, but retrieval still recalls snippets from the old version. Cause: The version is not synchronized, and the old version is not marked as traceable.
- Symptom: The comments material lacks a signature or receipt, but the ledger still records it as complete. Cause: The signature field is not included in the scope of checks for recalled candidates.
How to verify the setup
Feature acceptance: Test once each with synonymously rewritten questions, compare the candidates and scores, then toggle re-ranking on and off to see the ordering of the top few items.
Business test: Change one piece of content and see whether the version number and citations are updated synchronously.
- In the search test, switch
searchMode, record the number of candidates and the score, and check whether the fields of the invitation, comments, and revision notes correspond item by item. - Adjust
similarityandlimit, compare the ordering before and after enabling and disablingusingReRank, and check and record the cited text tokens and the array item count separately.