Document digital management method and device, equipment and storage medium

Abstract

The invention relates to the field of digitization, and discloses a document digitization management method and device, equipment and a storage medium. The method comprises the following steps: displaying a document image of a to-be-processed paper document through a front-end interface, and carrying out digital processing on contents in a region of interest selected by a user; the operation description of each step node in the digital processing process is pushed in a step-by-step navigation mode through a front-end interface, and after feedback of a user is received, corresponding operation logic is triggered and executed; displaying progress information of each step node on a front-end interface through a progress bar component; and when it is determined that the digital processing process is completed, outputting the processed content in the region of interest in a target document format selected by the user. In the document digitization process, step-by-step navigation and a visual progress bar display mechanism are introduced, so that user operation is simplified, accurate control and transparent management of complex processes are realized, and document digitization management efficiency and user experience are remarkably improved.

Description

Technical Field

[0001] The present application relates to the field of digitization, and in particular to a document digitization management method, device, equipment and storage medium. Background Art

[0002] With the rapid development of digital technology, all walks of life have gradually realized the transformation from traditional paper-based to digital office, and digital management systems have been gradually introduced into daily life to realize functions such as electronic documents and process automation. However, during the application process, people found that although digital processing has brought many conveniences, there are still some problems in management efficiency.

[0003] Specifically, the current digital processing system's user interface is not user-friendly and the operation is complex. At the same time, since the digital processing system directly performs digital processing at the back end, it is difficult for managers to accurately measure the actual completion of various tasks, which indirectly reduces management efficiency. Therefore, the problem of poor management efficiency in the digital processing process needs to be solved urgently. Summary of the invention

[0004] In a first aspect, the present application provides a document digital management method, comprising: Displaying a document image of a paper document to be processed through a front-end interface, receiving content in a region of interest selected by a user in the document image, and digitally processing the content in the region of interest; Pushing the operation description of each step node in the digital processing process in sequence in a step-by-step navigation manner through the front-end interface, and triggering the execution of corresponding operation logic after receiving user feedback based on the operation description; Displaying progress information of each step node on the front-end interface through a progress bar component, each step node corresponds to a progress bar component; The target document format selected by the user is received, and when it is determined that the digitization process is completed, the digitized content in the region of interest is output in the target document format.

[0005] In an optional implementation, displaying the progress information of each step node through a progress bar component on the front-end interface includes: Through a plurality of predefined task functions, the total execution amount of each step node is simulated and calculated; each step node is configured with a task function; Get the current execution amount of the current step node through the built-in callback function of the target task function; Calculate the completion percentage of the current step node according to the total execution amount and the current execution amount, and obtain the progress information of the current step node; The progress information is transmitted to the front-end interface so as to dynamically display the progress information through a progress bar component in the front-end interface.

[0006] In an optional implementation manner, dynamically displaying the progress information through a progress bar component in the front-end interface includes: Parsing the progress information through a front-end processor of the front-end interface to match a target progress bar component, and smoothly adjusting the progress bar length of the target progress bar component in a transition animation manner, wherein the progress bar length is used to indicate the completion percentage; If it is determined that the execution of the current step node fails, the progress bar component of the current step node is stopped, the progress bar color of the progress bar component is changed to the target color, and a progress abnormality prompt message is displayed; If a rollback request is received, the progress bar lengths of all progress bar components between the specified step node and the current step node are cleared, and the specified step node is rolled back; the rollback request is used to instruct the current digital processing process to roll back to the specified step node.

[0007] In an optional implementation, the current execution amount of each step node is the current completion quantity of a number of quantifiable sub-stages divided corresponding to each step node or the current execution duration of each step node.

[0008] In an optional implementation, the operation description of each step node in the digital processing process is pushed in sequence through the front-end interface in a step-by-step navigation manner, and after receiving user feedback based on the operation description, the corresponding operation logic is triggered to execute, including: At least one navigation guide box is pre-set for each step node in the front-end interface, and a click event listener is bound to the operation component in each navigation guide box, so as to listen to the click event triggered by the operation component according to the click event listener; each navigation guide box is arranged according to a predetermined layout rule, and each navigation guide box contains the step name, operation description and operation component of the target step node; the click event is used to represent the user's feedback based on the operation description; Display the navigation guide box corresponding to the current step node in a step-by-step navigation manner; Update the state attribute of the current navigation guide frame according to the monitored click event, and trigger the execution of the operation logic corresponding to the click event; If it is determined that the operation logic execution fails, then redisplaying the navigation guide frame corresponding to the current step node or displaying the first target guide frame; If it is determined that the operation logic has been completed, the next navigation guide box is displayed in a step-by-step navigation manner.

[0009] In an optional implementation, before the triggering of the operation logic corresponding to the click event, the method further includes: Performing a validity check on the click event and determining whether the user has completed the necessary operations indicated in the navigation guide box; If the legality check fails and / or the necessary operation is not completed, then the navigation guide frame corresponding to the current step node is redisplayed or the second target guide frame is displayed; If the legality check passes and the necessary operations are completed, the operation logic corresponding to the click event is triggered and executed.

[0010] In an optional embodiment, the method further comprises: Receive the report generation parameter items selected by the user, and assemble an execution report according to the execution process and execution result of each step node according to the report generation parameter items, wherein the execution report is used to display the execution status of the corresponding step node; the report generation parameter items include the report generation format, the level of detail, and the report content to be generated; Outputting the execution report through the front-end interface; Before outputting the execution report through the front-end interface, the method further includes: Previewing the execution report to be output through the front-end interface, so that the user can preview and confirm the execution report to be output; If the report change information of the user is received, the corresponding execution report is modified according to the report change information; If confirmation output information of the user confirming to output the execution report to be output is received, the execution report is output through the front-end interface according to the confirmation output information; After outputting the execution report through the front-end interface, the method further includes: A report display parameter item selected by a user is received, report data corresponding to the report display parameter item is filtered out from the execution report, and the report data is displayed through the front-end interface.

[0011] In a second aspect, the present application provides a document digital management device, comprising: A content selection module is used to display a document image of a paper document to be processed through a front-end interface, receive content in an area of ​​interest selected by a user in the document image, and perform digital processing on the content in the area of ​​interest; A digitization module, used to push the operation description of each step node in the digitization process in sequence in a step-by-step navigation manner through the front-end interface, and trigger the execution of corresponding operation logic after receiving user feedback based on the operation description; A progress monitoring module, used to display the progress information of each step node on the front-end interface through a progress bar component, each step node corresponds to a progress bar component; The output module is used to receive the target document format selected by the user, and when it is determined that the digitization process is completed, output the content in the interest area after digitization in the target document format.

