A manuscript review process control method, system, device and storage medium based on a state machine

Abstract

The application discloses a manuscript review process control method, system and device based on a state machine and a storage medium, belongs to the technical field of manuscript review process control, and comprises a state machine engine module, a manuscript management module, a task scheduling module, a rule configuration module, an event listening module, an exception processing module, a log auditing module and a notification management module. The application standardizes each link of a review process into state nodes and transition rules by constructing a finite state machine model with a manuscript state as a core, realizes fine state management of the review process, and ensures that a manuscript is in a unique and explicit state at any time, state change must be triggered by a legal event and satisfy preset prerequisites, and the review process is normative and rigorous. Meanwhile, through the cooperative working mechanism of the exception processing module and the state machine engine, automatic detection and standardized processing of a review exception scene are realized.

Description

Technical Field

[0001] This invention relates to the field of manuscript review process control technology, specifically to a manuscript review process control method, system, device, and storage medium based on a state machine. Background Technology

[0002] Academic journals, publishing houses and other institutions generally adopt a "three-stage review" process in the manuscript processing, namely, preliminary review, secondary review (usually external expert review) and final review. The review process involves multiple stages such as manuscript registration, academic misconduct detection, expert selection, feedback of reviewers' comments, revision, acceptance decision, editing and proofreading. The process is complex and involves many roles, requiring a high degree of standardization and traceability.

[0003] Existing manuscript review systems employ linear workflow designs or simple task queues, lacking refined modeling of manuscript status. When manuscripts flow between different review stages, status changes lack clear triggering conditions and transfer rules, making the process prone to errors due to human intervention. For example, a manuscript in the "under external review" state may be mistakenly changed to "accepted," skipping the necessary final review stage and causing the review process to spiral out of control. Furthermore, there are numerous scenarios requiring exception handling during the review process, but existing systems lack standardized mechanisms for handling these exceptions, typically relying on manual intervention. This process is opaque, untraceable, and prone to overlooking abnormal states. Therefore, it is essential to invent a manuscript review process control method, system, device, and storage medium based on a state machine. Summary of the Invention

[0004] The purpose of this invention is to provide a manuscript review process control method, system, device, and storage medium based on a state machine. By constructing a finite state machine model with the manuscript state as the core, refined state management of the review process is achieved. At the same time, through the collaborative working mechanism of the exception handling module and the state machine engine, automatic detection and standardized processing of review exception scenarios are realized, thereby solving the problems currently on the market mentioned in the background.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a manuscript review process control system based on a state machine, comprising a state machine engine module, a manuscript management module, a task scheduling module, a rule configuration module, an event monitoring module, an exception handling module, a log auditing module, and a notification management module. The state machine engine module is bidirectionally connected to all the other modules and serves as the core control center of the system, driving the flow of manuscript status and the execution of business operations. The state machine engine module is used to load the state machine definition of the manuscript review process, maintain the current state of each manuscript, receive event inputs and drive state changes according to state transition rules, and call the corresponding action executor to perform business operations. The manuscript management module is used to store and manage the basic information, metadata, version records, and various document attachments of the manuscript during the review process; The task scheduling module is used to automatically create and assign review tasks based on the current status of the manuscript and the review process configuration, and to monitor the task execution progress. The rule configuration module is used to provide a visual configuration interface for administrators to define the status nodes, status transition rules, exception transition rules, and action bindings for each status in the review process. The event listening module is used to listen for events triggered by external systems or user operations, convert the events into a standard format, and submit them to the state machine engine module. The anomaly handling module is used to detect anomalies in the review process and trigger corresponding anomaly transfers or alarms according to the preset anomaly handling strategy. The log auditing module is used to record the complete trajectory of every status change of the manuscript in the review process, including the change time, operator, status before change, status after change, triggering event and operation notes, so as to achieve full traceability. The notification management module is used to automatically send notification messages to relevant roles when the status of a manuscript changes or a task is assigned.

