What this category's data looks like
This page focuses on progress records and statistical verification for journal three-stage review, three-proof correction, and editorial quality. The source materials are three types of editorial process documents: three-stage review forms, proofs, and proofreading records. The three-stage review form carries the dates and signatures for initial review, re-review, and final review; the proof carries edition and proof-round markings; the proofreading record carries the issue entries and receipts for each proof round. Materials are aggregated weekly or monthly into a progress table, with fields including record name, quantity, date, signature status, and exception notes. When these three types of materials enter this function, the three-stage review form provides process nodes and responsible persons, the proof provides the correspondence between versions and proof rounds, and the proofreading record provides entry-level details. Together they support the verification of progress records and the explanation of statistical criteria. The update cadence is based on weekly or monthly reports as nodes. The field characteristics require that names, quantities, and dates can be matched item by item between the two types of materials, and exceptional situations are stated in the table header criteria.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "progress table and statistical criteria explanation" is parsed by subsequent nodes, or handled by an external system according to the agreement to complete the next step. The HTTP node does not replace the external system in writing to the database or approving; it only sends requests and retrieves results according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| Three-stage review form | The fields, dates, and signatures of the three-stage review form must correspond item by item with the proof and proofreading record. The name, quantity, and date of the same record must not mismatch between the two materials. | Take one three-stage review form, verify the rendered complete address and request body fields in the request preview, and compare the date and signature status in the returned fields. |
| Proof | The proof must be synchronized with the edition and proof round of the three-stage review form. If the version is not synchronized, it must not be counted in the progress total. | Use one proof sample to compare against the return, verify the request header names and value sources, and confirm that the version field is consistent with the three-stage review form. |
| Proofreading record | The number of entries, dates, and receipts of the proofreading record must correspond with the proof. Entries missing signatures or receipts must be listed separately as exceptions in the criteria. | Verify the source of each placeholder in the variable panel, confirm the field mapping of variables and responseData, and check whether Authorization is passed in according to the external system's requirements. |
| Progress table and statistical criteria explanation | The record count and statistical count must match. The criteria must be written in the table header, and exceptional situations must be noted in the table header. | Use one week of records to verify the total, and check item by item whether the name, quantity, date, and signature are consistent between the two types of materials. |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the three-stage review form and the proofreading record. Cause: The two materials are entered separately, no item-by-item comparison is made, and the versions are not synchronized.
- Symptom: After the proof edition is updated, the progress table still uses the old edition for statistics. Cause: The versions are not synchronized, and the criteria do not state the version correspondence in the table header.
- Symptom: Proofreading records missing signatures or receipts are still counted in the completion total. Cause: Exceptional situations are not listed separately in the criteria, and they are not excluded during statistics.
How to verify the setup
This function's acceptance: In the request preview, verify the rendered request, verify the status code and returned fields, then compare the result against one sample, and confirm that the placeholder sources for Authorization, variables, and responseData are traceable.
Business test: Use one week of records to verify the total, check whether the criteria and exceptions are clearly written, and whether the record count and statistical count match.
- In the variable panel, verify the source of each placeholder, and confirm that the variables in the request address and path parameters, request headers, and request body can all be resolved into actual values.
- Use one sample request to compare against the return, check that the request body fields are consistent with the external interface agreement, and avoid the external system receiving empty fields.