[0012] In a third aspect, the present application provides a computer device, comprising a processor and a memory, wherein the memory stores a computer program, and the processor is used to execute the computer program to implement the aforementioned document digitization management method.

[0013] In a fourth aspect, the present application provides a computer storage medium storing a computer program, which, when executed on a processor, implements the document digitization management method described above.

[0014] The embodiments of the present application have the following beneficial effects: The embodiment of the present application provides a document digitization management method, which efficiently manages the entire document digitization process through the interaction between the user and the front end, and the front end and the back end, and introduces a step-by-step navigation and a visual progress bar display mechanism, which simplifies user operations while achieving precise control and transparent management of complex processes, significantly improving the management efficiency and user experience of document digitization. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present application and should not be regarded as limiting the scope of protection of the present application. For ordinary technicians in this field, other related drawings can also be obtained based on these drawings without creative work.

[0016] Figure 1 A schematic diagram of the structure of a document digitization processing system in an embodiment of the present application is shown; Figure 2 A schematic diagram of a process of a document digital management method in an embodiment of the present application is shown; Figure 3 A schematic diagram showing a front-end interface display of a document digitization processing system in an embodiment of the present application is shown; Figure 4 Another schematic diagram of the process of the document digital management method in the embodiment of the present application is shown; Figure 5 Another front-end interface display schematic diagram of the document digitization processing system in the embodiment of the present application is shown; Figure 6 A structural schematic diagram of a document digital management device in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0017] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments.

[0018] The components of the embodiments of the present application generally described and shown in the drawings herein may be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0019] Hereinafter, the terms "including", "having" and their cognates, which may be used in various embodiments of the present application, are intended only to indicate specific features, numbers, steps, operations, elements, components, or combinations of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components, or combinations of the foregoing items or adding the possibility of one or more features, numbers, steps, operations, elements, components, or combinations of the foregoing items.

[0020] Furthermore, the terms “first”, “second”, “third”, etc. are merely used for distinguishing descriptions and are not to be understood as indicating or implying relative importance.

[0021] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meanings as those generally understood by those skilled in the art to which the various embodiments of the present application belong. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meanings as the contextual meanings in the relevant technical field and will not be interpreted as having idealized meanings or overly formal meanings unless clearly defined in the various embodiments of the present application.

[0022] In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0023] AJAX (Asynchronous JavaScript and XML) is a technology for creating fast dynamic web pages. It enables web pages to update part of the page content asynchronously instead of reloading the entire page every time data is interacted with.

[0024] The embodiment of the present application provides a document digitization management method, which efficiently manages the entire document digitization process through the interaction between the user and the front end, and the front end and the back end, and introduces a step node management mechanism for step-by-step navigation, which simplifies user operations, and also realizes visual monitoring of progress under multi-task parallel processing, thereby improving the user experience. In short, this embodiment significantly improves the efficiency and user experience of document digitization through user-friendly interface design, step-by-step navigation mechanism, and real-time progress monitoring. It not only simplifies the operation process, but also provides comprehensive progress visualization and report generation functions, which is very suitable for application scenarios that require high precision and efficient management.

[0025] In this embodiment, the method can be implemented based on a specific document digitization processing system, wherein the system is used to convert paper documents into electronic documents and perform other operations on the electronic documents, such as digital calculations.

[0026] Furthermore, the system can execute the document digitization processing method based on the internal computing program to realize the digitization processing of paper documents and obtain electronic documents. In this process, each function realized by the system based on the document digitization processing method can be set up with a corresponding module internally. In other words, the system can realize one or more functions through the corresponding modules set up internally, that is, when the system is running, each module is used to execute one or more steps of the document digitization processing method. Among them, the module can be a hardware module or device, or a programmed software function module or program code, which is not limited in this embodiment.

[0027] For example, Figure 1 As shown, the system includes an image acquisition module 110, an image preprocessing module 120, a character recognition module 130 and an information management module 140; wherein the image acquisition module 110 is used to obtain image data of a paper document; the image preprocessing module 120 is used to optimize image quality and improve recognition accuracy; the character recognition module 130 is used to extract text information from an image; the information management module 140 is used to manage and store recognized text information, and can also perform corresponding processing based on the text information, such as digital calculations.

[0028] Furthermore, in the process of executing the document digitization management method and digitizing paper documents, the system monitors and manages the document digitization process through the interaction between the user and the front end, and between the front end and the back end, thereby optimizing the digitization process of paper documents and improving processing efficiency and accuracy. It can be understood that the entire document digitization process is divided into back-end logic processing and front-end logic processing; wherein the front end is used to display the document image and interact with the user, and the back end is used to monitor and execute the digitization processing logic according to the interaction results between the front end and the user, and to display information such as the digitization processing progress to the user through the front end, so that the user can intuitively understand the entire digitization process and improve the user experience and satisfaction.

[0029] For reference, Figure 2 As shown, the document digital management method may specifically include the following steps: S210, displaying a document image of a paper document to be processed through a front-end interface, receiving content in an area of ​​interest selected by a user in the document image, and digitally processing the content in the area of ​​interest.

[0030] In this embodiment, the document image of the paper document to be processed is collected in advance by a device such as a camera or a scanner, and the backend can subsequently digitize the document image. The types of the paper document include but are not limited to single-page or multi-page documents such as contracts, bills, invoices, and handwritten documents.

[0031] Then, the document image is displayed through the front-end interface for the user to view and confirm. Optionally, before the document image is displayed on the front-end interface, the back-end may also pre-process the collected document image, such as format conversion, denoising, binarization, perspective correction, etc. Exemplarily, after receiving the image data of the document to be processed uploaded by the user, this embodiment may convert the image data into a standard digital format to facilitate the subsequent rapid digital processing of the document image data. The standard digital format includes but is not limited to JPEG, PNG or PDF format, with a resolution of not less than 300dpi; then Gaussian filtering is used to eliminate noise (σ=1.5), an adaptive threshold segmentation algorithm is applied for binarization, and Hough transform is used to detect document edges and perform perspective correction and other processing.