[0006] Preferably, the state definition module is used to define the various state nodes of the manuscript in the review process. The state nodes include at least the following states: pending initial review, in the process of initial review, returned after initial review, pending secondary review, in the process of secondary review, returned after secondary review, secondary review conflict, pending final review, in the process of final review, returned after final review, under revision, overdue under revision, pending proofreading, in the process of typesetting, accepted, and rejected. The transfer rule module is used to store the rules for migrating from the current state to the target state under the trigger of a specific event. The rules include the source state, the target state, the triggering event, and the precondition verification function. The action execution module is used to be called after the state transfer is successful to execute the business operation associated with the target state. The business operation includes task creation, notification sending, document state change, and permission change. The context management module is used to maintain the context data of the current manuscript during the execution of the state machine, including manuscript metadata, review comments, operator information, and timestamps. The state persistence module is used to write the current state and state change history of the manuscript into the database to ensure the consistency and recoverability of the state data.

[0007] Preferably, the manuscript entry module is used to receive manuscripts submitted by authors, and to complete format verification, metadata extraction and storage. The version management module is used to manage multiple version iterations of manuscripts, including the original submission version, the revised version after revision, and the edited version, and to record the differences and relationships between each version. The attachment management module is used to manage various attachments generated in the review process, including review comments, revision instructions, copyright agreements and proofreadings.

[0008] Preferably, the task creation module is used to automatically create corresponding review task instances according to the actions defined in the state machine transition rules; the task allocation module is used to allocate tasks to specific responsible persons according to the preset allocation strategy; the task monitoring module is used to track the execution status of each review task in real time and feed it back to the state machine engine module; and the timeout detection module is used to periodically scan tasks that are in the "in progress" state but have exceeded the preset time limit and trigger timeout events.

[0009] Preferably, the anomaly detection module is used to monitor anomaly signals in the peer review process. The anomaly signals include task timeout signals, academic misconduct detection exceeding the standard signals, peer review conflict signals, and author revision overdue signals. The anomaly classification module is used to classify and grade anomalies according to their type and severity. The anomaly transfer module is used to query preset anomaly transfer rules based on the anomaly classification results and drive the manuscript status to the corresponding anomaly handling status. The manual intervention module is used to generate a manual intervention work order and notify the administrator to handle the anomaly when it cannot be handled automatically.

[0010] Preferably, the status change recording module is used to automatically record a change log each time the status of a manuscript changes. The change log includes the change time, operator identity, source status, target status, trigger event type, and change remarks. The operation behavior recording module is used to record all user operation behavior logs during the review process. The traceability query module is used to provide traceability query interfaces by manuscript, by time range, and by operator, supporting full-chain restoration of the review process.

