Information processing system, data management device, data management method and program

Abstract

To reduce operational burden for accessing an execution result of processing data.SOLUTION: In an information processing system including a data management apparatus and a data processing apparatus, the data management apparatus includes: a storage processing unit for storing data transmitted from any one of one or more terminals in a first storage unit; a transmission unit for transmitting data stored in the first storage unit to the data processing apparatus; and a first acquisition unit for acquiring, from the data processing apparatus, first identification information for accessing a result of processing the data by the data processing apparatus from outside of the data processing apparatus, and for controlling storage of the first identification information in a second storage unit that stores information to be transmitted to any one of the one or more terminals.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an information processing system, a data management device, a data management method, and a program. [Background technology]

[0002] 2. Description of the Related Art Document management systems are known that manage documents created in business as electronic data.

[0003] Also known is a system that performs processing such as OCR (Optical Character Recognition) on electronic documents (for example, Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional technologies, when a user wants a document processing system to process a document managed by a document management system, the user must perform complex operations. For example, the user must download the document from the document management system, upload the document to the document processing system, and then manually input instructions to process the document. The user must then input some kind of operational instruction to the document processing system to access the results of the processing.

[0005] The present invention has been made in view of the above points, and an object of the present invention is to reduce the operational burden of accessing the results of execution of processing on data. [Means for solving the problem]

[0006] In order to solve the above problem, in an information processing system including a data management device and a data processing device, the data management device includes a storage processing unit that stores document data and a data type of the document data transmitted from any one of one or more terminals in a first storage unit, an identification unit that identifies workflow information of a workflow to be applied to a target document from one or more workflows stored in a workflow information storage unit based on the type of the document data, a first transmission unit that transmits the document data stored in the first storage unit to the data processing device as one process constituting a workflow related to the workflow information identified by the identification unit, a first acquisition unit that acquires first identification information from the data processing device indicating an acquisition destination of a result of processing the document data by the data processing device, making the result of the processing on the document data by the data processing device accessible from outside the data processing device, and saves the first identification information in a second storage unit that stores information to be transmitted to any one of the one or more terminals, and a second transmission unit that transmits metadata including the first identification information to any one of the one or more terminals. a notification unit that notifies one of the one or more terminals of a task assignment for the document data transmitted from one of the one or more terminals and stored in the first storage unit, wherein the first acquisition unit acquires the first identification information corresponding to the second identification information for the document data from the data processing device after receiving an inspection result indicating that there is no problem with the document data related to the task from the one or more terminals that notified the assignment to the task. . [Effects of the Invention]

[0007] The operational burden of accessing the results of processing data can be reduced. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of a configuration of an information processing system 1 according to a first embodiment. [Figure 2] 1 is a diagram illustrating an example of a hardware configuration of a document management device 10 according to a first embodiment. [Figure 3] 1 is a diagram illustrating an example of a functional configuration of a document management apparatus 10 and a document processing apparatus 20 according to a first embodiment. [Figure 4] FIG. 2 is a sequence diagram illustrating an example of a processing procedure executed by the information processing system 1 according to the first embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of the configuration of an upload screen. [Figure 6] FIG. 10 is a diagram showing the state of the target metadata at the end of step S106 in the first embodiment. [Figure 7] FIG. 4 is a diagram illustrating an example of workflow information applied in the first embodiment. [Figure 8] FIG. 10 is a diagram illustrating a display example of a task list screen. [Figure 9] FIG. 10 is a diagram showing the state of the target metadata at the end of step S113 in the first embodiment. [Figure 10] FIG. 10 is a diagram showing a display example of a metadata confirmation screen. [Figure 11] FIG. 10 is a diagram showing a display example of an accounting processing screen. [Figure 12] FIG. 10 is a diagram showing the state of the target metadata at the end of step S121 in the first embodiment. [Figure 13] FIG. 10 is a sequence diagram illustrating an example of a processing procedure executed by the information processing system 1 according to the second embodiment. [Figure 14] FIG. 11 is a diagram showing the state of the target metadata at the end of step S113a in the second embodiment. [Figure 15] FIG. 11 is a diagram showing the state of the target metadata at the end of step S121 in the second embodiment. [Figure 16] FIG. 10 is a diagram illustrating an example of the functional configuration of a document management apparatus 10 and a document processing apparatus 20 according to a third embodiment. [Figure 17] FIG. 11 is a sequence diagram illustrating an example of a processing procedure executed by the information processing system 1 according to the third embodiment. [Figure 18] FIG. 13 is a diagram illustrating an example of workflow information applied in the third embodiment. [Figure 19] FIG. 13 is a diagram showing the state of the target metadata at the end of step S113b in the third embodiment. [Figure 20]FIG. 13 is a diagram showing the state of the target metadata at the end of step S206 in the third embodiment. [Figure 21] FIG. 13 is a sequence diagram illustrating an example of a processing procedure executed by the information processing system 1 according to the fourth embodiment. [Figure 22] FIG. 13 is a diagram illustrating an example of workflow information applied in the fourth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Fig. 1 is a diagram showing an example of the configuration of an information processing system 1 in a first embodiment. In Fig. 1, the information processing system 1 includes one or more user terminals 30, a document management device 10, and a document processing device 20. Each user terminal 30 is connected to the document management device 10 and the document processing device 20 via a network such as a LAN (Local Area Network) or the Internet.

[0010] The document management device 10 is one or more computers that electronically store (store) documents. A document is a concept corresponding to a written document. Documents are managed in a virtual space, for example, as document files and metadata. A document file is data representing the document itself (hereinafter referred to as a "document file"). Examples of document files include files that store image data obtained by scanning a paper document and files that store data electronically created by a document creation application. Metadata is data containing information related to a document. Examples of metadata include bibliographic information about the document and the contents of the document file. By managing metadata for each document, the management system enables efficient searches using metadata as a search key. The management system also has a workflow function and outputs work instructions related to a certain document to one or more users in the order defined in the workflow. In this embodiment, an invoice is an example of a document.

[0011] The document processing device 20 is one or more computers that perform predetermined processing on documents. The processing performed by the document processing device 20 may vary depending on the type of document. For example, if the document is an invoice, the document processing device 20 performs OCR (Optical Character Recognition) processing (analysis of the document's data structure) and accounting processing for inputting the document into accounting software. Note that some or all of the one or more computers that make up the document processing device 20 may be the same as the one or more computers that make up the document management device 10.

[0012] The user terminal 30 is a terminal such as a PC (Personal Computer), a smartphone, or a tablet terminal used by users of the document management device 10 and the document processing device 20. The user terminal 30 provides the user with a user interface for each of the document management device 10 and the document processing device 20. In this embodiment, the users are four people: a sales representative, a sales approver, an accounting representative, and an accounting approver. Each of these four people may use a different user terminal 30, or two or more users may use the same user terminal 30.

[0013] The sales representative is, for example, a specific individual who is a person in charge of the sales department. When the sales representative receives an invoice, the sales representative uploads (registers) the document file of the invoice to the document management device 10.

[0014] The sales approver is, for example, a specific individual who is the superior of a sales representative in a sales department. The sales approver reviews the content of the document file uploaded by the sales representative (i.e., the content of the invoice).

[0015] An accounting staff member is, for example, a specific individual who is in charge of the accounting department. The accounting staff member performs the necessary work in the accounting department (hereinafter referred to as "accounting work") for invoices approved by the sales approver. For example, the accounting staff member inputs the contents of the invoice and inputs the required slips. Note that the accounting work does not depend on the document management device 10. On the other hand, in the accounting work, the document processing device 20 is used to assist in inputting the contents of the invoice. Specifically, the document processing device 20 generates text data indicating the contents of the invoice by performing OCR processing or the like on the document file of the invoice. Therefore, the accounting staff member does not need to manually input all of the contents of the invoice, and the burden of the accounting work can be reduced by correcting any OCR misrecognitions in the text data.

[0016] The accounting approver is, for example, a specific individual who is the supervisor of the accounting staff in the accounting department. The accounting approver reviews the results of accounting work.

[0017] The four people mentioned above do not necessarily have to be different people.

[0018] Fig. 2 is a diagram showing an example of the hardware configuration of a document management device 10 according to the first embodiment. The document management device 10 in Fig. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, and an interface device 105, which are all interconnected via a bus B.

[0019] A program that realizes processing in the document management device 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, the program does not necessarily have to be installed from the recording medium 101, but may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program as well as necessary files, data, etc.

[0020] When an instruction to start a program is received, the memory device 103 reads the program from the auxiliary storage device 102 and stores it. The CPU 104 executes functions related to the document management device 10 in accordance with the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.

[0021] The document processing device 20 and the user terminal 30 may also have the hardware configuration shown in FIG.

[0022] 3 is a diagram showing an example of the functional configuration of the document management device 10 and the document processing device 20 according to the first embodiment. In FIG. 3, the document management device 10 has a UI unit 11, a document management unit 12, and a workflow control unit 13. Each of these units is realized by a process executed by a CPU 104 of one or more programs installed in the document management device 10. The document management device 10 also uses a document storage unit 14, a metadata storage unit 15, and a workflow information storage unit 16. Each of these storage units can be realized using, for example, an auxiliary storage device 102, or a storage device connectable to the document management device 10 via a network.

[0023] The document storage unit 14 is a database that stores document files. The metadata storage unit 15 is a database that stores document metadata. The workflow information storage unit 16 is a database that stores one or more pieces of workflow information. Workflow information refers to information that indicates the definition of a workflow.

[0024] The UI unit 11 provides a user interface (screen) related to the document management device 10 to the user terminal 30.

[0025] The document management unit 12 manages document files uploaded from the user terminal 30 and metadata of documents related to the document files. The document management unit 12 stores the document files in the document storage unit 14 and stores the metadata in the metadata. The document management unit 12 associates document files and metadata related to the same document.

[0026] The workflow control unit 13 controls processing of documents managed by the document management unit 12 in accordance with a workflow pre-stored in the workflow information storage unit 16. In controlling the workflow, the workflow control unit 13 controls tasks constituting the workflow and performs communication with an external system (in this embodiment, the document processing device 20). In FIG. 3, the workflow control unit 13 includes a workflow information acquisition unit 131, a target flow information identification unit 132, a transition detection unit 133, an assignment unit 134, an upload unit 135, a processing result identifier acquisition unit 136, and a processing result acquisition unit 137.

[0027] The workflow information acquisition unit 131 acquires all workflow information stored in the workflow information storage unit 16. The workflow information includes a start trigger and definitions of one or more tasks in the order of execution. Workflow information including two or more tasks also includes a transition condition from an earlier task in the order of execution to a later task in the order of execution. The start trigger is information indicating the start condition of the workflow indicated by the workflow information.

[0028] The target flow information identifying unit 132 identifies, from among one or more pieces of workflow information acquired by the workflow information acquiring unit 131, a workflow related to the workflow information whose start trigger is satisfied, as a target to be executed.

[0029] The transition detection unit 133 detects whether a transition condition is satisfied for a workflow to be executed.

[0030] When the execution target transitions to a task related to the assignment of work to any user (in this embodiment, the sales representative, sales approver, accounting representative, or accounting approver), the assignment unit 134 executes processing for the assignment.

[0031] When the execution target shifts to a task of uploading a document file to the document processing device 20, the upload unit 135 executes the upload.

[0032] The processing result identifier acquisition unit 136 acquires, from the document processing device 20, a processing result identifier indicating the source of the processing result by the document processing device 20 for the document file uploaded by the upload unit 135.

[0033] The processing result acquisition unit 137 acquires from the document processing device 20 the processing result of the document file uploaded by the upload unit 135 by the document processing device 20 .

[0034] The document processing device 20 includes a UI unit 21 and a document processing unit 22. These units are realized by processing that is executed by the CPU of the document processing device 20 by one or more programs installed in the document processing device 20.

[0035] The UI unit 21 provides a user interface (screen) related to the document processing device 20 to the user terminal 30.

[0036] The document processing unit 22 performs predetermined processing on the document uploaded to the document processing device 20. For example, the document processing unit 22 performs OCR (Optical Character Recognition) processing on the document.

[0037] The following describes the processing procedure executed by the information processing system 1. Fig. 4 is a sequence diagram for explaining an example of the processing procedure executed by the information processing system 1 in the first embodiment.

[0038] Before step S102 and subsequent steps are executed, the workflow information acquisition unit 131 of the workflow control unit 13 acquires workflow information from the workflow information storage unit 16 (S101-1, S101-2). The target flow information identification unit 132 of the workflow control unit 13 monitors whether the start trigger is satisfied for each piece of acquired workflow information.

[0039] Thereafter, when the sales representative receives the invoice (S102), the user terminal 30 used by the sales representative uploads (transmits) the document file of the invoice (hereinafter referred to as the "target document file") to the document management device 10 in accordance with the sales representative's instructions (S103). Note that the sales representative's instructions are input, for example, via an upload screen provided by the UI unit 11.

[0040] Fig. 5 is a diagram showing an example of the configuration of an upload screen. As shown in Fig. 5, the upload screen 510 can accept input of the file name of a document to be uploaded and the type (document type) of the document (hereinafter referred to as the "target document"). The user terminal 30 used by the sales representative transmits to the document management device 10 the target document file associated with the file name input on the upload screen 510 and a character string indicating the document type input on the upload screen 510 (hereinafter, the character string will be simply referred to as the "document type").

[0041] The document type is information indicating the category to which the target document belongs when a group of documents is classified based on the content of the document, such as estimates, invoices, etc. The document type of an invoice is "invoice." In this embodiment, the document type is used to identify the workflow to be executed for the document. Therefore, for example, if the information processing system 1 is a system dedicated to invoices and the same workflow is executed for all documents, input of the document type may not be necessary.

[0042] When the UI unit 11 receives the uploaded target document file and document type (hereinafter referred to as "target type"), it requests the document management unit 12 to save the target document file and target type (S104). The document management unit 12 assigns a new document ID (hereinafter referred to as "target document ID") to the target document file, and saves the target document file in the document storage unit 14 in association with the target document ID (S105). Next, the document management unit 12 saves metadata (hereinafter referred to as "target metadata") associated with the target document ID and target type in the metadata storage unit 15 (S106).

[0043] 6 is a diagram showing the state of the target metadata at the end of step S106 in the first embodiment. As shown in FIG. 6, in the first embodiment, the target metadata includes items such as a document ID, a document type, a date, an amount, and a processing result identifier. At the end of step S106, new metadata including the document ID and the document type among these items is stored in the metadata storage unit 15.

[0044] Next, the document management unit 12 notifies the workflow control unit 13 of the saving of the new document (S108). At this time, the document management unit 12 notifies the workflow control unit 13 of the target document ID and target type. The target flow information identification unit 132 of the workflow control unit 13 identifies workflow information to be applied to the target document from one or more pieces of workflow information stored in the workflow information storage unit 16, based on the target type notified by the document management unit 12.

[0045] Fig. 7 is a diagram showing an example of workflow information applied in the first embodiment. Fig. 7 includes, from the top row, a start trigger, one or more tasks, one or more transition conditions, and an end condition.

[0046] The start trigger "Save document (invoice)" in Figure 7 indicates that a document whose document type is an invoice has been saved. In step S108, notification is given of the document being saved and the target type ("invoice"). Therefore, the workflow information shown in Figure 7 is the target of application here. Note that the start trigger is not limited to saving a document. For example, the arrival of a specific time or various other events may also be set as the start trigger.

[0047] Tasks are processes that make up a workflow. In Figure 7, tasks on the top row have the highest priority in the execution order.

[0048] A transition condition is a condition that must be satisfied in order to transition from the task immediately preceding the transition condition to the task immediately following the transition condition. The workflow information in Figure 7 includes five tasks, Task 1 to Task 5, and therefore includes four transition conditions.

[0049] An exit condition is a condition that must be met to terminate the workflow.

[0050] In this embodiment, the configuration of the workflow information is simplified for the sake of convenience, but the workflow information shown in FIG. 7 will be hereinafter referred to as "target flow information."

[0051] Because the start trigger of the target flow information has been satisfied, the assignment unit 134 of the workflow control unit 13 notifies the sales approver of the assignment of Task 1 ("Review by Sales Approver") to the target document based on the definition of Task 1 ("Review by Sales Approver") in the target flow information (FIG. 7) (S108). In FIG. 7, the definition of Task 1 is expressed abstractly as "Review by Sales Approver," but in reality it is computer-understandable information that includes identification information of the "Sales Approver" as the task executor and identification information of "Review" as the task content. This also applies to the definitions of other items in the workflow information.

[0052] The sales approver may be notified of the assignment of task 1 by sending an email to the email address corresponding to the sales approver. Alternatively, the assignment unit 134 may notify the sales approver of the assignment in response to the sales approver logging in to the document management device 10. The same method of notifying other users of the assignment applies. Each time the assignment unit 134 assigns a task, it associates the target document ID with the user ID of the assigned user and stores information indicating the assigned task in the auxiliary storage device 102 or the like. This allows the assignment unit 134 to grasp which task for which document is assigned to each user. Each time the assignment unit 134 assigns a task, it associates the target document ID with the target document ID and stores information indicating the assigned task for the target document (information indicating which task in which workflow information the task belongs) in the auxiliary storage device 102 or the like. This allows the assignment unit 134 to grasp which task in which workflow has been executed for each document.

[0053] The user terminal 30 used by the sales approver who has been notified of the assignment of task 1 displays a task list screen in response to an operation by the sales approver. For example, the user terminal 30 may display the task list screen in response to the sales approver logging in to the document management device 10 or performing a predetermined operation after logging in. Alternatively, the user terminal 30 may display the task list screen in response to selection of a URL (a URL corresponding to the assigned task) included in an email notifying the task assignment. In either case, the task list screen is displayed with the user to whom it is to be displayed (hereinafter referred to as the "target user") specified. The target user here is the sales approver.

[0054] 8 is a diagram showing a display example of a task list screen 520. As shown in FIG. 8, a task list screen 520 includes a task list area 521, a preview area 522, a metadata confirmation button 523, a complete button 524, and a reject button 525.

[0055] The task list area 521 is an area showing a list of tasks assigned to the target user. For example, when generating the task list screen 520, the UI unit 11 acquires a list of tasks assigned to the target user and includes the list in the task list area 521. Each task in the task list area 521 is associated with the document ID of the document to which the task is applied.

[0056] The preview area 522 is an area that displays a document file related to a task selected in the task list area 521. For example, when a task is selected in the task list area 521, the user terminal 30 transmits a document ID associated with the task to the document management unit 12. The document management unit 12 acquires a document file corresponding to the document ID from the document storage unit 14. The document management unit 12 transmits the document file to the user terminal 30. The user terminal 30 displays the document file in the preview area 522.

[0057] The procedure for displaying the task list screen 520 is the same for other users (accounting staff, accounting approvers).

[0058] The sales approver selects a task corresponding to the target document in the task list area 521 of the task list screen 520. As a result, the target document file is displayed in the preview area 522. The sales approver reviews the target document by referring to the target document file (i.e., the invoice) displayed in the preview area 522. If the review results show that there are no problems, the sales approver selects the complete button 524, and if there are problems, the sales approver selects the reject button 525. The user terminal 30 transmits the review result ("complete" or "reject") corresponding to the selected button and the target document ID to the document management device 10 (S109).

[0059] Upon receiving the review result and the target document ID, the UI unit 11 of the document management device 10 notifies the workflow control unit 13 of the review result and the target document ID (S110). If the review result notified from the UI unit 11 is "Completed," the transition detection unit 133 of the workflow control unit 13 detects that the transition condition ("Completed") from Task 1 to Task 2 has been satisfied based on the target flow information (FIG. 7) related to the target document ID. Then, the upload unit 135 of the workflow control unit 13 acquires the target document file via the document management unit 12 based on the definition of Task 2 ("Upload to the document processing device 20") in the target flow information. Next, the upload unit 135 uploads (transmits) the target document file to the document processing unit 22 of the document processing device 20 (S111-1). If the review result is "Rejected," the transition condition from Task 1 to Task 2 is not satisfied, and therefore step S111-1 is not executed. The same applies to other transition conditions, in that the transition destination task is not executed if the transition condition is not satisfied.

[0060] When the document processing unit 22 of the document processing device 20 receives the target document file, it performs a predetermined process on the target document file. In this embodiment, the document processing unit 22 performs a text data extraction (generation) process, such as OCR processing, on the uploaded document file. That is, the document processing unit 22 generates text data containing the contents of the target document file. The target document file does not have to be image data. For example, the target document file may be data in a format dependent on a specific application. In this case, the document processing unit 22 converts data in that format into text data to generate text data containing the contents of the target document file. The document processing unit 22 generates identification information (hereinafter referred to as a "processing result identifier") to enable external access to the text data resulting from the predetermined process (OCR processing). The document processing unit 22 stores the processing result (text data) and the target document file (i.e., data to be processed) in association with the processing result identifier (hereinafter referred to as a "target processing result identifier"). The processing result identifier is, for example, a URL (Uniform Resource Locator). In other words, the processing result identifier can be said to be identification information for disclosing on the network the processing result by the document processing unit 22. Next, the document processing unit 22 transmits a response including the target processing result identifier to the workflow control unit 13 (S111-2).

[0061] When the processing result identifier acquisition unit 136 of the workflow control unit 13 receives (acquires) the target processing result identifier, it controls the storage of the target processing result identifier in the metadata storage unit 15 for the target document as a series of processes for task 2. Specifically, the processing result identifier acquisition unit 136 specifies the target document ID and requests the document management unit 12 to set the target processing result identifier in the target metadata (save the target processing result identifier as metadata) (S112).

[0062] In response to a request from the processing result identifier acquisition unit 136, the document management unit 12 sets a target processing result identifier for the target metadata corresponding to the target document ID specified in the request from among the metadata stored in the metadata storage unit 15 (S113).

[0063] 9 is a diagram showing the state of the target metadata at the end of step S113 in the first embodiment. As shown in Fig. 9, at the end of step S113, the target metadata includes a URL as a processing result identifier.

[0064] Next, the document management unit 12 notifies the workflow control unit 13 of the completion of setting the target process result identifier (S114). Such notification includes the target document ID.

[0065] Based on the notification of the setting completion, the transition detection unit 133 of the workflow control unit 13 detects that the transition condition from Task 2 to Task 3 ("Setting Completed") has been satisfied in the target flow information (FIG. 7) related to the target document ID. Then, the assignment unit 134 notifies the accountant of the assignment of Task 3 ("Accounting Work by Accountant") to the target document based on the definition of Task 3 ("Accounting Work by Accountant") in the target flow information (S115). The user terminal 30 used by the accountant who has been notified of the assignment of Task 3 displays the task list screen 520 (FIG. 8) in response to an operation by the accountant.

[0066] Here, what the accountant wants to do in task 3 ("accounting work by accountant") is accounting work related to the target document. The accounting work involves inputting the contents of the target document (invoice), etc., and these contents are stored in the document processing device 20 as the processing results by the document processing device 20. Therefore, if the processing results can be obtained, the accounting work can be made more efficient. However, in order for the accountant to obtain the processing results, the accountant needs to know where to obtain the processing results. Therefore, the accountant selects the metadata confirmation button 523 on the task list screen 520. The user terminal 30 used by the accountant displays a metadata confirmation screen in response to the selection of the metadata confirmation button 523.

[0067] 10 is a diagram showing an example of a metadata confirmation screen. As shown in FIG. 10, the metadata confirmation screen 530 is a screen that displays the target metadata. At this point, the target metadata is as shown in FIG. 9, so the values for the date and amount are blank. However, the information that the accounting staff needs at this point is the processing result identifier that indicates the source from which the processing result by the document processing device 20 is obtained. Therefore, the accounting staff can access the processing result using the URL that serves as the processing result identifier.

[0068] The metadata displayed on the metadata confirmation screen 530 is acquired by the user terminal 30 from the document management device 10 in response to selection of the metadata confirmation button 523, for example. Specifically, when the metadata confirmation button 523 is selected, the user terminal 30 transmits a metadata acquisition request, including a document ID corresponding to the task selected in the task list area 521 ( FIG. 8 ), to the document management unit 12. The document management unit 12 acquires the metadata stored in the metadata storage unit 15 in association with the document ID and transmits the acquired metadata to the user terminal 30. As a result, the user terminal 30 can display the metadata confirmation screen 530 including the acquired metadata. In this manner, the metadata stored in the metadata storage unit 15 is intended to be transmitted to the user terminal 30. In other words, the metadata storage unit 15 can be considered a storage unit that stores information to be transmitted to the user terminal 30. Therefore, in step S112, the processing result identifier acquisition unit 136 controls the storage of the target processing result identifier in the metadata storage unit 15 so that the target processing result identifier is transmitted to the user terminal 30.

[0069] When the accounting staff clicks on the URL displayed on the metadata confirmation screen 530 as the target processing result identifier or enters the URL into a browser, the accounting process is executed in step S116. In the accounting process, the user terminal 30 used by the accounting staff first accesses the URL. This access corresponds to a request to the UI unit 21 of the document processing device 20 to obtain the processing result (OCR result) corresponding to the target document (S116-1). In response to the request, the UI unit 21 obtains the processing result and the target document file stored in association with the URL to be accessed from the document processing unit 22 (S116-2). The UI unit 21 generates screen data for an accounting process screen including the processing result and the target document file, and transmits the screen data to the user terminal 30 (S116-1). The user terminal 30 displays the accounting process screen based on the screen data.

[0070] FIG. 11 is a diagram showing an example of an accounting processing screen. As shown in FIG. 11, the accounting processing screen 540 includes a preview area 541, an invoice information area 542, a journal voucher area 543, and the like. The preview area 541 is an area where the target document file is displayed. The invoice information area 542 is an area where the contents of the target document are displayed. In the initial state of the accounting processing screen 540, each field in the invoice information area 542 displays the processing results (OCR results) of the target document file by the document processing unit 22. The journal voucher area 543 is an area where the accounting staff enters data during accounting work. The accounting staff checks the contents of the invoice information area 542 for errors (i.e., misrecognition by the document processing unit 22, etc.). If there is an incorrect item in the invoice information area 542, the accounting staff corrects the content of the item.

[0071] When the accounting staff completes the corrections to the invoice information area 542 and the input to the journal voucher area 543 and selects the confirm button 544, the user terminal 30 transmits the contents of the invoice information area 542 and the contents of the journal voucher area 543 to the UI unit 21 (S116-1). The UI unit 21 requests the document processing unit 22 to save the contents of the invoice information area 542 and the contents of the journal voucher area 543 (S116-2). The document processing unit 22 overwrites the processing result stored in association with the target processing result identifier with the contents of the invoice information area 542. As a result, for example, corrections made by the document processing unit 22 to OCR misrecognition or the like are reflected in the processing result. This completes the accounting work.

[0072] When the accounting work is completed, the accounting staff selects the Complete button 524 with the task corresponding to the target document selected in the task list area 521 of the task list screen 520 (FIG. 8) displayed by the user terminal 30. The user terminal 30 transmits the accounting processing result ("Complete") corresponding to the selected Complete button 524 and the target document ID to the document management device 10 (S117).

[0073] When the UI unit 11 of the document management device 10 receives the accounting processing result and the target document ID, it notifies the workflow control unit 13 of the accounting processing result and the target document ID (S118). If the accounting processing result notified from the UI unit 11 is "completed," the transition detection unit 133 of the workflow control unit 13 detects that the transition condition ("completed") from Task 3 to Task 4 has been satisfied, based on the target flow information (FIG. 7) related to the target document ID. Then, the processing result acquisition unit 137 of the workflow control unit 13 acquires the processing result from the document processing unit 22 of the document processing device 20, based on the definition of Task 2 ("Acquire processing result from document processing device 20") in the target flow information (S119-1, S119-2).

[0074] Next, the processing result acquisition unit 137 requests the document management unit 12 to set the acquired processing results in the target metadata (S120) as a series of processes for task 4. Such a request includes the target document ID.

[0075] In response to a request from the processing result acquisition unit 137, the document management unit 12 sets the processing result to the target metadata stored in the metadata storage unit 15 that corresponds to the target document ID included in the request (S121).

[0076] FIG. 12 is a diagram showing the state of the target metadata at the end of step S121 in the first embodiment. As shown in FIG. 12, at the end of step S121, the target metadata includes a date and an amount. Note that, for convenience, the values in FIG. 12 do not match the values in FIG. 11. Furthermore, this embodiment shows an example in which part of the processing result by the document processing unit 22 is set in the metadata. However, all of the processing result by the document processing unit 22 may also be set in the metadata.

[0077] Next, the document management unit 12 notifies the workflow control unit 13 of the completion of setting the processing result (S122). Such notification includes the target document ID.

[0078] Based on the notification of the setting completion, the transition detection unit 133 of the workflow control unit 13 detects that the transition condition from Task 4 to Task 5 ("Setting Completed") has been satisfied in the target flow information (FIG. 7) related to the target document ID. Then, the assignment unit 134 notifies the accounting approver of the assignment of Task 5 ("Review by Accounting Approver") for the target document based on the definition of Task 5 ("Review by Accounting Approver") in the target flow information (FIG. 7) (S123).

[0079] The user terminal 30 used by the accounting approver who has been notified of the assignment of Task 5 displays the task list screen 520 (FIG. 8) in response to an operation by the accounting approver. Here, the type of work the accounting approver performs is arbitrary. For example, the accounting approver may select the metadata confirmation button 523 on the task list screen 520 to display the metadata confirmation screen 530. In this case, the accounting approver may click on a URL as a processing result identifier included in the metadata confirmation screen 530, or enter the URL into a browser, to refer to the processing result corresponding to the processing result identifier and confirm the results of the accounting work.

[0080] When approving the results of the accounting work, the accounting approver selects the Complete button 524 while the task corresponding to the target document is selected in the task list area 521 of the task list screen 520 (FIG. 8). The user terminal 30 transmits the review result ("Complete") and the target document ID corresponding to the selected Complete button 524 to the document management device 10 (S124). Upon receiving the review result and the target document ID, the UI unit 11 of the document management device 10 notifies the workflow control unit 13 of the review result and the target document ID (S125). If the review result notified from the UI unit 11 is "Complete," the transition detection unit 133 of the workflow control unit 13 detects that the termination condition of the workflow related to the target flow information has been satisfied, based on the target flow information (FIG. 7) related to the target document ID.

[0081] Although the above description has been given of an example in which the processing result identifier is a URL, any identification information other than a URL may be used as the processing result identifier as long as the identification information allows access to the processing result from outside the document processing device 20.

[0082] As described above, according to the first embodiment, document files are automatically uploaded from the document management device 10 to the document processing device 20. This eliminates the need for a user to download a document file from the document management device 10 and then upload it to the document processing device 20. However, if the document processing device 20 processes the document file in response to the upload from the document management device 10, it becomes difficult for the user (accounting staff) to obtain the processing results from the document processing device 20. This is because the user does not directly input an instruction to execute the process to the document processing device 20, and therefore the user cannot obtain the processing results in response to the execution instruction.

[0083] Therefore, in this embodiment, a processing result identifier indicating the source of the processing result is returned from the document processing device 20 to the document management device 10. The document management device 10 stores the processing result identifier in the metadata storage unit 15, which stores information to be sent to the user terminal 30 used by the user. As a result, the user can easily access the processing result by using the processing result identifier.

[0084] Therefore, according to this embodiment, even in the middle of a workflow (involving various users), it is possible to reduce the operational burden of accessing the execution results of processing on data that is the subject of the workflow.

[0085] Next, a second embodiment will be described. In the second embodiment, differences from the first embodiment will be described. Therefore, unless otherwise specified, the second embodiment may be the same as the first embodiment.

[0086] Fig. 13 is a sequence diagram illustrating an example of a processing procedure executed by the information processing system 1 according to the second embodiment. In Fig. 13, the same steps as those in Fig. 4 are assigned the same step numbers, and descriptions thereof will be omitted.

[0087] As shown in FIG. 13, in the second embodiment, steps S111-2, S112, and S113 in FIG. 4 are replaced with steps S111-2a, S112a, and S113a, respectively.

[0088] In step S111-2a, the document processing unit 22 transmits to the workflow control unit 13 a response including the target processing result identifier as well as the processing result (for example, OCR result) related to the target processing result identifier.

[0089] When the processing result identifier acquisition unit 136 of the workflow control unit 13 receives the target processing result identifier and the processing result, it controls the storage of the target processing result identifier and the processing result for the target document in the metadata storage unit 15 as a series of processes for task 2. Specifically, the processing result identifier acquisition unit 136 requests the document management unit 12 to set the target processing result identifier and the processing result in the target metadata (save the target processing result identifier and the processing result as metadata) (S112a). Such a request includes the target document ID.

[0090] In response to a request from the processing result identifier acquisition unit 136, the document management unit 12 sets a target processing result identifier and the processing result for the target metadata corresponding to the target document ID included in the request, among the metadata stored in the metadata storage unit 15 (S113a).

[0091] 14 is a diagram showing the state of the target metadata at the end of step S113a in the second embodiment. As shown in FIG. 9, at the end of step S113a, the target metadata includes the date and amount included in the processing result by the document processing unit 22 in addition to the processing result identifier.

[0092] The subsequent processing steps in Fig. 13 are the same as those in the first embodiment (Fig. 4). Note that in steps S119-1 to S121, the processing results are acquired again, and the date and amount of the target metadata are overwritten with the processing results.

[0093] FIG. 15 is a diagram showing the state of the target metadata at the end of step S121 in the second embodiment.

[0094] The reason why the processing result is acquired again in step S119 is that the processing result acquired in step S111a may include misrecognition in the OCR process by the document processing unit 22, and such misrecognition may have been corrected in the accounting work. That is, in step S119, there is a possibility that a processing result obtained is a result in which corrections have been made to the processing result acquired in step S111a.

[0095] To illustrate this possibility, FIG. 15 shows an example in which the date and amount in FIG. 14 have been corrected. Specifically, in FIG. 14, "2027 / 02 / 22" and "7,000,000 yen" are set for the date and amount, respectively, whereas in FIG. 15, "2021 / 02 / 22" and "1,000,000 yen" are set. This indicates that the accounting staff corrected the date and amount in this way. However, if there was no misrecognition by the document processing unit 22, the contents of FIG. 14 and FIG. 15 would be the same.

[0096] As described above, according to the second embodiment, it is possible to obtain the same effects as those of the first embodiment. Furthermore, according to the second embodiment, in step S113a, temporary values are set for the metadata (date, amount) of the target document, so that after step S113a is completed, it is possible to search for the target document based on the metadata, etc.

[0097] Next, a third embodiment will be described. In the third embodiment, differences from the first or second embodiment will be described. Therefore, unless otherwise specified, the third embodiment may be the same as the first or second embodiment.

[0098] 16 is a diagram showing an example of the functional configuration of the document management apparatus 10 and the document processing apparatus 20 according to the third embodiment. In FIG. 16, the same components as those in FIG. 3 are denoted by the same reference numerals, and the description thereof will be omitted.

[0099] 16, the workflow control unit 13 of the document management device 10 further includes a file ID acquisition unit 138.

[0100] Fig. 17 is a sequence diagram illustrating an example of a processing procedure executed by the information processing system 1 according to the third embodiment. In Fig. 17, the same steps as those in Fig. 4 are assigned the same step numbers, and descriptions thereof will be omitted as appropriate.

[0101] Steps S101 to S107 are the same as those in Fig. 4. However, in Fig. 17, the workflow information (that is, the target flow information) acquired in step S101 is different from that in Fig. 7.

[0102] Fig. 18 is a diagram showing an example of workflow information applied in the third embodiment. In the workflow information shown in Fig. 18, the start trigger is the same as in Fig. 7, but task 1 and task 2 are swapped with respect to Fig. 7. That is, in Fig. 18, "upload to document processing device 20" is set as task 1.

[0103] Therefore, following step S107, the upload unit 135 uploads (transmits) the target document file to the document processing unit 22 of the document processing device 20 (S111-1).

[0104] The process executed by the document processing unit 22 of the document processing device 20 in response to receiving the target document file is basically the same as that in the above-described embodiments. However, the document processing unit 22 of the third embodiment does not generate a processing result identifier at this point. Instead, the document processing unit 22 generates a file ID as identification information for the target document file. The document processing unit 22 stores the processing result (OCR result, etc.) in association with the file ID. At this time, the document processing unit 22 locks (restricts access to) the processing result for the file ID (hereinafter referred to as the "target file ID") to restrict (prohibit) access to the processing result. Therefore, the document processing unit 22 restricts (prohibits) access to the processing result until the lock is released. Next, the document processing unit 22 sends a response including the target file ID and the processing result to the workflow control unit 13 (S111-2b). However, the processing result does not have to be sent at this point.

[0105] When the file ID acquisition unit 138 of the workflow control unit 13 receives the target file ID, it controls the storage of the target file ID and the processing result for the target document in the metadata storage unit 15 as a series of processes for task 2. Specifically, the file ID acquisition unit 138 specifies the target document ID and requests the document management unit 12 to set the target file ID and the processing result in the target metadata (S112b).

[0106] In response to a request from the file ID acquisition unit 138, the document management unit 12 sets the target file ID and the processing result for the target metadata corresponding to the target document ID specified in the request from among the metadata stored in the metadata storage unit 15 (S113b).

[0107] 19 is a diagram showing the state of the target metadata at the end of step S113b in the third embodiment. As shown in Fig. 19, at the end of step S113b, the target metadata includes a file ID. However, at this point, the target metadata does not include a processing result identifier.

[0108] Next, the document management unit 12 notifies the workflow control unit 13 of the completion of setting the target file ID etc. (S114b). Such notification includes the target document ID.

[0109] Based on the notification of the setting completion, the transition detection unit 133 of the workflow control unit 13 detects that the transition condition from Task 1 to Task 2 ("Setting Completed") has been satisfied in the target flow information (FIG. 18) related to the target document ID. Then, the assignment unit 134 notifies the sales approver of the assignment of Task 2 (review) for the target document based on the definition of Task 2 ("Review by Sales Approver") in the target flow information (FIG. 18) (S108). Note that Task 2 is the same as Task 1 in the first embodiment. Therefore, steps S108 to S110 are executed for Task 2 in the same way as for Task 1 in the first embodiment.

[0110] Following step S110, if the examination result notified from the UI unit 11 is "Completed," the transition detection unit 133 of the workflow control unit 13 detects that the transition condition ("Completed") from Task 2 to Task 3 has been satisfied based on the target flow information (FIG. 18) related to the target document ID. Then, the processing result identifier acquisition unit 136 of the workflow control unit 13 controls Task 3 based on the definition of Task 3 ("Acquire processing result identifier from document processing device 20") in the target flow information.

[0111] First, the processing result identifier acquisition unit 136 specifies a target document ID and requests the document management unit 12 to acquire a target file ID (S201). The document management unit 12 acquires the target file ID from the target metadata (FIG. 19) corresponding to the target document ID (S202-1, S202-2). The document management unit 12 notifies the processing result identifier acquisition unit 136 of the acquired target file ID (S203).

[0112] Next, the processing result identifier acquisition unit 136 specifies the target file ID and sends a processing result identifier acquisition request to the document processing unit 22 of the document processing device 20 (S204-1). The document processing unit 22 generates a processing result identifier (target processing result identifier) for the processing result associated with the target file ID and associates the target processing result identifier with the processing result. Therefore, the target processing result identifier also corresponds to the target file ID. Note that, upon generating the target processing result identifier, the document processing unit 22 releases the lock on the processing result associated with the target processing result identifier. Next, the document processing unit 22 sends a response including the target processing result identifier to the processing result identifier acquisition unit 136 (S204-2).

[0113] When the processing result identifier acquisition unit 136 receives the target processing result identifier, it controls the storage of the target processing result identifier in the metadata storage unit 15 for the target document as a series of processes for task 3. Specifically, the processing result identifier acquisition unit 136 specifies the target document ID and requests the document management unit 12 to set the target processing result identifier in the target metadata (save the target processing result identifier as metadata) (S205).

[0114] In response to a request from the processing result identifier acquisition unit 136, the document management unit 12 sets a target processing result identifier for the target metadata corresponding to the target document ID specified in the request from among the metadata stored in the metadata storage unit 15 (S206).

[0115] Fig. 20 is a diagram showing the state of the target metadata at the end of step S206 in the third embodiment. As shown in Fig. 20, at the end of step S206, the target metadata includes a processing result identifier.

[0116] Next, the document management unit 12 notifies the workflow control unit 13 of the completion of setting the target process result identifier (S207). Such notification includes the target document ID.

[0117] Based on the notification of the setting completion, the transition detection unit 133 of the workflow control unit 13 detects that the transition condition from task 3 to task 4 ("setting completed") has been satisfied in the target flow information (FIG. 18) related to the target document ID. Task 4 and subsequent tasks in the target flow information (FIG. 18) in the third embodiment are the same as task 3 and subsequent tasks in the target flow information (FIG. 7) in the first embodiment. Therefore, from this point on, the same processes as those for task 3 and subsequent tasks (S115 to S125) in FIG. 4 are executed.

[0118] As described above, according to the third embodiment, it is possible to obtain the same effects as those of the first embodiment.

[0119] Furthermore, in the third embodiment, a document file is uploaded to the document processing device 20 before approval by the business approver. In this case, it is undesirable for the accounting staff to start accounting work on a target document that has not been approved by the business approver. Therefore, in the third embodiment, a target processing result identifier for the processing result by the document processing device 20 is set in the target metadata after approval by the business approver, rather than when the document file is uploaded to the document processing device 20. This makes it possible to prevent the accounting staff from starting accounting work before approval by the business approver.

[0120] The locking and unlocking of the processing result by the document processing unit 22 may be defined as a task of the workflow information.

[0121] Next, a fourth embodiment will be described. In the fourth embodiment, differences from the above embodiments will be described. Therefore, unless otherwise specified, the fourth embodiment may be the same as the above embodiments.

[0122] Fig. 21 is a sequence diagram illustrating an example of a processing procedure executed by the information processing system 1 according to the fourth embodiment. In Fig. 21, the same steps as those in Fig. 4 are assigned the same step numbers, and descriptions thereof will be omitted.

[0123] In step S101 of FIG. 21, workflow information different from that of FIG. 7 is acquired as target flow information.

[0124] Fig. 22 is a diagram showing an example of workflow information applied in the fourth embodiment. The workflow information in Fig. 22 is obtained by deleting task 4 and the transition condition from task 4 to task 5 from the workflow information in Fig. 7. As a result, task 5 in Fig. 7 becomes task 4 in Fig. 22. Here, task 4 in Fig. 7 is acquisition of a processing result from the document processing device 20. In the fourth embodiment, the definition of task 4 is unnecessary because the processing result is notified from the document processing device 22 to the workflow control unit 13.

[0125] In order to enable the document processing unit 22 to notify the workflow control unit 13 of the processing result, in FIG. 21, step S111-1 in FIG. 4 is replaced with step S111-1c.

[0126] In step S111-1c, the upload unit 135 uploads (transmits) the notification destination identifier together with the target document file to the document processing unit 22 of the document processing device 20. The notification destination identifier is identification information indicating the notification destination (callback destination) of the processing result. For example, in this embodiment, the notification destination of the processing result is the processing result acquisition unit 137. Therefore, the notification destination identifier is, for example, address information (e.g., a URL) for the processing result acquisition unit 137 to receive the processing result.

[0127] After that, when the accounting process is completed and the process result for the target document is determined, the document processing unit 22 transmits the process result to the notification destination identifier (S301).

[0128] When the processing result acquisition unit 137 receives the processing result, the processing procedure from step S120 onwards is executed.

[0129] As described above, according to the fourth embodiment, it is possible to obtain the same effects as those of the first embodiment.

[0130] Furthermore, in the fourth embodiment, the processing result reflecting the accounting work is automatically sent from the document processing device 20 to the document management device 10. Therefore, the accounting staff does not need to select the Complete button 524 on the task list screen 520. In other words, selecting the Confirm button 544 on the accounting processing screen 540 can also serve as selecting the Complete button 524 on the task list screen 520. As a result, the workload of the accounting staff can be further reduced.

[0131] Note that the user terminal 30 is not limited to a specific type of device as long as it is a device equipped with a communication function. The user terminal 30 may be, for example, an image forming device, a PJ (Projector), an IWB (Interactive White Board: a white board with an electronic blackboard function that allows mutual communication), an output device such as digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, a network home appliance, a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, a desktop PC, or the like.

[0132] Furthermore, each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and conventional circuit modules designed to perform each of the above-described functions.

[0133] Additionally, the devices described in each embodiment represent only one of multiple computing environments for implementing the embodiments disclosed herein.

[0134] In one embodiment, the document management device 10 includes multiple computing devices, such as a server cluster, configured to communicate with each other over any type of communications link, including a network, shared memory, etc., to perform the processes disclosed herein. Similarly, the document processing device 20 may include multiple computing devices configured to communicate with each other.

[0135] Furthermore, the document management device 10 and the document processing device 20 can be configured to share the disclosed processing steps in various combinations. For example, the process performed by a specific functional unit can be executed by the document processing device 20. Similarly, the function of a specific functional unit can be executed by the document processing device 20. Furthermore, the elements of the document management device 10 and the document processing device 20 can be integrated into a single server device or separated into multiple devices.

[0136] In each of the above embodiments, the document management device 10 is an example of a data management device. The document processing device 20 is an example of a data processing device. The document management unit 12 is an example of a storage processing unit. The upload unit 135 is an example of a transmission unit. The processing result identifier acquisition unit 136 is an example of a first acquisition unit. The document storage unit 14 is an example of a first storage unit. The processing result identifier is an example of first identification information. The metadata storage unit 15 is an example of a second storage unit. The file ID acquisition unit 138 is an example of a second acquisition unit. The file ID is an example of second identification information. The notification destination identifier is an example of third identification information. The processing result acquisition unit 137 is an example of a third acquisition unit. The sales representative is an example of a first user. The accounting representative is an example of a second user.

[0137] Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications and variations are possible within the scope of the gist of the present invention as described in the claims. [Explanation of symbols]

[0138] 1. Information Processing Systems 10 Document management device 11 UI section 12 Document Management Department 13 Workflow control section 14 Document Storage 15 Metadata storage unit 16 Workflow information storage unit 20 Document Processing Device 21 UI section 22 Document Processing Unit 30 User terminals 100 Drive device 101 Recording media 102 Auxiliary storage 103 Memory Device 104 CPU 105 Interface Device 131 Workflow information acquisition unit 132 Target flow information identification part 133 Transition detection unit 134 Assignment Section 135 Upload Section 136 Processing result identifier acquisition unit 137 Processing result acquisition unit 138 File ID Acquisition Unit B Bus [Prior art documents] [Patent documents]

[0139] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-259211

Claims

1. An information processing system including a data management device and a data processing device, The data management device a storage processing unit that stores document data transmitted from one or more terminals and a data type of the document data in a first storage unit; an identification unit that identifies workflow information of a workflow to be applied to a target document from one or more workflows stored in a workflow information storage unit based on the type of the document data; a first transmission unit that transmits the document data stored in the first storage unit to the data processing device as one process constituting a workflow related to the workflow information identified by the identification unit; a first acquisition unit that acquires first identification information indicating a destination for obtaining the processing result from the data processing device, making the processing result of the document data by the data processing device accessible from outside the data processing device, and stores the first identification information in a second storage unit that stores information to be transmitted to any one of the one or more terminals; a second transmission unit that transmits metadata including the first identification information to any one of the one or more terminals; a notification unit that notifies one of the one or more terminals of a task assignment for the document data transmitted from one of the one or more terminals and stored in the first storage unit; and the first acquisition unit acquires, from the data processing device, the first identification information corresponding to the second identification information for the document data after receiving an inspection result indicating that there is no problem with the document data related to the task from the one or more terminals that have notified the assignment to the task. An information processing system comprising:

2. the first acquisition unit further acquires a result of the processing and stores the result of the processing in the second storage unit.

2. The information processing system according to claim 1, further comprising:

3. The first transmission unit further transmits third identification information to the data processing device, the third identification information indicating the data management device as a notification destination of the result of the processing, The data management device a second acquisition unit that acquires a result of the processing from the data processing device; 2. The information processing system according to claim 1, further comprising:

4. a storage processing unit that stores document data transmitted from one or more terminals and a data type of the document data in a first storage unit; an identification unit that identifies workflow information of a workflow to be applied to a target document from one or more workflows stored in a workflow information storage unit based on the type of the document data; a first transmission unit that transmits the document data stored in the first storage unit to a data processing device as one process constituting a workflow related to the workflow information identified by the identification unit; a first acquisition unit that acquires first identification information indicating a destination for obtaining the processing result from the data processing device, making the processing result of the document data by the data processing device accessible from outside the data processing device, and stores the first identification information in a second storage unit that stores information to be transmitted to any one of the one or more terminals; a second transmission unit that transmits metadata including the first identification information to any one of the one or more terminals; a notification unit that notifies one of the one or more terminals of a task assignment for the document data transmitted from one of the one or more terminals and stored in the first storage unit; and the first acquisition unit acquires, from the data processing device, the first identification information corresponding to the second identification information for the document data after receiving an inspection result indicating that there is no problem with the document data related to the task from the one or more terminals that have notified the assignment to the task. A data management device characterized by:

5. a storage process step of storing document data transmitted from one or more terminals and the data type of the document data in a first storage unit; a specifying step of specifying workflow information of a workflow to be applied to the target document from one or more workflows stored in a workflow information storage unit based on the type of the document data; a first transmission step of transmitting the document data stored in the first storage unit to a data processing device as one process constituting a workflow related to the workflow information identified in the identification step; a first acquisition step of acquiring, from the data processing device, first identification information indicating a destination for acquiring the processing result on the document data by the data processing device, which makes the processing result accessible from outside the data processing device, and storing the first identification information in a second storage unit that stores information to be transmitted to any one of the one or more terminals; a second transmission step of transmitting metadata including the first identification information to any one of the one or more terminals; a notification step of notifying any one of the one or more terminals of a task assignment for the document data transmitted from any one of the one or more terminals and stored in the first storage unit; The computer executes the first acquisition step includes acquiring, from the data processing device, the first identification information corresponding to the second identification information for the document data after receiving an inspection result indicating that there is no problem with the document data related to the task from the one or more terminals that have notified the assignment to the task; A data management method comprising:

6. a storage process step of storing document data transmitted from one or more terminals and the data type of the document data in a first storage unit; a specifying step of specifying workflow information of a workflow to be applied to the target document from one or more workflows stored in a workflow information storage unit based on the type of the document data; a first transmission step of transmitting the document data stored in the first storage unit to a data processing device as one process constituting a workflow related to the workflow information identified in the identification step; a first acquisition step of acquiring, from the data processing device, first identification information indicating a destination for acquiring the processing result on the document data by the data processing device, which makes the processing result accessible from outside the data processing device, and storing the first identification information in a second storage unit that stores information to be transmitted to any one of the one or more terminals; a second transmission step of transmitting metadata including the first identification information to any one of the one or more terminals; a notification step of notifying any one of the one or more terminals of a task assignment for the document data transmitted from any one of the one or more terminals and stored in the first storage unit; on the computer, the first acquisition step includes acquiring, from the data processing device, the first identification information corresponding to the second identification information for the document data after receiving an inspection result indicating that there is no problem with the document data related to the task from the one or more terminals that have notified the assignment to the task; A program characterized by:

Images