[0032] In one example, the system pre-builds a front-end interface using technologies such as HTML, CSS, and JavaScript to ensure that images on the front-end interface load smoothly and the interface is user-friendly and easy to operate. Then, a front-end framework (such as React, Vue, or Angular) is used to obtain and display the image of the paper document to be processed from the back-end, and then the Canvas element or similar technologies are used to display the document image on the front-end interface.

[0033] For example, Figure 3 As shown, the front-end interface can display the operation pages of multiple documents to be processed through the task management window. The task management window includes multiple display items such as task ID, picture, result, time and operation. The user can click the "Picture" column to view the document content processed corresponding to the task ID, and click the "Result" column to view the corresponding digitized result of the document, and choose whether to delete the current task by clicking the "Delete" button component in the "Operation" column.

[0034] Furthermore, in the front-end interface, the document images of different paper documents to be processed can be displayed through a preview box; wherein, the preview box allows the user to view and select the area of ​​interest to be digitized in the document image. The selection action includes regular selection and irregular selection, regular selection includes rectangular selection, circular selection, etc., and irregular selection is free graphic selection. The area of ​​interest is the entire area or part of the area of ​​the document image.

[0035] In other words, the drag-and-drop selection function can be implemented on the front-end interface, that is, the user can directly select a specific area of ​​interest (such as a table, text paragraph, etc.) on the document image displayed on the front-end interface. The front-end interface receives the position of interest selected by the user by dragging the mouse on the displayed document image, and automatically identifies and records the coordinate information of the area of ​​interest selected by the user. In this process, JavaScript can be used to monitor and calculate the coordinate information of the area of ​​interest selected by the user. Then, the back-end marks the content corresponding to the coordinate information according to the coordinate information of the area of ​​interest, so as to facilitate subsequent efficient digital processing.

[0036] Furthermore, the front-end interface also allows users to set digital processing modes, wherein the digital processing modes include but are not limited to batch processing of multiple documents, single document processing, batch processing of single document interest areas, and batch processing of multiple document interest areas. The specific type of processing mode can be set according to actual needs and is not limited here.

[0037] Furthermore, the backend can digitize the document image according to the area of ​​interest and digitization processing mode selected by the user. For example, the content in the area of ​​interest is digitized through OCR (optical character recognition) technology or other image processing algorithms, and then the results of the digitization processing are recorded and stored for subsequent processing. Among them, the digitization process includes multiple steps such as document uploading, image preprocessing, character recognition, text proofreading, digital calculation, document publishing, etc., which can be set according to actual needs and are not limited to this.

[0038] In some examples, the entire digital processing process can be decomposed into tasks to obtain multiple independent but interrelated step nodes; that is, each task in the digital processing process corresponds to a step node.

[0039] S220, pushing the operation description of each step node in the digital processing process in sequence in a step-by-step navigation manner through the front-end interface, and triggering the execution of corresponding operation logic after receiving user feedback based on the operation description.

[0040] It can be understood that the front-end interface can also be used to display the progress information of each step node in the digital processing process, and to push the step name of each step node in sequence in the form of a step-by-step navigation or wizard page according to the predefined task flow, and to display the operation description of each step node; wherein the operation description is used to indicate the navigation process of the current step node. It should be noted that the number of step nodes used to display the operation description in the form of a step-by-step navigation is less than or equal to the total number of step nodes set in the digital processing process, that is, it is allowed to display only part of the step node's operation navigation process to the user in the front-end interface.

[0041] Exemplarily, at least one navigation guide box is set in advance in the front-end interface for each step node that needs to display navigation guides to the user during the document digitization process, wherein each navigation guide box is arranged according to a predetermined layout rule, which can be arranged horizontally, vertically, or in a grid form, etc. The specific rules can be set according to actual needs and are not limited to this. Each navigation guide box contains the step name of the target step node, the operation description (detailed description of the specific operation that the user needs to perform) and the operation component (such as buttons and input boxes, etc.).

[0042] Then, a click event listener is bound to each operation component to listen to the click event triggered by the operation component according to the click event listener. The click event is used to characterize the user's feedback based on the operation description. In other words, the click event listener is used to capture the user's click behavior on the operation component, and the click behavior is the user's feedback. The click behavior can be identified later to process the user feedback.

[0043] Then, the navigation guide box corresponding to the current step node is displayed in a step-by-step navigation manner; initially, the navigation guide box corresponding to the first step node is displayed by default, and the display content of the navigation guide box is dynamically adjusted according to the processing status of the current step node, hiding the completed or irrelevant navigation guide boxes.

[0044] At the same time, when the user clicks on an operation component of the currently displayed navigation guide box, the bound click event is triggered. The click event carries the user's behavior information (such as the target step node ID, operation type, etc.). After the click event listener listens to the click event, it transmits the click event to the backend. The backend updates the state attributes of the current navigation guide box on the front-end interface according to the listened click event, and triggers the operation logic corresponding to the click event.

[0045] In one example, before triggering the operation logic corresponding to the click event, the click event is first checked for legitimacy to verify whether the user meets the triggering conditions (such as entering correct data, meeting the preconditions), and to determine whether the user has completed the necessary operations indicated in the navigation guide box (such as checking whether the input fields are filled in completely, or verifying whether certain conditions are met); if the legitimacy check fails and / or the necessary operations are not completed, the navigation guide box corresponding to the current step node and / or the second target guide box is displayed again, and the second target guide box is a guide box that displays abnormal prompt information; if the legitimacy check passes and the necessary operations are completed, the operation logic corresponding to the click event is triggered, and the operation logic includes but is not limited to updating the status information of the current step node and calling the API to perform corresponding operations, without specific limitation.

[0046] Furthermore, if it is determined that the operation logic execution fails, the navigation guide frame corresponding to the current step node is redisplayed or the first target guide frame is displayed or the next navigation guide frame is directly jumped to, and the first target guide frame is a guide frame that displays abnormal prompt information.

[0047] If it is determined that the operation logic has been completed, the next navigation guide box is displayed in a step-by-step navigation manner, and the state information of the step node is updated. The jump method between each navigation guide box can be smooth scrolling or directly switching the display area, which is not limited.

[0048] In addition, the state attributes (such as color, icon, etc.) of the current navigation guide frame may be updated according to the result of the click event so that the user can intuitively understand the progress. The specific settings may be made according to actual needs, and this embodiment does not limit this.