[0011] This invention also provides a state machine-based manuscript review process control method, applied to the system described in any one of claims 1-6, comprising the following steps: S1 Process Modeling and Configuration: Administrators define the state machine model of the review process through the rule configuration module, including: configuring the set of state nodes, configuring state transition rules, configuring exception transition rules, and configuring the business actions associated with each state, thus completing the modeling and configuration of the review process; S2 Manuscript Submission and Initial Status Setting: The manuscript management module receives the manuscript submitted by the author, and after completing the storage in the database, it calls the state machine engine module to initially set the manuscript status to "pending initial review" and notifies the management module to automatically send the initial review task notification to the responsible editor. S3 event-driven state transition: The state machine engine module continuously listens for event inputs submitted by the event listening module. When a valid event is received, the following sub-steps are executed: S31: Based on the current status of the manuscript and the event type, query the matching status transition rules in the transition rules module; S32: If a rule is matched, call the precondition validation function to perform condition validation; S33: After the condition verification is passed, the state persistence module records the current state change log and updates the manuscript status to the target status; S34: The action execution module executes the business actions associated with the target state, including task creation and notification sending; S35: If no rule is matched or the precondition validation fails, reject the event and log the exception. S4 Review Task Scheduling and Execution: The task scheduling module generates specific review task instances based on the task creation action triggered by the state machine engine, assigns tasks to responsible persons according to the preset allocation strategy, monitors the task execution progress in real time, generates corresponding events when the task is completed and sends them back to the state machine engine module to trigger subsequent state transitions. S5 Anomaly Detection and Automated Handling: The anomaly handling module continuously detects anomaly signals in the peer review process. When an anomaly is detected, the following sub-steps are executed: S51: The anomaly classification module classifies and grades anomalies; S52: The exception transfer module queries the preset exception transfer rules based on the exception classification; S53: If a matching exception transition rule exists, drive the state machine to execute the exception state transition and transfer the manuscript to the corresponding exception handling state; S54: If no automatic processing rules exist, the manual intervention module will generate a manual intervention work order and notify the administrator. S6 Full-Link Log Traceability: The log audit module automatically records logs every time a status change or operation occurs, establishing a full-link traceability archive with the manuscript's unique identifier as the primary key, and supporting traceability queries by multiple dimensions; S7 Process Termination or Archiving: When the manuscript status transitions to the final state (including "accepted" and "rejected"), the state machine engine terminates the manuscript's status transition, and the manuscript management module completes the final archiving of the manuscript.

[0012] The present invention also provides a manuscript review process control device based on a state machine, including a memory and a processor. The memory stores a computer program that can be executed by the processor, and the processor executes the computer program to implement the control method as described in claim 7.

[0013] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the control method as described in claim 7.

[0014] Compared with the prior art, the beneficial effects of the present invention are as follows: This invention constructs a finite state machine model centered on the manuscript's status, standardizing each stage of the review process into state nodes and transition rules. This achieves refined state management of the review process, ensuring that the manuscript is in a unique and definite state at any given time. State changes must be triggered by legitimate events and meet preset preconditions, ensuring the standardization and rigor of the review process. Furthermore, through the collaborative working mechanism of the exception handling module and the state machine engine, the system achieves automatic detection and standardized handling of review exception scenarios. When exceptions such as review overdue, conflicting review comments, or overdue revisions occur, the system can automatically drive the manuscript into an exception handling state according to preset exception transition rules, or generate a manual intervention work order. The entire exception handling process is recorded and traceable, solving the problem of weak exception handling capabilities in traditional review systems.

[0015] This invention, through the decoupling design of the state machine engine and business logic, centralizes the management of the review process control logic in the rule configuration module. When the review rules are adjusted, only the state machine configuration needs to be modified without changing the core code, which significantly improves the scalability and maintainability of the system and reduces the system transformation costs caused by process adjustments. At the same time, through the full-link log traceability mechanism, the entire status change trajectory of the manuscript from submission to final archiving is fully recorded, providing complete data support for compliance auditing, problem investigation and process optimization of the review process, and improving the transparency and accountability of review management. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the control system structure of the present invention; Figure 2 This is a schematic diagram of the method flow of the present invention.

[0017] In the diagram: 1. State Machine Engine Module; 101. State Definition Module; 102. Transition Rule Module; 103. Action Execution Module; 104. Context Management Module; 105. State Persistence Module; 2. Manuscript Management Module; 201. Manuscript Entry Module; 202. Version Management Module; 203. Attachment Management Module; 3. Task Scheduling Module; 301. Task Creation Module; 302. Task Allocation Module; 303. Task Monitoring Module; 304. Timeout Detection Module; 4. Rule Configuration Module; 5. Event Listening Module; 6. Exception Handling Module; 601. Exception Detection Module; 602. Exception Classification Module; 603. Exception Transition Module; 604. Manual Intervention Module; 7. Log Auditing Module; 701. State Change Record Module; 702. Operation Behavior Record Module; 703. Traceability Query Module; 8. Notification Management Module. Detailed Implementation

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention. Example

