What this category's data looks like
The core materials for data versioning and change maintenance in peer review organizations are review invitations, expert review comments, and author revision notes. A review invitation contains the manuscript number, invitation date, expert name, and confirmation receipt; expert review comments contain review dimensions, the comment body, submission date, and signature; author revision notes contain point-by-point responses, revision locations, date, and signature. When these three types of materials enter HTTP interfaces and external systems, the review invitation serves as the trigger record, expert review comments serve as the process record, and author revision notes serve as the closed-loop record. Sources are editorial systems, email receipts, and manuscript platform exports. The update cadence advances with review rounds, with each round producing a new version. The field characteristic is that the name, quantity, and date of the same record must be consistent across the invitation, comments, and revision notes, and signatures and receipts must be complete.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The version ledger and change records are completed by subsequent nodes parsing the response, or by an external system handling it as agreed. The HTTP node sends a request to the target address; path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Review invitation | The invitation date, expert name, and confirmation receipt must be consistent with the expert review comments | View the fully rendered address in the request preview, and check the invitation record fields against the receipt |
| Expert review comments | The review dimensions, submission date, and signature must correspond point by point with the author revision notes | Check the request header names and value sources, and compare the dates in the comment body and the revision responses |
| Author revision notes | The point-by-point responses, revision locations, date, and signature must be consistent with the current version | Use a sample request to compare the response, and check the revision note version number and references |
| Request variables | Every placeholder can be traced to a global variable, system variable, or the output of a preceding node | Check the source of each placeholder in the variables panel, and confirm the values of variables and responseData |
Three common errors
- Symptom: The name, quantity, and date of the same manuscript do not match across two materials. Cause: The review invitation and expert review comments each maintain their own fields, and no comparison is made against the current version.
- Symptom: The author revision notes have been updated, but references still point to the old version. Cause: The version was not synchronized, the HTTP request did not carry the latest version identifier, and although the old version can be traced, the references were not refreshed.
- Symptom: Review comments lack a signature or receipt. Cause: When the external system handles it as agreed, the signature field is not validated, and the field being empty in the response body is still accepted by subsequent nodes.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, then compare the result against a sample, and confirm that the three placeholders Authorization, variables, and responseData can be traced.
Business test: change one piece of content and see whether the version number and references are updated in sync
- In the request preview, check the fully rendered address and path parameters, and confirm that the placeholder variables resolve to actual values
- In the variables panel, check the source of each placeholder, and confirm that
Authorizationand the request header value sources are consistent