[0049] Exemplarily, clear operation instructions for corresponding step nodes are displayed on the front-end interface to ensure that users can understand and execute them correctly. For example, at the beginning of the current step node, the operation description is pushed to the user through the front-end interface (for example: prompting "Please check whether the character recognition result is correct", "Please confirm whether to perform digital calculations on the recognized numbers", etc.); in other words, the user understands and confirms each step node that needs to be executed currently through the operation description, and after confirmation, clicks buttons such as "OK" or "Cancel" or "Previous" or "Skip" displayed in the current navigation guide box to trigger a click event, so that the back end triggers the actual execution of the corresponding step node according to the click event.

[0050] In one example, this embodiment displays the operation description of each step node in sequence on the front-end interface, and can specifically present the various stage processes of each step node in the form of a list or card. At the same time, the Java Script click event listener listens to the click event of the user operation (such as clicking the "Next" or "OK" button), and the back-end dynamically updates the status information of the current step node according to the click event, and triggers the status verification function to check whether it is currently allowed to switch from the current stage process of the current step node to the next stage process of the current step node or the next step node. The front-end interface receives the progress message of the current step node sent by the back-end, and automatically jumps to display the navigation guide box of the corresponding step node or the corresponding stage process.

[0051] Moreover, after triggering the backend to execute the operation logic of the corresponding step node, the backend can call different APIs or execute different processing functions according to the different step nodes to execute the operation logic of the target step node; among them, the selection of API and processing function is not limited, and the correspondence between each step node and the callable API or processing function can be set according to actual needs and is not limited.

[0052] In addition, the front-end interface also provides an embedded help function. When users trigger the execution of each step node through step-by-step navigation, they can view prompt boxes, quick help documents or tutorial videos at any time to solve common problems. These contents are displayed in the form of pop-ups and prompt bubbles, and users can get the required information without leaving the current interface. Or, based on user operating habits, corresponding optimization suggestions can be output. For example, for commonly used document processing processes, corresponding prompt information can be output to prompt users to set up automated tasks to improve the efficiency of daily operations.

[0053] As a feasible implementation method, when processing the document digitization process, the back-end can automatically decide whether to not execute certain step nodes (i.e., skip certain non-essential step nodes) based on the results of the previous rapid character recognition, and not display the skipped step nodes in the step-by-step navigation of the front-end interface (i.e., skip the step-by-step navigation instructions of non-essential step nodes, and only display the navigation instructions of necessary step nodes).

[0054] Exemplarily, after the document image data is uploaded, a quick character pre-recognition operation is first performed on the uploaded document image data (this operation is not equivalent to the aforementioned character recognition step node), that is, structured recognition is first performed on the document image data to determine whether the document image meets one of the preset conditions, which include but are not limited to one or more conditions such as not containing numbers that meet the calculation requirements, the correct text direction, etc. The specific condition settings can be set according to actual needs; and then after determining that the document image meets the corresponding conditions, the corresponding step node is skipped in the subsequent actual digital processing process; for example, if the document image does not contain numbers that meet the calculation requirements, the step node of digital calculation is skipped; if the text direction of the document image is correct, the step node of correcting the text direction is skipped.

[0055] In one embodiment, taking the step node of determining whether the document image skips digital calculation as an example, during the execution of the fast character pre-recognition operation, the document image is first subjected to structured recognition to determine whether the document image contains a table structure. When a table structure is detected, a table OCR parser is called to perform character recognition in a subsequent character recognition step node. Otherwise, free text recognition is performed in a subsequent character recognition step node.

[0056] After the fast character pre-recognition operation is processed, structured recognition result data is generated, which includes the text content and its coordinate position information in the document. Then, according to the pre-built digital content detection rule matrix, context association analysis is performed. When digital content is detected in the predetermined window range (5 characters before and after) of the calculation indicator word, it is marked as requiring calculation processing (i.e., meeting the calculation requirements).

[0057] Among them, the digital content detection rule matrix includes: continuous number matching rules (detecting patterns of ≥3 consecutive numbers (regular expression: \b\d{3,}\b)); currency value recognition rules (matching numerical expressions containing currency symbols); calculation instruction vocabulary (storing a set of verbs related to numerical calculations (including "calculate", "total", "sum", etc.)).

[0058] In other words, in combination with the context association analysis and the above-mentioned digital content detection rule matrix, if it is determined that the structured recognition result data contains digital content that conforms to the above-mentioned digital content detection rule matrix and the digital content is associated with calculation indicator words in the calculation indicator word library, then it is determined that the steps of digital calculation need to be performed.

[0059] Correspondingly, an instruction to skip the digital calculation step is generated when any of the following conditions is met: Condition 1: No digital content that conforms to the above-mentioned digital content detection rule matrix is ​​detected in the document; Condition 2: Digital content is detected but is not associated with any calculation indicator.

[0060] Then, a step jump instruction set is generated, the skipped step identifier and the jump basis are recorded, and the front-end interface is updated based on the step jump instruction; wherein, when implementing the step-by-step navigation, the front-end interface pre-builds a navigation node tree structure, and each node contains a step ID, a display name, and a dependency relationship. Then, when updating the step nodes of the step-by-step navigation guide, a node filtering algorithm is applied to remove the step nodes marked as skipped from the navigation node tree structure and dynamically redraw the step connection lines of each step node displayed on the front-end interface.

[0061] Furthermore, this embodiment realizes the dynamic optimization of the document processing flow by establishing a multi-level OCR analysis mechanism and an intelligent decision-making model. In particular, before the formal digital processing, a composite condition judgment strategy is used to identify all necessary step nodes and non-essential step nodes, which not only ensures the execution integrity of the necessary step nodes, but also avoids the waste of resources caused by meaningless operations. The step-by-step navigation guide of the front-end interface is updated in real time according to the judgment results, ensuring the user's perception of process changes while maintaining the continuity of the front-end interface.

[0062] S230, displaying the progress information of each step node through a progress bar component on the front-end interface, and each step node corresponds to a progress bar component.

[0063] In some examples, this embodiment designs a progress bar component for each step node on the front-end interface, and the progress bar component is used to display the execution progress of the corresponding step node. The progress bar component can be customized using styles such as HTML and CSS, which is not limited in this embodiment. For example, in HTML, use The element creates one or more progress bar components. The outer layer of the progress bar component is #progressBar, and the inner layer is #progressBarInner. The width of this inner layer will be dynamically updated according to the progress, and the execution progress of the corresponding step node is represented by the width.