[0019] Please see Figures 1 to 2 This invention provides a technical solution: a manuscript review process control system based on a state machine, including a state machine engine module 1, a manuscript management module 2, a task scheduling module 3, a rule configuration module 4, an event listening module 5, an exception handling module 6, a log auditing module 7, and a notification management module 8. The state machine engine module 1 is bidirectionally connected to all the other modules and serves as the core control center of the system, driving the flow of manuscript status and the execution of business operations. The state machine engine module 1 includes a state definition module 101, a transition rule module 102, an action execution module 103, a context management module 104, and a state persistence module 105. The state definition module 101 is used to define the various state nodes of the manuscript in the review process, including at least: pending initial review, in the process of initial review, returned after initial review, pending review, in the process of review, returned after review, review conflict, pending final review, in the process of final review, returned after final review, under revision, overdue under revision, pending proofreading, in the process of typesetting, accepted, and rejected. The transition rule module 102 is used to store the rules for migrating from the current state to the target state under the trigger of a specific event, including the source state, the target state, the triggering event, and the precondition verification function. The action execution module 103 is used to execute the business operations associated with the target state after the state transition is successful, including task creation, notification sending, document state change, and permission change. The context management module 104 is used to maintain the context data of the current manuscript. The state persistence module 105 is used to write the current state and state change history of the manuscript into the database. Manuscript Management Module 2 includes a manuscript entry module 201, a version management module 202, and an attachment management module 203. The manuscript entry module 201 is used to receive manuscripts submitted by authors, complete format verification, metadata extraction, and storage. The version management module 202 is used to manage multiple version iterations of manuscripts. The attachment management module 203 is used to manage various attachments generated during the review process. The task scheduling module 3 includes a task creation module 301, a task allocation module 302, a task monitoring module 303, and a timeout detection module 304. The task creation module 301 is used to automatically create review task instances according to the actions defined in the state machine transition rules; the task allocation module 302 is used to allocate tasks to responsible persons according to a preset allocation strategy; the task monitoring module 303 is used to track the execution status of each review task in real time; and the timeout detection module 304 is used to periodically scan tasks that exceed the preset time limit and trigger timeout events. Rule configuration module 4 provides a visual configuration interface for administrators to define the status nodes, status transition rules, exception transition rules, and action bindings for each status in the review process. Event listening module 5 is used to listen for events triggered by external systems or user operations, including manuscript submission events, peer review comment submission events, revision completion events, and timeout events. It converts the events into a standard format and submits them to state machine engine module 1. The anomaly handling module 6 includes an anomaly detection module 601, an anomaly classification module 602, an anomaly transfer module 603, and a manual intervention module 604. The anomaly detection module 601 is used to monitor anomaly signals in the review process; the anomaly classification module 602 is used to classify and grade anomalies according to their type and severity; the anomaly transfer module 603 is used to drive state transfers based on pre-set anomaly transfer rules queried according to the anomaly classification; and the manual intervention module 604 is used to generate a manual intervention work order when anomalies cannot be handled automatically. The log audit module 7 includes a status change recording module 701, an operation behavior recording module 702, and a traceability query module 703. The status change recording module 701 is used to automatically record change logs each time the status of a manuscript changes; the operation behavior recording module 702 is used to record all user operation behavior logs; and the traceability query module 703 is used to provide a multi-dimensional traceability query interface. The notification management module 8 is used to automatically send notification messages to relevant roles when the status of a manuscript changes or a task is assigned.

[0020] This system uses the state machine engine module 1 as the control center to construct a full lifecycle management architecture for the review process based on finite state machines. During the system startup phase, the administrator models and configures the review process through the rule configuration module 4. First, the state definition module 101 defines the set of all state nodes in the review process, including states such as pending initial review, in the process of initial review, returned after initial review, pending for review, in the process of review, returned after review, review conflict, pending final review, in the process of final review, returned after final review, under revision, overdue for revision, pending proofreading, in the process of typesetting, accepted, and rejected. Then, the transition rule module 102 configures the process. Legitimate transition relationships between different statuses: For example, the "Pending Initial Review" status transitions to the "Initial Review in Progress" status when triggered by the "Editor Receives Manuscript" event; the "Initial Review in Progress" status transitions to the "Pending Second Review" status when triggered by the "Initial Review Comments Submitted (Passed)" event, and transitions to the "Initial Review Returned" status when triggered by the "Initial Review Comments Submitted (Returned)" event; the "Second Review in Progress" status transitions to the "Pending Final Review" status when triggered by the "Reviewed by Two Experts" event and the opinions of the two experts are consistent, and transitions to the "Second Review Conflict" status when triggered by the "Reviewed by Two Experts" event but the opinions of the two experts conflict.

[0021] At the same time, the prerequisites for each state transition are configured. For example, in the "under review" state, at least two valid review opinions from experts must be returned before the transition can be triggered. The action execution module 103 binds the corresponding business actions in each state transition rule. For example, when entering the "pending review" state, an expert review task is automatically created; when entering the "under revision" state, the author is automatically notified and the revision timer is started; when entering the "accepted" state, a proofreading task is automatically created.

[0022] When an author submits a manuscript through the submission portal, the manuscript entry module 201 performs format verification and preliminary academic misconduct detection (plagiarism rate verification) on the manuscript. After extracting metadata, it stores the manuscript text and related attachments in the database. The version management module 202 records this submission as the original submission version. After the manuscript is entered into the database, the manuscript management module 2 calls the state machine engine module 1 to initially set the manuscript status to "pending preliminary review." The status persistence module 105 writes the initial status to the database, and the status change recording module 701 of the log audit module 7 records the first status change log. The management module 8 is then notified to automatically send a preliminary review task notification to the corresponding responsible editor.

[0023] After a manuscript enters the "Pending Initial Review" state, the responsible editor receives the initial review task through the system. The event listening module 5 captures the "Responsible Editor Receives Manuscript" event and submits it to the state machine engine module 1. The state machine engine module 1 queries the transfer rule module 102 based on the current status of the manuscript (Pending Initial Review) and the event type. After matching the corresponding transfer rule, it performs a precondition check (checking whether the current manuscript has been locked by other editors). After the check passes, the state persistence module 105 updates the manuscript status to "Under Initial Review". At the same time, the action execution module 103 triggers the task creation module 301 to generate an initial review task instance and update the task status to "Processing". During the initial review process, the responsible editor evaluates the manuscript's orientation, academic level, and completeness (Qi Qingding standards), forms initial review opinions, and submits them through the system. If the initial review opinion is "passed", the event "Initial review opinion submitted (passed)" will drive the manuscript from "under initial review" to "pending review"; if the initial review opinion is "returned" or "rejected", it will be transferred to the status of "initial review returned" or "rejected" respectively, and trigger the corresponding notification and rejection process.

[0024] After a manuscript enters the "Pending Review" state, the task creation module 301 of the task scheduling module 3 automatically creates expert review tasks based on the preset expert selection strategy. The task allocation module 302 allocates 2-3 peer reviewers based on the manuscript's discipline, the experts' academic reputation, research expertise, and recent research results using an intelligent matching algorithm based on the experts' research directions. The module then sends review invitations to the reviewers through the notification management module 8. After the reviewers receive the review tasks through the system, the manuscript status changes from "Pending Review" to "Under Review". The task monitoring module 303 starts the review timer. After the reviewers complete the review and submit their review comments, the task monitoring module 303 records the feedback of the review comments. The timeout detection module 304 periodically scans for review tasks that have not been submitted on time. When a review timeout is detected, a timeout event is triggered. After the state machine engine module 1 listens for a timeout event, the exception detection module 601 of the exception handling module 6 captures the exception signal, the exception classification module 602 classifies it as "task timeout - review overdue" level, and the exception transfer module 603 queries the preset exception transfer rules: if the timeout does not exceed the preset buffer period, a reminder notice is sent to the review experts and the "under review" status is maintained; if the buffer period is exceeded, the manuscript is automatically transferred to the "review overdue" exception status, and at the same time the manual intervention module 604 generates a manual intervention work order to notify the responsible editor to handle it manually.