[0064] Through multiple pre-defined task functions, the total execution volume of each step node is simulated and calculated; a task function is configured for each step node; the current execution volume of the current step node is obtained through the built-in callback function of the target task function; the completion percentage of the current step node is calculated based on the total execution volume and the current execution volume, and the progress information of the current step node is obtained; the progress information is transmitted to the front-end interface so that the progress information can be dynamically displayed through the progress bar component in the front-end interface.

[0065] It can be understood that the backend predefines multiple task functions, each of which simulates the operation logic of executing each step node and then calculates the total execution amount of each step node. Among them, the execution amount of each step node can be the number of completed quantifiable sub-stages corresponding to each step node or the execution time of each step node; for example, the digital processing process of the entire document can be quantified into processing by page or by text block or by file fragment, and then each page or each text block or each file fragment is a quantifiable sub-stage. When each step node completes the processing of a page or a text block or a file fragment, it can be determined that a quantifiable sub-stage is completed.

[0066] Then, a callback function (Progress Callback) is used inside each task function to report the execution amount of each step node in real time. Each callback function will be called when the corresponding step node is executed to feedback the current execution amount of the step node (such as the current execution time of the current step node or the current completion number of quantifiable sub-stages).

[0067] Next, the backend calculates the completion percentage of the current step node based on the current execution volume and the total execution volume (such as the total execution time of the current step node or the total number of completed quantifiable sub-stages), and uses the completion percentage as the execution progress of the current step node. The execution progress and information such as the name of the current step node are then encapsulated as progress information, and the progress information is transmitted to the front-end interface through the event bus or message queue.

[0068] Then, the progress information is parsed by the front-end processor of the front-end interface to match the target progress bar component corresponding to the current step node, and the progress bar length of the target progress bar component is smoothly adjusted according to the transition animation. The length of the progress bar is used to indicate the completion percentage in the progress information. Among them, the front-end interface can use CSS or JavaScript animation to update the length of the target progress bar component. At the same time, the change of the progress bar can be made smoother through the transition animation.

[0069] As an optional implementation, if the front-end interface determines that the length of the progress bar of the current step node reaches 100%, the status of the progress bar component of the current step node is switched to "completed", and the navigation guide box for the next step node is automatically triggered and the progress bar component of the step node is activated.

[0070] In some examples, if it is determined that the current step node fails to execute, the progress bar component of the current step node is stopped, the progress bar color of the progress bar component is changed to the target color, and a progress exception prompt message is displayed.

[0071] If a rollback request is triggered under certain special conditions, if the backend receives the rollback request, it will clear the progress bar length of all progress bar components between the specified step node and the current step node, and roll back the execution of the specified step node; wherein, the rollback request is used to indicate that the current digital processing process is rolled back to the specified step node; the special conditions include failure of execution of the current step node, requirement to roll back to the specified step node for re-execution, abnormality in the execution of the current step node, etc., without specific limitation.

[0072] In the digital processing process, the execution status management and rollback mechanism of step nodes are important parts to ensure the stability and recoverability of the process.