[0025] Once the opinions of two or more reviewers have been returned, task monitoring module 303 summarizes the review opinions. If the two experts agree (both recommend acceptance or both recommend rejection), the event "Summary of Review Opinions (Consensus)" drives the manuscript from "Under Review" to "Pending Final Review". If the two experts disagree (one recommends acceptance and the other recommends rejection), the event "Summary of Review Opinions (Conflict)" drives the manuscript from "Under Review" to "Review Conflict" state. Anomaly handling module 6 triggers the "Review Conflict" handling process, deciding whether to submit the manuscript to a third expert for arbitration or have the editorial board decide based on preset rules. After processing, the opinions are summarized again and the status continues to flow.

[0026] Once a manuscript enters the "pending final review" stage, the editor-in-chief or editorial board will make the final review decision. The final review takes into account the journal's overall positioning and column planning, and comprehensively evaluates the manuscript's academic quality, orientation, and social impact based on the opinions of the initial and secondary reviews. If the final review is passed, the "final review passed" event drives the manuscript from the "pending final review" stage to the "accepted" stage; if the final review requires revision and re-review, it drives the manuscript to the "revision in progress" stage; if the final review decides to reject the manuscript, it drives the manuscript to the final "rejected" stage.

[0027] Once a manuscript enters the "Revision in Progress" status, the action execution module 103 automatically creates a revision task, notifies the author to revise according to the reviewers' comments and submit a revision explanation, and simultaneously starts the revision timer. The timeout detection module 304 monitors the revision deadline. If the author submits the revised manuscript within the specified deadline, the "Revision Completed" event drives the manuscript to either the "Pending Review" (resubmitted for review) or "Pending Final Review" (minor revisions) status, depending on the quality of the revisions. If the manuscript is not submitted within the revision deadline, the timeout event triggers the exception handling process, driving the manuscript to the "Revision Overdue" exception status, where the manual intervention module 604 notifies the responsible editor for processing.

[0028] Once the manuscript reaches the "Accepted" status, the action execution module 103 triggers the typesetting and proofreading tasks. The state machine drives the manuscript to sequentially transition to the "Pending Proofreading" and "Typesetting" states. The proofreading process employs a multi-round proofreading mechanism. The editor completes the first, second, and third proofreadings, as well as the printing proof. After each proofreading is completed, the submission of the proofreading event drives the transition between the proofreading sub-states. Once all proofreading is completed and the chief editor signs off on the printing, the manuscript finally reaches the "Accepted" final state. The state machine engine module 1 terminates the state transition of the manuscript, and the manuscript management module 2 completes the final archiving of the manuscript.

[0029] Throughout the entire system operation cycle, the status change recording module 701 of the log audit module 7 automatically records a complete change log each time the manuscript status changes, including the change time, operator identity, status before the change, status after the change, trigger event type, and change remarks; the operation behavior recording module 702 records the operation behavior logs of all users (authors, responsible editors, reviewers, chief editors, and administrators); and the traceability query module 703 provides full-link traceability capabilities with the manuscript's unique identifier as the primary key, supporting multi-dimensional queries by time range, operator, status type, etc., and can completely restore the entire review trajectory of any manuscript from submission to final archiving, providing complete data support for compliance auditing, problem investigation, and process optimization.