[0073] It can be understood that in the process of processing each step node, the backend regularly sends and updates the progress information of each step node to the front-end interface, and the front-end interface monitors the progress information and updates the progress bar display result of the progress bar component in real time according to the progress information. For example, the front-end interface can monitor the progress information of the back-end by setting a progress update function. Exemplarily, the front-end interface uses the fetch function to request the progress information of each step node of the back-end. Each time the latest progress information is obtained from the back-end, the width of the progress bar component (#progressBarInner) corresponding to the corresponding step node is updated, and the progress bar component will adjust the width according to the value of totalProgress. In addition, the front-end interface can also set a loop listening function to periodically obtain the latest progress information through the progress update function; for example, the loop listening function is setTimeout (updateProgress, 1000), and the progress information is requested again every 1 second until the target step node has been determined to be completed.

[0074] That is, when the user triggers the digitization process of the paper document, the front-end interface will start the progress bar update function updateProgress(), and obtain the progress information of the back-end periodically through technologies such as AJAX. The back-end will update the progress data at each step node when a stage is completed. Each time the front-end interface requests the back-end, the latest progress information will be returned, and the progress bar component will update the width in real time according to the obtained progress information.

[0075] Furthermore, users can understand the current execution progress of each step node through the progress bar display results of each progress bar component on the front-end interface, which is convenient for users to intuitively understand and monitor the entire process of paper document digitization, and also convenient for users to timely intervene and adjust at different step node processing stages according to actual needs. In addition, when the back-end finds abnormal problems during the digitization process (such as document recognition failure, digital errors, etc.), a prompt message will be immediately popped up through the front-end interface to notify users to adjust parameters or re-upload the document image of the paper document, so that users can handle abnormal situations in real time and reduce waiting time.

[0076] In some examples, the backend can simulate the execution progress of each step node through a preset task function to obtain the progress information of each step node; and then transmit the progress information to the front-end interface to dynamically display the progress information through the progress bar component in the front-end interface.

[0077] Exemplarily, this embodiment tracks the processing time of each step node through multiple pre-defined task functions to obtain the progress information of each step node, and updates the progress information of any step node when the execution progress of any step node is monitored to be updated; wherein the task function corresponds to the step node one by one.

[0078] That is, for each step node, the backend designs a preset task function to simulate its execution progress; dynamically updates the progress percentage of each step node according to the actual processing situation to generate progress information; and then transmits this progress information to the front-end interface in real time so that users can understand the current processing status of each step node at any time.

[0079] In one embodiment, the back end transmits the updated progress information of the corresponding step node to the front end. When the front end updates the progress bar display result of the progress bar component in real time according to the updated progress information, the update process can be to use AJAX technology or WebSocket technology to asynchronously update part of the page content of the front-end interface, that is, only the progress bar of the target step node of the front-end interface is updated, avoiding the need to reload the entire page every time the front-end and back-end data interact; in addition, this embodiment can also update the entire page content of the front-end interface each time the progress bar component is updated.

[0080] As an optional implementation, the progress bar display result update process of the progress bar component of this embodiment can be that the front-end interface periodically initiates an access request to the target step node through the target API, and after the back-end receives the access request periodically initiated by the front-end interface through the target API, the back-end transmits the current progress information of the target step node to the front-end interface through the progress port until the progress information of the target step node meets a preset condition; wherein, the preset condition is that the progress information of the target step node indicates that the target step node has been completed.

[0081] It can be understood that this embodiment sets a separate progress bar component for each step node on the front-end interface, and the display result of the progress bar component can intuitively display the completion degree of each step node until the corresponding step node is completed; the display result of the progress bar component changes dynamically with the execution status of the step node, helping the user to clearly grasp the progress of the entire digital processing process; through this visualization method, not only the user experience is improved, but also it is convenient for users to promptly discover and deal with possible problems.

[0082] In one embodiment, for tasks that can be executed in parallel (such as uploading multiple files at the same time), the backend allocates an independent thread or process for the digitization processing task of each file, and the front-end interface generates an independent progress bar instance for the digitization processing task of each file, and displays the overall progress in a stacked form in the guide box (such as "File 1: 80%; File 2: 45%"); after the digitization processing tasks of each file are completed, the backend automatically cleans up temporary files and releases memory resources to save memory space.

[0083] This embodiment builds a visual operation interface for the entire process of document digitization through the collaborative design of the step-by-step navigation bar and the task progress bar. This embodiment can also map the discrete task execution process into a continuous navigation state stream, and achieve millisecond-level synchronization of the front-end and back-end states through an event-driven mechanism; this method significantly improves the user controllability and system observability of complex document processing processes, and can be extended to high-precision scenarios such as financial bill processing and medical archive digitization. In addition, this embodiment can achieve a global view of the entire document digitization process through the progress bar display on the front-end interface, so that users can directly track the current progress or backtrack steps.

[0084] S240, receiving a target document format selected by a user, and when it is determined that the digitization process is completed, outputting the content in the region of interest after digitization in the target document format.

[0085] When the digitization process of the corresponding paper document is detected to be completed, the embodiment can output the digitization result in the target document format selected by the user.

[0086] It can be understood that when the user triggers the digital processing of the target paper document through the corresponding control of the front-end interface, or during or after the processing, the user can select the output format of the digital processing result of the target paper document through the front-end interface (that is, determine in which document format to output the digital processing result); after the back-end receives the target document format selected by the user through the front-end interface, it outputs the content in the digitized area of ​​interest according to the target document format, and finally the front-end interface will display the digitized result presented in the target document format.

[0087] In some examples, a drop-down menu or similar control can be pre-designed on the front-end interface to allow users to select the document format (such as PDF, Word, Excel, etc.) to be output after digital processing; the user selects the target document format through the drop-down menu or control and submits the selection, triggering the generation of a submission event; the front-end interface uses techniques such as JavaScript to monitor the user's submission event, and then obtains the target document format selected by the user through the submission event, and transmits the target document format to the back-end, so that the back-end outputs the result of digital processing in the target document format.

[0088] As an optional implementation, if the digitization processing mode is batch processing of multiple documents or batch processing of multiple interest areas of a single document or multiple documents, this embodiment can batch read and write document images of multiple paper documents according to the digitization processing mode.

[0089] Furthermore, in order to ensure stability and improve processing efficiency during the digital processing of batch processing of multiple paper documents, this embodiment adopts a dynamic task allocation mechanism to determine how to dynamically allocate step nodes to work threads or processes based on the current system or server load and hardware resource availability.

[0090] Exemplarily, currently available hardware resources are first obtained. For example, the current load situation is monitored and evaluated through a set load monitoring and resource evaluation module, and currently available hardware resources are obtained. The load monitoring and resource evaluation module is used to dynamically evaluate the amount of hardware resources available for paper document digitization tasks. For example, under high load conditions, only part of the CPU cores and a small amount of memory may be available for new tasks, while under low load conditions, all available hardware resources can be fully utilized.

[0091] This embodiment uses a dynamic allocation strategy to allocate step nodes based on the hardware resource information provided by the load monitoring and resource evaluation module. For example, when there is hardware with multi-threading support, it is preferred to create an independent thread for each step node; if there is a hardware environment with multiple processes available, different processes can be created for different paper documents or larger step nodes. For simple step nodes, fewer hardware resources (such as a single CPU core and a small amount of memory) can be allocated, while for complex step nodes (such as OCR tasks involving a large amount of image processing), more hardware resources (such as multiple CPU cores and larger memory) are allocated. In addition, as the load changes, the hardware resources that have been allocated to each step node can be dynamically adjusted. For example, when a step node is about to be completed, its released hardware resources are reallocated to other step nodes waiting to be executed.

[0092] In one example, if multiple threads process multiple step nodes in parallel, multiple threads are created in the same process to process different step nodes of paper document digitization in parallel. For example, in one process, multiple threads are started at the same time to perform image scanning of multiple paper documents or OCR of different pages of the same paper document. Since threads share the memory space of the process, this helps to reduce memory overhead, but synchronization and communication mechanisms between threads (such as using locks, semaphores, etc.) need to be ensured to avoid data conflicts.

[0093] In another example, if multiple processes process multiple step nodes in parallel, multiple processes can be created for different paper document digitization tasks or larger-scale step nodes (such as processing the digitization of very large paper documents). Each process has its own independent memory space, which can better isolate resource competition between tasks. Multiple processes can interact with each other through inter-process communication (IPC) mechanisms (such as pipes, message queues, etc.), such as passing information such as the digitized file path.

[0094] Furthermore, this embodiment can dynamically allocate processing tasks according to the current processing load and available hardware resources (such as CPU, GPU, memory, etc.) through the above-mentioned dynamic task allocation mechanism, and can process different tasks at the same time without blocking each other. In addition, load balancing is also used to ensure optimal processing efficiency and avoid delayed processing of certain step nodes due to insufficient resources. That is, this embodiment dynamically allocates tasks according to the current processing load and available hardware resources, thereby realizing multi-threaded or multi-process parallel processing of paper document digitization. This method not only improves processing efficiency, but also ensures the stability and reliability of the system.

[0095] In one example, this embodiment also involves the generation of an execution report for a step node, wherein the execution report is used to display the execution status of the corresponding step node; that is, this embodiment can display the execution profile of each step node by generating an execution report for each step node, thereby facilitating user management and analysis of the entire digital processing process.

[0096] For example, Figure 4 As shown, the method also includes the following steps: S250, receiving the report generation parameter items selected by the user, and assembling the execution report according to the report generation parameter items and the execution process and execution result of each step node.

[0097] S260, output execution reports through the front-end interface.

[0098] It should be noted that the execution order of S250~S260 can be before S240 or after S240 or synchronously with S240, that is, the execution order of the above steps is not limited and can be set accordingly according to actual needs.

[0099] In this embodiment, similar to the aforementioned process of outputting the results after digital processing, the user can select the output method of the execution report through the front-end interface (i.e., determine in which form the execution report is output, which contents of the execution report need to be output, etc.).

[0100] Exemplarily, the user triggers the generation and output of the execution report through the corresponding controls or forms of the front-end interface, and the user inputs report generation parameter items such as the report content to be output and the report generation format through the corresponding controls or forms of the front-end interface; in this process, after the back-end receives the report generation parameter items selected by the user through the front-end interface, it assembles the corresponding execution report according to the report generation parameter items and the execution process and execution results of each step node; wherein, the report generation parameter items include but are not limited to the report generation format, the level of detail and the report content to be generated, the report generation format is not limited to PDF, Word, Excel, CSV, etc., the level of detail can be divided into simple, detailed, ordinary, etc. (the back-end can be pre-configured with multiple report templates, different report templates correspond to different levels of detail, and the back-end can directly call the report template to generate a report with a corresponding level of detail according to the needs), and the report content to be generated includes but is not limited to the start execution time, completion time, etc.; the report generation parameter items can be specifically set according to actual needs, and this embodiment does not limit this.

[0101] In one example, the backend can obtain the report generation parameter item from the frontend interface by means of HTTP request, and then extract the corresponding data from the execution process of the target step node according to the report generation parameter item to generate the execution report of the target step node. In this process, the backend can fill the extracted target data into the predefined template by using an appropriate template engine or report tool (such as JasperReports, Crystal Reports, Jinja2, Mustache, etc.) to generate the execution report and provide a download link for the execution report.

[0102] In one embodiment, before the execution report is output on the front-end interface, the user can preview the report to be output through the front-end interface, that is, the front-end interface displays the execution report style to be output through the preview box, so that the user can preview and confirm the execution report to be output; if the user's report change information is received, the corresponding execution report is modified according to the report change information until the user's confirmation output information of the execution report to be output is received; if the user's confirmation output information of the execution report to be output is received, the execution report is output through the front-end interface according to the confirmation output information.

[0103] It can be understood that, in this embodiment, the execution report can be previewed and adjusted before outputting the execution report, so as to timely modify error information in the execution report or adjust the final generated result of the execution report to generate an execution report that meets the requirements.

[0104] As an optional implementation, during the process of outputting an execution report, or after outputting an execution report, this embodiment also allows the user to select report display parameter items from the generated report content. In other words, the report data corresponding to the report display parameter items is filtered out from the execution report, and then the report data is displayed through the front-end interface.

[0105] For example, the user inputs the report display parameter item through the corresponding control or form or text input box of the front-end interface, the back-end receives the report display parameter item selected by the user, filters the report data that meets the report display parameter item from the generated report content, and directly displays the report data through the front-end interface. That is, this embodiment can filter the data of several parameter items from the multiple parameter items in the actually generated report for display, and in the case of too many report parameter items, it can avoid displaying too much content and causing the entire report display page to be too complicated.

[0106] As a feasible implementation method, this embodiment can also integrate simple statistical functions. For example, the back end can generate relevant statistical charts based on the character recognition results, such as recognition success rate, character error rate, etc., and then export these charts through the front-end interface to facilitate subsequent analysis or tracing.

[0107] In one embodiment, the back end can also synchronously store the digitized content within the area of ​​interest in the form of electronic documents and execution reports on local and cloud servers; then, when receiving access requests from different user-end devices, the target electronic documents and / or target execution reports are searched and output from the local or cloud server according to the access requests.

[0108] That is, this embodiment supports synchronization of cloud and local storage, and users can access corresponding electronic documents and execution reports through the same front-end interface on different devices at any time without worrying about data loss or version inconsistency.

[0109] In addition, when the backend outputs execution reports or the content within the area of ​​interest after digital processing, it can also provide multilingual translation functions. That is, when the front end outputs the digital processing results in the target document format and the corresponding execution reports, users can select different language versions according to their needs, which is convenient for users from different regions or language backgrounds to use and improve the user experience.

[0110] In one embodiment, Figure 5 As shown, the present embodiment can also provide a log management function, that is, a corresponding log is generated according to the digitization process of each document, and the logs corresponding to each document can be associated and displayed through the log management window in the front-end interface, such as the time used in the digitization process of each document, the recorded time of the digitization processing of each document, and the operation of the log (such as deletion, etc.); the user can choose whether to delete the log record or perform other operations on the log record through the delete and other button components in the operation column.

[0111] It can be understood that this embodiment guides user operations and triggers background task execution through the front-end step-by-step navigation guide box, while tracking task progress in real time and feeding back to the user through visual components, and combining structured interface design, step node status synchronization mechanism and progress bar dynamic update mechanism to achieve precise control and transparent management of complex processes. At the same time, the user operation guidance, step node execution monitoring and visual feedback of the whole process execution progress are seamlessly connected, which significantly reduces the operation threshold of complex processes, and improves system reliability and user trust, so that this embodiment can be extended to fields such as intelligent manufacturing and financial transactions that require strict process control and real-time status tracking.

[0112] Please refer to Figure 6 The embodiment of the present application further provides a document digital management device, which can be referred to as: The content selection module 410 is used to display the document image of the paper document to be processed through the front-end interface, receive the content in the interest area selected by the user in the document image, and perform digital processing on the content in the interest area; The digitization module 420 is used to push the operation description of each step node in the digitization process in sequence in a step-by-step navigation manner through the front-end interface, and trigger the execution of corresponding operation logic after receiving user feedback based on the operation description; A progress monitoring module 430, used to display the progress information of each step node through a progress bar component on the front-end interface, and each step node corresponds to a progress bar component; The output module 440 is used to receive the target document format selected by the user, and when it is determined that the digitization process is completed, output the digitized content in the interest region in the target document format.

[0113] It can be understood that the device of this embodiment corresponds to the document digitization management method of the above embodiment, and the options in the above embodiment are also applicable to this embodiment, so they will not be described repeatedly here.

[0114] The present application also provides a computer device. Exemplarily, the computer device includes a processor and a memory, wherein the memory stores a computer program, and the processor runs the computer program to enable the computer device to execute the functions of each module in the above-mentioned document digitization management method or the above-mentioned document digitization management device.

[0115] Among them, the processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including a central processing unit (CPU), a graphics processing unit (GPU), a network processor (NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or at least one of other programmable logic devices, discrete gates or transistor logic devices, and discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc., which can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.

[0116] The memory may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electric erasable programmable read-only memory (EEPROM), etc. The memory is used to store a computer program, and the processor may execute the computer program accordingly after receiving an execution instruction.

[0117] The present application also provides a computer storage medium for storing the computer program used in the above-mentioned computer device. The computer storage medium may be a readable storage medium, or a non-volatile storage medium or a volatile storage medium. For example, the computer storage medium may include but is not limited to: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0118] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or the flow diagram, and the combination of boxes in the structure diagram and / or the flow diagram, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0119] In addition, the functional modules or units in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0120] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.