[0030] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A state machine-based manuscript review process control system, comprising a state machine engine module (1), a manuscript management module (2), a task scheduling module (3), a rule configuration module (4), an event monitoring module (5), an exception handling module (6), a log auditing module (7), and a notification management module (8), characterized in that: The state machine engine module (1) is bidirectionally connected to all other modules, serving as the core control center of the system and driving the flow of manuscript status and the execution of business operations. The state machine engine module (1) is used to load the state machine definition of the manuscript review process, maintain the current state of each manuscript, receive event inputs and drive state changes according to state transition rules, and call the corresponding action executor to perform business operations. The manuscript management module (2) is used to store and manage the basic information, metadata, version records and various document attachments of the manuscript during the review process; The task scheduling module (3) is used to automatically create and allocate review tasks according to the current status of the manuscript and the review process configuration, and to monitor the task execution progress. The rule configuration module (4) is used to provide a visual configuration interface for administrators to define the status nodes, status transition rules, exception transition rules and action bindings in each status of the review process. The event listening module (5) is used to listen to events triggered by external systems or user operations, convert the events into a standard format and submit them to the state machine engine module; The anomaly handling module (6) is used to detect anomalies in the review process and trigger corresponding anomaly transfers or alarms according to the preset anomaly handling strategy. The log audit module (7) is used to record the complete trajectory of each status change of the manuscript in the review process, including the change time, operator, status before change, status after change, triggering event and operation notes, so as to achieve full traceability; The notification management module (8) is used to automatically send notification messages to relevant roles when the status of a manuscript changes or a task is assigned.

2. The manuscript review process control system based on a state machine according to claim 1, characterized in that: The state machine engine module (1) includes a state definition module (101), a transition rule module (102), an action execution module (103), a context management module (104), and a state persistence module (105). The state definition module (101) is used to define the various state nodes of the manuscript in the review process. The state nodes include at least the following states: pending initial review, under initial review, returned after initial review, pending second review, under second review, returned after second review, second review conflict, pending final review, under final review, returned after final review, under revision, overdue for revision, pending proofreading, under typesetting, accepted, rejected. The transition rule module (102) is used to store the state triggered by a specific event. The rules for migrating down to the target state include the source state, the target state, the triggering event, and the precondition verification function. The action execution module (103) is called after the state transition is successful to execute the business operations associated with the target state. The business operations include task creation, notification sending, document state change, and permission change. The context management module (104) is used to maintain the context data of the current manuscript during the execution of the state machine, including manuscript metadata, review comments, operator information, and timestamps. The state persistence module (105) is used to write the current state of the manuscript and the history of state changes into the database to ensure the consistency and recoverability of the state data.

3. The manuscript review process control system based on a state machine according to claim 1, characterized in that: The manuscript management module (2) includes a manuscript entry module (201), a version management module (202), and an attachment management module (203). The manuscript entry module (201) is used to receive manuscripts submitted by authors and complete format verification, metadata extraction, and storage. The version management module (202) is used to manage multiple version iterations of manuscripts, including the original submission version, the revised version after revision, and the edited version, and to record the differences and relationships between each version. The attachment management module (203) is used to manage various attachments generated in the review process, including review comments, revision instructions, copyright agreements, and proofreadings.

4. The manuscript review process control system based on a state machine according to claim 1, characterized in that: The task scheduling module (3) includes a task creation module (301), a task allocation module (302), a task monitoring module (303), and a timeout detection module (304). The task creation module (301) is used to automatically create corresponding review task instances according to the actions defined in the state machine transition rules. The task allocation module (302) is used to allocate tasks to specific responsible persons according to the preset allocation strategy. The task monitoring module (303) is used to track the execution status of each review task in real time and feed it back to the state machine engine module (1). The timeout detection module (304) is used to periodically scan tasks that are in the "in progress" state but exceed the preset time limit and trigger timeout events.