[0121] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A document digital management method, characterized in that: include: Displaying a document image of a paper document to be processed through a front-end interface, receiving content in a region of interest selected by a user in the document image, and digitally processing the content in the region of interest; Pushing the operation description of each step node in the digital processing process in sequence in a step-by-step navigation manner through the front-end interface, and triggering the execution of corresponding operation logic after receiving user feedback based on the operation description; Displaying progress information of each step node on the front-end interface through a progress bar component, each step node corresponds to a progress bar component; The target document format selected by the user is received, and when it is determined that the digitization process is completed, the digitized content in the region of interest is output in the target document format.

2. The document digital management method according to claim 1, characterized in that: Displaying the progress information of each step node through a progress bar component on the front-end interface includes: Through a plurality of predefined task functions, the total execution amount of each step node is simulated and calculated; each step node is configured with a task function; Get the current execution amount of the current step node through the built-in callback function of the target task function; Calculate the completion percentage of the current step node according to the total execution amount and the current execution amount, and obtain the progress information of the current step node; The progress information is transmitted to the front-end interface so as to dynamically display the progress information through a progress bar component in the front-end interface.

3. The document digital management method according to claim 2, characterized in that: The dynamically displaying the progress information through a progress bar component in the front-end interface includes: Parsing the progress information through a front-end processor of the front-end interface to match a target progress bar component, and smoothly adjusting the progress bar length of the target progress bar component in a transition animation manner, wherein the progress bar length is used to indicate the completion percentage; If it is determined that the execution of the current step node fails, the progress bar component of the current step node is stopped, the progress bar color of the progress bar component is changed to the target color, and a progress abnormality prompt message is displayed; If a rollback request is received, the progress bar lengths of all progress bar components between the specified step node and the current step node are cleared, and the specified step node is rolled back; the rollback request is used to instruct the current digital processing process to roll back to the specified step node.