5. The manuscript review process control system based on a state machine according to claim 1, characterized in that: The anomaly handling module (6) includes an anomaly detection module (601), an anomaly classification module (602), an anomaly transfer module (603), and a manual intervention module (604). The anomaly detection module (601) is used to monitor anomaly signals in the review process. The anomaly signals include task timeout signals, academic misconduct detection exceeding the standard signals, reviewer opinion conflict signals, and author revision overdue signals. The anomaly classification module (602) is used to classify and grade anomalies according to their type and severity. The anomaly transfer module (603) is used to query the preset anomaly transfer rules according to the anomaly classification results and drive the manuscript status to the corresponding anomaly handling status. The manual intervention module (604) is used to generate a manual intervention work order and notify the administrator to handle the anomaly when it cannot be handled automatically.

6. The manuscript review process control system based on a state machine according to claim 1, characterized in that: The log audit module (7) includes a status change recording module (701), an operation behavior recording module (702), and a traceability query module (703). The status change recording module (701) is used to automatically record change logs each time the status of a manuscript changes. The change logs include change time, operator identity, source status, target status, trigger event type, and change remarks. The operation behavior recording module (702) is used to record all user operation behavior logs during the review process. The traceability query module (703) is used to provide traceability query interfaces by manuscript, by time range, and by operator, supporting full-link restoration of the review process.

7. The present invention also provides a manuscript review process control method based on a state machine, applied to the system described in any one of claims 1-6, comprising the following steps: S1 Process Modeling and Configuration: The administrator defines the state machine model of the review process through the rule configuration module (4), including: configuring the set of state nodes, configuring state transition rules, configuring exception transition rules, configuring business actions associated with each state, and completing the modeling and configuration of the review process; S2 Manuscript Submission and Initial Status Setting: The manuscript management module (2) receives the manuscript submitted by the author, and after completing the storage, it calls the state machine engine module (1) to initially set the manuscript status to "pending preliminary review" and notifies the management module (8) to automatically send the preliminary review task notification to the responsible editor. S3 event-driven state transition: State machine engine module (1) continuously listens for event inputs. When a valid event is received, the following sub-steps are executed: S31: Based on the current status of the manuscript and the event type, query the matching status transition rules in the transition rule module (102); S32: If a rule is matched, call the precondition validation function to perform condition validation; S33: After the condition verification is passed, the state persistence module (105) records the current state change log and updates the manuscript status to the target status; S34: The action execution module (103) executes the business actions associated with the target state, including task creation and notification sending; S35: If no rule is matched or the precondition validation fails, reject the event and log the exception. S4 Review Task Scheduling and Execution: The task scheduling module (3) generates specific review task instances based on the task creation action triggered by the state machine engine, assigns the task to the responsible person according to the preset allocation strategy, monitors the task execution progress in real time, generates corresponding events when the task is completed and sends them back to the state machine engine module (1), triggering subsequent state transitions. S5 Anomaly Detection and Automatic Processing: The anomaly processing module (6) continuously detects anomaly signals in the review process. When an anomaly is detected, the following sub-steps are executed: S51: The anomaly classification module (602) classifies and grades anomalies; S52: The exception transfer module (603) queries the preset exception transfer rules according to the exception classification; S53: If a matching exception transition rule exists, drive the state machine to execute the exception state transition and transfer the manuscript to the corresponding exception handling state; S54: If no automatic processing rules exist, the manual intervention module (604) will generate a manual intervention work order and notify the administrator; S6 full-link log traceability: The log audit module (7) automatically records logs when each status change and operation occurs, establishes a full-link traceability file with the manuscript's unique identifier as the primary key, and supports traceability queries by multiple dimensions; S7 Process Termination or Archiving: When the manuscript status transitions to the final state (including "accepted" and "rejected"), the state machine engine terminates the status transition of the manuscript, and the manuscript management module (2) completes the final archiving of the manuscript.

8. The present invention also provides a manuscript review process control device based on a state machine, including a memory and a processor, wherein the memory stores a computer program that can be executed by the processor, and the processor executes the computer program to implement the control method as described in claim 7.

9. The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the control method as described in claim 7.

Images