4. The document digital management method according to claim 2, characterized in that: The current execution amount of each step node is the current completion quantity of a number of quantifiable sub-stages divided corresponding to each step node or the current execution duration of each step node.

5. The document digital management method according to claim 1, characterized in that: The operation description of each step node in the digital processing process is pushed in sequence through the front-end interface in a step-by-step navigation manner, and after receiving user feedback based on the operation description, the corresponding operation logic is triggered to execute, including: At least one navigation guide box is pre-set for each step node in the front-end interface, and a click event listener is bound to the operation component in each navigation guide box, so as to listen to the click event triggered by the operation component according to the click event listener; each navigation guide box is arranged according to a predetermined layout rule, and each navigation guide box contains the step name, operation description and operation component of the target step node; the click event is used to represent the user's feedback based on the operation description; Display the navigation guide box corresponding to the current step node in a step-by-step navigation manner; Update the state attribute of the current navigation guide frame according to the monitored click event, and trigger the execution of the operation logic corresponding to the click event; If it is determined that the operation logic execution fails, then redisplaying the navigation guide frame corresponding to the current step node or displaying the first target guide frame; If it is determined that the operation logic has been completed, the next navigation guide box is displayed in a step-by-step navigation manner.

6. The document digital management method according to claim 5, characterized in that: Before the triggering and executing the operation logic corresponding to the click event, the method further includes: Performing a validity check on the click event and determining whether the user has completed the necessary operations indicated in the navigation guide box; If the legality check fails and / or the necessary operation is not completed, then the navigation guide frame corresponding to the current step node is redisplayed or the second target guide frame is displayed; If the legality check passes and the necessary operations are completed, the operation logic corresponding to the click event is triggered and executed.

7. The document digital management method according to claim 1, characterized in that: The method further comprises: Receive the report generation parameter items selected by the user, and assemble an execution report according to the execution process and execution result of each step node according to the report generation parameter items, wherein the execution report is used to display the execution status of the corresponding step node; the report generation parameter items include the report generation format, the level of detail, and the report content to be generated; Outputting the execution report through the front-end interface; Before outputting the execution report through the front-end interface, the method further includes: Previewing the execution report to be output through the front-end interface, so that the user can preview and confirm the execution report to be output; If the report change information of the user is received, the corresponding execution report is modified according to the report change information; If confirmation output information of the user confirming to output the execution report to be output is received, the execution report is output through the front-end interface according to the confirmation output information; After outputting the execution report through the front-end interface, the method further includes: A report display parameter item selected by a user is received, report data corresponding to the report display parameter item is filtered out from the execution report, and the report data is displayed through the front-end interface.

8. A document digital management device, characterized in that: include: A content selection module is used to display a document image of a paper document to be processed through a front-end interface, receive content in an area of ​​interest selected by a user in the document image, and perform digital processing on the content in the area of ​​interest; A digitization module, used to push the operation description of each step node in the digitization process in sequence in a step-by-step navigation manner through the front-end interface, and trigger the execution of corresponding operation logic after receiving user feedback based on the operation description; A progress monitoring module, used to display the progress information of each step node on the front-end interface through a progress bar component, each step node corresponds to a progress bar component; The output module is used to receive the target document format selected by the user, and when it is determined that the digitization process is completed, output the content in the interest area after digitization in the target document format.

9. A computer device, characterized in that: The computer device comprises a processor and a memory, wherein the memory stores a computer program, and the processor is used to execute the computer program to implement the document digitization management method according to any one of claims 1 to 7.

10. A computer storage medium, characterized in that: It stores a computer program, which, when executed on a processor, implements the document digitization management method according to any one of claims 1 to 7.

Images