Server, its control method, and program

Abstract

To provide an image processing system, a server and a method for controlling the same, and a program.SOLUTION: A method controls a server accessible to a cloud service, and presents, on an information processing apparatus, a first setting screen for performing settings of image data to be transmitted, and stores the settings of the image data to be transmitted received from a user through the first setting screen in association with the type of the image data and information on the user. The method presents, on the information processing apparatus, a second setting screen for selecting settings to be stored in storage means for new image data to be transmitted, and presents the first setting screen on the information processing apparatus while reflecting settings necessary for transmission excluding the type of the image data from among the settings stored in the storage means and selected by the user so as to use the same settings through the second setting screen. The method transmits the image data to be transmitted to the cloud service according to the settings of the image data to be transmitted received by the user through the first setting screen. The method further stores the type of the new image data to be transmitted in the storage means additionally in association with the selected settings.SELECTED DRAWING: Figure 19

Description

[Technical Field]

[0001] The present invention ,sa The present invention relates to a server, a control method thereof, and a program. [Background technology]

[0002] In recent years, an increasing number of MFPs (multi-function peripherals) are linked to cloud services that provide services such as cloud storage. Using such an MFP, for example, allows a user to scan a document and send the resulting image data to a cloud service designated by the user. The user then designates the cloud service and folder to which the image data is to be sent, sets a file name, and then transmits the image data. Setting the file name using a keyboard or other device is tedious, so Patent Document 1 proposes a technique for previewing a scanned image and using the OCR results of a character region selected by the user as the file name, metadata, and so on for the image data. Patent Document 2 also proposes a technique for sharing a personal setting information file of an MFP device associated with personal authentication over a network, enabling it to be used by other MFP devices. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-178280 [Patent Document 2] Japanese Patent Application Laid-Open No. 2007-49609 Summary of the Invention [Problem to be solved by the invention]

[0004] According to Patent Document 1, when a similar image is scanned again, a unique file name can be assigned to the scanned image data using the same character string in the same position as the file name assigned to the previous similar image, thereby reducing the effort required for configuration. However, because the destination setting must be configured in advance, it is not possible for each user to freely specify and manage storage rules for, for example, a form with no set storage rules. Furthermore, as in Patent Document 2, if information set by an individual is stored in association with personal authentication and can be reused to specify file names, etc., the configuration burden for new types of image data can be reduced. However, if a setting using character strings within an image is included, as in Patent Document 1, applying that position information to a different type of image can result in the extraction of incorrect character strings, which is inconvenient.

[0005] An object of the present invention is to solve at least one of the problems of the prior art.

[0006] An object of the present invention is to provide a technique for improving operability when a user makes settings for transmitting image data to a service. [Means for solving the problem]

[0007] In order to achieve the above object, a server according to one aspect of the present invention has the following configuration: A server that can access a cloud service, a storage means for storing the type of image data and a transmission setting for transmitting the image data to the cloud service in association with each other; a selection screen presenting means for presenting a list of the transmission settings stored in the storage means to the information processing device and presenting a selection screen on the information processing device for allowing the user to select a transmission setting to be used for the image data to be newly transmitted from the list, when the type of image data to be newly transmitted is not similar to any of the types of image data stored in the storage means and an instruction to reuse the transmission setting stored in the storage means is given by a user of the information processing device; and a setting screen presenting means for presenting to the information processing device, when a transmission setting is selected by the user via the selection screen, a setting screen for making transmission settings for the new image data to be transmitted, in a state where the selected transmission settings, excluding settings related to character strings to be OCR-targeted, are reflected; the determination of whether the type of the image data to be newly transmitted is similar to any of the types of image data stored in the storage means is made by comparing the layout information of character regions of the image data to be newly transmitted and the image data stored in the storage means; The storage means is characterized in that it stores the type of image data to be newly transmitted in additional association with the transmission setting selected via the selection screen and stored in the storage means. [Effects of the Invention]

[0008] According to the present invention, it is possible to improve the operability when a user makes settings to transmit image data to a service.

[0009] Other features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings, in which the same or similar elements are designated by the same reference numerals. [Brief explanation of the drawings]

[0010] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. [Figure 1] 1 is a diagram showing the overall configuration of an image processing system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram illustrating the hardware configuration of an MFP according to an embodiment. [Figure 3] FIG. 2 is a block diagram illustrating the hardware configuration of a client PC and an MFP cooperation service according to the embodiment. [Figure 4] FIG. 2 is a functional block diagram illustrating the software configuration of the image processing system according to the embodiment. [Figure 5]FIG. 10 is a sequence diagram illustrating the flow of processing between devices when scan image data obtained by scanning with the MFP according to the embodiment is converted into a file and transmitted to cloud storage. [Figure 6] FIG. 10 is a sequence diagram illustrating how form data transmitted to the MFP linkage service according to the embodiment is viewed and manipulated on a client PC, and then transmitted to cloud storage. [Figure 7] 1A shows an example of a scan button selection screen displayed on the MFP according to the embodiment, and FIG. 1B shows an example of a default scan setting screen displayed on the MFP according to the embodiment. [Figure 8] Figure (A) shows an example of setting up new transmission settings for unlearned scanned document data on a list screen of scanned document data displayed on a client PC relating to an embodiment, and Figure (B) shows an example screen on a list screen of scanned document data displayed on a client PC relating to an embodiment, where the user can select whether to reuse transmission settings set for other existing scanned document data or set new settings for scanned document data for which there are no similar documents (unlearned). [Figure 9] FIG. 1A shows an example of a list screen of transmission settings displayed on a client PC when reusing existing transmission settings, and FIG. 1B shows an example of a destination setting screen displayed on a client PC according to an embodiment. [Figure 10] FIG. 1A shows an example of a destination folder setting screen displayed on a client PC according to an embodiment, and FIG. 1B shows an example of a folder rule setting screen displayed on a client PC according to an embodiment. [Figure 11] FIG. 1A shows an example of a fixed string formula creation screen displayed on a client PC according to an embodiment, and FIG. 1B shows an example of a new OCR string selection screen displayed on a client PC according to an embodiment. [Figure 12] FIG. 10 is a diagram showing an example of a setting screen for the file format of scanned form data displayed on a client PC according to the embodiment. [Figure 13] FIG. 10 is a diagram showing an example of a file name editing screen displayed on a client PC according to the embodiment. [Figure 14] FIG. 10 is a diagram showing an example of a list screen of scanned form data displayed on a client PC according to the embodiment. [Figure 15] 10A and 10B are diagrams showing an example of a screen displayed on a client PC according to the embodiment when selecting a character string to be used as the company name in the file name of scanned form data. [Figure 16] FIG. 4 is a diagram showing an example of a setting information management table according to the embodiment. [Figure 17] 10 is a flowchart for describing image analysis processing executed by an image processing unit of the MFP collaboration service according to the embodiment. [Figure 18] 10 is a flowchart for explaining a process in which the MFP linkage service according to the embodiment acquires information for displaying a list screen of scanned form data and transmits the information to a client PC. [Figure 19] 10 is a flowchart for explaining processing by the MFP linkage service according to the embodiment to save setting information for scanned form data. [Figure 20] 15 is a flowchart for explaining the processing performed by the MFP collaboration service according to the embodiment when a button for changing settings is pressed on the screen of FIG. 14. [Figure 21] 10 is a flowchart illustrating processing in which the MFP linkage service according to the embodiment generates a file using information set in scanned form data and transmits the file to a set destination. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention claimed. Although multiple features are described in the embodiments, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined arbitrarily. Furthermore, in the accompanying drawings, the same reference numerals are used to designate the same or similar components, and redundant explanations will be omitted.

[0012] [Embodiment] FIG. 1 is a diagram showing the overall configuration of an image processing system according to an embodiment of the present invention.

[0013] This image processing system includes an MFP 110, a client PC (personal computer) 111, an MFP linkage service 120, and cloud storage 130. The MFP 110 and the client PC 111 are connected via a LAN (Local Area Network) so as to be able to communicate with servers that provide various services on the Internet.

[0014] The MFP 110 is a multifunction peripheral having multiple functions such as a scanner and a printer, and is an example of an image forming apparatus. The client PC 111 is an information processing apparatus that receives a service requested from the MFP linkage service 120. The MFP linkage service (Web server) 120 is an example of a service that has the function of saving image data files obtained by scanning with the MFP 110 on its own server and transferring the image data to a service that can save the image data files, such as another storage service. The cloud storage (service) 130 saves files received via the Internet. It also provides a service that allows an external device to obtain files from the cloud storage 130 via a web browser. Note that the cloud storage is not limited to the illustrated cloud storage 130, and multiple cloud storages exist in this image processing system (not shown).

[0015] Although the image processing system according to the embodiment includes an MFP 110, a client PC 111, an MFP collaboration service 120, and a cloud storage 130, the present invention is not limited to this. For example, the MFP 110 may also serve as both the client PC 111 and the MFP collaboration service 120. The MFP collaboration service 120 may also be connected to a server on a LAN rather than on the Internet. The cloud storage 130 may be replaced by a mail server or the like, and scanned image data may be attached to an email and sent.

[0016] FIG. 2 is a block diagram illustrating the hardware configuration of the MFP 110 according to the embodiment.

[0017] The MFP 110 includes a control unit 210, an operation unit 220, a printer unit 221, a scanner unit 222, and a modem 223. The control unit 210 includes units 211 to 219, which will be described below, and controls the overall operation of the MFP 110. The CPU 211 loads a control program stored in a ROM 212 into a RAM 213 and executes the program to perform and control various functions of the MFP 110, such as reading, printing, and communication. The RAM 213 is used as a temporary storage area, such as the CPU 211's main memory and work area. In the embodiment, one CPU 211 executes each process shown in the flowcharts described below using one memory (RAM 213, ROM 212, or HDD 214). However, the present invention is not limited to this. For example, each process may be executed by multiple CPUs or multiple RAMs or HDDs working together. The HDD (hard disk drive) 214 is a large-capacity storage unit that stores image data and various programs. The HDD is not limited to an HDD, and may be, for example, an SD memory. The operation unit I / F 215 is an interface that connects the operation unit 220 and the control unit 210. The operation unit 220 is equipped with a touch panel, a keyboard, and the like, and accepts operations, inputs, and instructions from a user. The printer I / F 216 is an interface that connects the printer unit 221 and the control unit 210. Image data to be printed is transferred from the control unit 210 to the printer unit 221 via the printer I / F 216, and is printed on a recording medium by the printer unit 221. The scanner I / F 217 is an interface that connects the scanner unit 222 and the control unit 210. The scanner unit 222 reads an original placed on a platen or an ADF (Auto Document Feeder), not shown, to generate image data, and inputs the image data to the control unit 210 via the scanner I / F 217. The MFP 110 can print (copy) the image data generated by the scanner unit 222 from the printer unit 221, as well as send it as a file or by email. The modem I / F 218 is an interface that connects the modem 223 and the control unit 210. The modem 223 communicates image data via facsimile with a facsimile device on the PSTN. The network I / F 219 is an interface that connects the control unit 210 (MFP 110) to a LAN.The MFP 110 uses the network I / F 219 to send image data and information to various services on the Internet and to receive various types of information.

[0018] 3 is a block diagram illustrating the hardware configuration of client PC 111 and MFP collaboration service 120 according to the embodiment. Here, client PC 111 and MFP collaboration service 120 have similar hardware configurations, and therefore will be described with reference to the single block diagram shown in FIG.

[0019] The client PC 111 and the MFP collaboration service 120 each have a CPU 311, a ROM 312, a RAM 313, a HDD 314, a network I / F 315, and an operation unit 316. The CPU 311 executes a boot program stored in the ROM 312 and loads a program stored in the HDD 314 into the RAM 313 for execution, thereby controlling the operation of the PC 111 or the entire server. The RAM 313 is used as a temporary storage area such as the main memory or work area of ​​the CPU 311. The HDD 314 is a mass storage unit that stores image data and various programs. The network I / F 315 is an interface that connects the client PC 111 or the MFP collaboration service 120 to the Internet. The MFP collaboration service 120 and cloud storage 130 receive processing requests from other devices (such as the MFP 110) via the network I / F 315 and send and receive various information. The operation unit 316 has a display with a touch panel function, a keyboard, a pointing device, etc., and receives user operations and transmits them to the CPU 311 .

[0020] FIG. 4 is a functional block diagram illustrating the software configuration of the image processing system according to the embodiment.

[0021] The MFP 110 is broadly divided into two parts: a native function unit 410 and an additional function unit 420. The functions of these function units are realized by the CPU 211 loading into the RAM 213 and executing programs stored in the ROM 212 or HDD 214 of the MFP 110. While the units included in the native function unit 410 are provided as standard in the MFP 110, the additional function unit 420 is realized by an application additionally installed on the MFP 110. The additional function unit 420 is an application based on Java (registered trademark), and can easily add functions to the MFP 110. Note that other additional applications (not shown) may be installed on the MFP 110.

[0022] The native function unit 410 includes a scan execution unit 411 and an image data storage unit 412. The additional function unit 420 includes a display control unit 421, a scan instruction unit 422, and a cooperation service request unit 423.

[0023] The display control unit 421 displays a UI (user interface) screen for accepting user operations via a display unit having a touch panel function of the operation unit 220 of the MFP 110. For example, it displays an operation screen for accepting input of authentication information for accessing the MFP linkage service 120, scan settings, and operations for starting scanning. The scan instruction unit 422 requests the scan execution unit 411 to perform scan processing using scan settings according to user instructions input via the UI screen.

[0024] The scan execution unit 411 receives a scan request including scan settings from the scan instruction unit 422. In accordance with the scan request, the scan execution unit 411 generates scanned image data by reading an original document transported or placed on the platen glass using the scanner unit 222 via the scanner I / F 217. The scanned image data generated in this manner is sent to and stored in the image data storage unit 412. The scan execution unit 411 sends an image identifier that uniquely identifies the scanned image data stored in the image data storage unit 412 to the scan instruction unit 422. This image identifier includes numbers, symbols, alphabets, etc. (not shown) for uniquely identifying image data obtained by scanning in the MFP 110. The image data storage unit 412 stores the scanned image data received from the scan execution unit 411 in the HDD 214. The scan instruction unit 422 then acquires the scanned image data corresponding to the image identifier received from the scan execution unit 411 from the image data storage unit 412. Furthermore, the scan instruction unit 422 outputs an instruction to process the scanned image data to the cooperation service request unit 423, and requests the MFP cooperation service 120 to perform the processing.

[0025] The collaboration service request unit 423 requests various processes from the MFP collaboration service 120. For example, it requests login, analysis of scanned image data, etc. Here, protocols such as REST and SOAP are used for communication with the MFP collaboration service 120, but other communication means may also be used.

[0026] Next, the functions of the MFP cooperation service 120 will be described.

[0027] The MFP linkage service 120 includes a request control unit 431 , an image processing unit 432 , a cloud storage access unit 433 , a data management unit 434 , and a display control unit 435 .

[0028] The request control unit 431 waits in a state in which it can receive a request from an external device. When the request is received, the request control unit 431 instructs the image processing unit 432, the cloud storage access unit 433, and the data management unit 434 to perform processing as appropriate in response to the request. For example, when a login request from the MFP 110 is received, the request control unit 431 performs login processing.

[0029] The image processing unit 432 performs recognition processing and image data processing such as analyzing character areas in image data, OCR (Optical Character Recognition), determining similar forms (explained in the processing of S516 in Figure 5 below), and rotating and tilting the image.

[0030] The cloud storage access unit 433 sends a processing request to a cloud service that provides the functions (storage service) of the cloud storage 130. Cloud services generally use protocols such as REST and SOAP to publish various interfaces for saving files in the cloud storage and retrieving saved files from external devices. The cloud storage access unit 433 operates the cloud storage 130 using the published interface of the cloud storage 130.

[0031] The data management unit 434 holds user information and various setting data managed by the MFP cooperation service 120 .

[0032] Display control unit 435 receives a request from a web browser running on a terminal (not shown), such as a PC or mobile device, connected via the Internet and returns screen configuration information (HTML, CSS, etc.) required for screen display. The user can check user information registered in MFP linkage service 120 or change settings for scanning via the screen displayed on the web browser. Note that while FIG. 4 illustrates an example configuration in which additional function unit 420 is installed in MFP 110, the present invention is not limited to this configuration, and for example, the functions of additional function unit 420 may be included in client PC 111.

[0033] Fig. 5 is a sequence diagram illustrating the flow of processing between each device when scan image data obtained by scanning with the MFP 110 according to the embodiment is converted into a file and sent to cloud storage. Fig. 5 shows the sequence from when a user scans a form using a scan app on the MFP 110 to when the form data is sent to the MFP linkage service 120. Here, the explanation will focus on the interactions between each device.

[0034] At the start of the process in FIG. 5, the MFP 110 displays a main screen on which buttons for executing the functions it provides are arranged. Manipulate Sakube 220 Ta The screen is displayed on the touch panel. By installing an additional application (hereafter referred to as a scan app) on the MFP 110 for sending scanned form data to cloud storage, a button for using the functions of the application is displayed on the main screen of the MFP 110. When this button is pressed, a screen required for sending scanned form data to the MFP linkage service 120 is displayed.

[0035] In S501, the MFP 101 displays a login screen (not shown) for entering authentication information for accessing the MFP linkage service 120. Then, in S502, when the user enters the username and password required for login via the login screen, the MFP 110 sends a login request to the MFP linkage service 120. In response, in S503 the MFP linkage service 120 verifies whether the username and password included in the login request are correct, and if correct, returns an access token to the MFP 110. From this point on, various requests made from the MFP 110 to the MFP linkage service 120 include this access token, and this information makes it possible to identify the user to be processed. User authentication is performed using a commonly known method (Basic authentication, Digest authentication, authorization using OAuth, etc.).

[0036] When the login process is complete, the MFP 110 displays applications that the MFP 110 can use on a main screen (not shown) in S504. When the user presses a scan application on the main screen, a request to launch the scan application is sent from the MFP 110 to the MFP collaboration service 120 in S505. In response, the MFP collaboration service 120 obtains information necessary to display a button selection screen for scan processes that the logged-in user can use from the HDD 314 of the MFP collaboration service 120 and sends the information to the MFP 110. In this way, in S506, the MFP 110 displays the scan button selection screen shown in FIG. 7A based on the information received from the MFP collaboration service 120.

[0037] FIG. 7A is a diagram showing an example of a scan button selection screen displayed on the MFP 110 according to the embodiment.

[0038] Buttons 701 to 704 in FIG. 7A indicate the scan buttons that can be used by the logged-in user among the scan buttons registered in the MFP service linkage 120. There are two types of scan buttons. One is button 701 (hereinafter referred to as a no-setting button) that allows the client PC 111 to set the cloud service to which scanned data is to be sent, the destination folder, output settings, file name, and the like. The other is buttons 702, 703, and 704 (hereinafter referred to as buttons with settings) that allow the cloud service to be sent, scan settings, and the like to be set in advance in the MFP linkage service 120. To display these setting-enabled buttons 702 to 704, the user or an administrator of the MFP 110 must register the required number of required combinations of settings in the MFP linkage service 120. Because button 701 does not need to be set in advance in the MFP linkage service 120, only one button is displayed to the user. Therefore, even if an administrator or the like has not registered the button in the MFP linkage service 120 in advance, this button 701 allows the logged-in user to use the functions of the scan application. Furthermore, the user can specify the necessary settings after scanning without relying on the administrator. In the following description of the embodiment, it is assumed that the user uses the No Settings button 701.

[0039] Here, when the user selects button 701, in S507, the MFP 110 requests the MFP collaboration service 120 for the scan settings that are set by default for the unset button 701. In response to this scan setting request, the MFP collaboration service 120 obtains the default scan settings for that button 701 and information necessary for displaying the scan setting screen from the HDD 314 of the MFP collaboration service 120 and transmits them to the MFP 110.

[0040] As a result, in S508, the MFP 110 displays the scan setting screen of FIG. 7B using the received information.

[0041] FIG. 7B is a diagram showing an example of a default scan setting screen displayed on the MFP 110 according to the embodiment.

[0042] The scan button 705 is a button for instructing to execute a scan. 6 is an area that accepts changes to scan settings such as color, resolution, image quality, double-sided printing, mixed document size, density, and document size. Preview display 707 displays a preview of the scanned document. Area 708 includes buttons for page forwarding and page rotation of the displayed preview, deleting pages, and adding pages (additional scanning). Back button 709 is a button for returning to the scan button selection screen. On this screen in FIG. 7(B), the user configures various scan reading settings, places the paper form to be scanned on the platen glass or ADF, and presses scan button 705. As a result, in S509 of FIG. 5, the MFP 110 executes scanning and generates electronic form data from the paper form.

[0043] 7B is a button for advancing the data obtained by scanning to the next process. When the Next button 710 is pressed, the MFP 110 displays a scan processing in progress screen in S510 of Fig. 5. Then, in S511, the MFP 110 transmits a request for analyzing the scanned image to the MFP cooperation service 120 together with the image data generated in the scan processing in S509.

[0044] The scanned image data received by MFP collaboration service 120 is held in HDD 314 of MFP collaboration service 120 until it is sent to cloud storage 130. When MFP collaboration service 120 receives a request to analyze the scanned image from MFP 110, in S512, image processing unit 432 of MFP collaboration service 120 begins analyzing the image data. Thereafter, without waiting for the image analysis process to finish, MFP collaboration service 120 returns to MFP 110 a "processId" that is an identifier that uniquely identifies the analysis requested of MFP collaboration service 120.

[0045] In this image analysis process, the MFP collaboration service 120 first analyzes character areas present in the image data in S514, and then performs character recognition processing on all character areas in S515. Then, in S516, using the layout information of the character areas in the form, the MFP collaboration service 120 compares the layout information of images scanned in the past and the layout information of the image scanned this time by the user who logged in in S503 to determine whether the scanned image has a similar layout of character areas. This process is called similar form determination. If the scanned image data of interest is similar to previously scanned image data in this similar form determination, the MFP collaboration service 120 adds information indicating the settings configured in the similar image and saves it in the HDD 314 of the MFP collaboration service 120. On the other hand, if no similar image is found, the MFP collaboration service 120 saves information on the character areas of the entire scanned image data and information indicating that no similar images exist. The information on the previously scanned image data used in this determination is saved and accumulated while being linked to the user in the processes of S617 and S621, which will be described later with reference to FIG. 6. The details of the processes in S514 to S516 in FIG. 5 will be described later with reference to FIG.

[0046] In S517, the MFP 110 uses the "processId" received in the response to S511 to periodically (for example, every several hundred milliseconds to a few milliseconds) check with the MFP interaction service 120 the processing status of the image analysis corresponding to that "processId." Although not shown in FIG. 5, the processing of S517 continues until a response indicating that image processing is complete is obtained from the MFP interaction service 120. When the MFP interaction service 120 receives the request to check the processing status in S517, it checks the status of the processing corresponding to that "processId" and returns a response.

[0047] At this time, a character string indicating the current processing status is stored in the "status" of the response. For example, when "status" is "processing," it indicates that processing is currently being performed by the MFP linkage service 120, and when it is "completed," it indicates that processing has been completed. Note that if processing fails, other statuses such as "failed" may also be returned.

[0048] When the MFP 101 detects the completion of the process in S517, the MFP 110 displays a message indicating that the scan is complete on the operation unit 220 of the MFP 110 in S518, and returns to the scan setting screen display in S508. If there are multiple forms to be scanned at this time, multiple copies of the forms can be scanned repeatedly (the processes from S508 to S518 can be repeated). Also, by specifying settings to divide the scanned document using a fixed number of pages or dividers before scanning, multiple forms can be scanned at once and then divided into multiple forms.

[0049] After S518, the user sets transmission settings such as the cloud storage destination, destination folder, output settings, file name, and metadata for the form data obtained by scanning, and performs processing to transmit the data to the cloud storage 130 on the client PC 111. Although not shown, when the client PC 111 accesses the MPF linkage service 120, a login process is performed in the same way as the MFP 110, and the user processes the scanned form data that he or she scanned.

[0050] Next, with reference to FIG. 6, a process will be described in which the user operates the client PC 111 to view and operate the form data transmitted to the MFP collaboration service 120 on the client PC 111 and transmit the data to the cloud storage 130.

[0051] 6 is a sequence diagram showing how form data transmitted to the MFP linkage service 120 according to the embodiment is viewed and operated on the client PC 111, and transmitted to the cloud storage 130. In FIG. 6 as well, the explanation will be centered on the interactions between the devices.

[0052] In step S601, the client PC 111 acquires from the MFP linkage service 120 and displays a list screen of scanned form data for confirming a list of form data obtained by scanning.

[0053] FIG. 8A is a diagram showing an example of a case where new transmission settings are made for unlearned scanned form data on a list screen of scanned form data displayed on the client PC 111 according to the embodiment.

[0054] Reference numerals 801 to 803 indicate form data scanned by the user with the MFP 110. Area 804 displays information (hereinafter referred to as job properties) set for scanned form data selected on the scanned form data list screen. Button 805 displays a screen for setting the destination cloud storage. Button 806 displays a screen for setting a destination folder in the destination cloud storage after setting the destination cloud storage with button 805. Button 807 displays a screen for setting output settings such as the save file format when saving form data to cloud storage. Button 808 displays a screen for setting the file name of the saved file. Button 809 is a button for saving the settings or sending the scanned form data to the set destination after completing the necessary settings. The name of button 809 switches to "Save" or "Send" depending on the settings. This button 809 is displayed in an inactive state if the settings required for saving or sending have not been made. In FIG. 8(A), it is displayed as "Save."

[0055] The send button 810 is a button for instructing transmission of scanned form data. The edit button 711 is an edit button that displays an edit screen. This edit screen is a screen for selecting and inputting character strings in a preview image of scanned form data, and is used when character strings in the image (OCR character strings) are used for folder rules, file name rules, and metadata (described later). Therefore, it is displayed in an inactive state if the settings are not complete or if there are no properties that use OCR character strings. The delete button 812 is a button for deleting the selected scanned form data. The update button 813 is a list update button that is enabled when scanned form data that has not yet been displayed exists in the MFP linkage service 120. Pressing the update button 813 updates the scanned form list screen. By using this update button 813 as many times as necessary, it is possible to display all scanned form data currently held in the MFP linkage service 120. The tag 814 is a tag that is displayed when the scanned form data is determined to be no similar form in the similar form determination. In this case, there is no similar form for the form data corresponding to the form data 801, so there is no learned data and "Unlearned" is displayed. In Fig. 8(A), the scanned form data of the form data 801 is selected, and job properties 804 for the scanned form data of the selected form data 801 are displayed. The tag 814 indicates that the user has never scanned a form similar to the form indicated by the form data 801.

[0056] Fig. 8(B) is a screen for selecting whether to reuse transmission settings set for other existing scanned form data or to set new settings for scanned form data for which there are no similar forms (unlearned). Button 815 is a button for making new transmission settings, and when button 815 is selected, the screen shown in 8(A) above is displayed. Button 816 is a button for reusing transmission settings set for other existing scanned form data, and when button 816 is selected, the transmission setting list screen shown in Fig. 9(A) is displayed.

[0057] FIG. 9A is a diagram showing an example of a list screen of transmission settings that is displayed when existing transmission settings are reused.

[0058] List 917 shows a list of transmission settings that the user set for scanned form data that has been learned in the past. Cancel button 918 is a button for canceling the reuse of settings and returning to the screen of FIG. 8(B). OK button 919 is a button for confirming the reuse of transmission settings selected in list 917. When an unlearned form is selected in the list of scanned form data, whether the screen for selecting the reuse of transmission settings in FIG. 8(B) is displayed depends on whether there is form data that the user has learned in the past. Furthermore, if the scanned form data is not unlearned but is similar to form data that has been learned in the past, the settings in job properties 804 reflect the settings that the user previously set for that similar form data.

[0059] First, in FIG. 8(B), an operation for setting new transmission settings for unlearned scanned form data and storing the data as learning data on the screen of FIG. 8(A) will be described.

[0060] If the user has no form data that has been learned in the past, or if they select the New Settings button 815 on the screen of Fig. 8(B), the default values ​​are displayed for each setting button in the job properties 804 for unlearned scanned form data, as shown in Fig. 8(A). In Fig. 8(A), the default values ​​are displayed as follows: destination cloud service is not set, destination folder is not set, output setting is cloud compressed PDF, and file name is not set. In this way, when the No Settings button 701 in Fig. 7(A) is pressed, transmission settings such as destination cloud storage can be set one by one for unlearned form data among the form data obtained by scanning.

[0061] First, when the user presses the destination button 805 in Fig. 8A on the client PC 111, in S602 a destination editing process is sent to the MFP linkage service 120. Then, the client PC 111 receives screen information from the MFP linkage service 120 and displays the destination setting screen in Fig. 9B.

[0062] FIG. 9B is a diagram showing an example of a destination setting screen displayed on the client PC 111 according to the embodiment.

[0063] Area 901 displays information about the scanned form data so that the scanned form data to be set can be identified. Area 902 displays cloud storages 130 that can be selected as destinations. Save button 903 is a button for saving the selected cloud storage 130 as the destination. When the user selects one cloud storage from area 902 and clicks save button 903, information about the selected destination is sent from client PC 111 to MFP collaboration service 120 in S603. Then, in S604, MFP collaboration service 120 checks whether the cloud storage 130 selected by the user is accessible. If the MFP collaboration service 120 has the authentication information required for the user to access cloud storage 130, MFP collaboration service 120 saves the selected cloud storage 130 as the destination for this scanned form data. On the other hand, if the user's authentication information is not stored in MFP collaboration service 120, a message is displayed indicating that authentication to cloud storage 130 is required. Thereafter, a login screen for cloud storage 130 is displayed, and when the user logs in, authentication information required to connect to cloud storage 130 is saved in MFP collaboration service 120. After the connection between client PC 111 and cloud storage 130 is confirmed in this way, MFP collaboration service 120 saves the selected cloud storage 130 as the destination of the scanned form data. Once saving of the destination is completed in S605, client PC 111 displays the list screen of scanned form data in FIG. 8(A) with the information of the set destination cloud storage updated.

[0064] Although not shown in FIG. 8A, the set destination is reflected in the destination of form data 801 and destination button 805, as shown in FIG. 12, for example. When setting the destination with destination button 805 is completed in this way, the setting of the destination folder with button 806 changes from disabled to enabled. When the user then clicks button 806, in S606, a request for an edit screen for the destination folder is sent from client PC 111 to MFP collaboration service 120. As a result, in S607, MFP collaboration service 120 acquires folder information from cloud storage 130 using authentication information for the user to cloud storage 130. Thereafter, MFP collaboration service 120 transmits an edit screen for the destination folder, on which the acquired folder information is displayed, to client PC 111, and client PC 111 displays it.

[0065] FIG. 10A is a diagram showing an example of a destination folder setting screen displayed on the client PC 111 according to the embodiment.

[0066] Area 1001 displays the scanned form data to be edited, similar to area 901 in FIG. 9(B). Preview 1002 displays a preview of the path of the selected destination folder. Area 1003 displays folder information acquired from cloud storage 130 in a tree view or the like. The user designates a folder displayed in area 1003 to select it as the destination folder. Set button 1004 is a button for setting rules for sorting folders starting from the folder selected in area 1003. Save button 1005 is a button for saving the selected folder as the destination folder.

[0067] When the user specifies a folder in area 1003 and clicks on a setting button 1004, a folder rule setting screen shown in FIG. 10(B) is displayed.

[0068] FIG. 10B is a diagram showing an example of a folder rule setting screen displayed on the client PC 111 according to the embodiment.

[0069] The folder rule configuration area 1006 has rules in items 1007 to 1009. Item 1007 is scan information. It is used when sorting and using the name of the user who scanned, the device name, the date and time, etc. in the rule. Item 1008 is a fixed character string. It is used when using any character string for sorting. New button 1010 is a button for creating a new fixed character string. Clicking the New button 1010 displays the screen in Figure 11(A), and the character string can be entered via this screen.

[0070] FIG. 11A is a diagram showing an example of a fixed character string creation screen displayed on the client PC 111 according to the embodiment.

[0071] Area 1116 is a static character input area. In this example, the user has entered the character string "Processed." A cancel button 1117 is a button for canceling character input on this screen, and an OK button 1118 is a button for confirming static characters input on this screen.

[0072] The character string created in this way is displayed in the static character display area 1011 in FIG. 10(B) and can be used in folder rules. Item 1009 is the OCR character string. It is used when using a character string at a specific position in scanned form data. New button 1012 is a button for creating an extraction field for the OCR character string. When the New button 1012 is selected, the new OCR character string selection screen in FIG. 11(B) is displayed.

[0073] FIG. 11B is a diagram showing an example of a new selection screen for an OCR character string displayed on the client PC 111 according to the embodiment.

[0074] Although not shown in FIG. 6 , information such as the preview image and the coordinates of the OCR character string area is obtained from the MFP linkage service 120 when the New button 1012 is pressed. Preview 1119 is a preview of the scanned form data. Character string 1120 indicates the OCR character string selected by the user. Button 1121 is a button for canceling the selection of the OCR character string. Area 1122 is an area for displaying a preview of the selected OCR character string area. Area 1123 is an area for inputting the name of the OCR character string extraction field. By specifying this field name, it becomes easier to understand what character string to select when using the same rule for other form data. Cancel button 1124 is a button for canceling the OCR selection on this screen and closing the screen. OK button 1125 is a button for confirming the OCR character string selection on this screen and creating an OCR character string item. This example shows a state in which the company name in the scanned form data has been selected as an OCR character string item. The OCR character string item created in this way is displayed in the OCR character string display area, area 1013 in Fig. 10(B). Next, a method for creating a folder rule will be briefly described.

[0075] The folder rule configuration area 1006 can be defined at multiple levels. Which item is inserted at which level depends on the selected row in the folder rule configuration area 1006. Figure 10(B) shows the second level (second row) of the folder rule configuration area 1006 selected. In this state, clicking "Month" in the scan information of item 1007 inserts the "Month" item at that level. Items 1007 to 1009 can also be inserted by dragging them and dropping them onto the corresponding row. In this example, the OCR string [Company Name] and the fixed strings "underscore" and "Done" are placed in the folder name at the first level, and the scan information {Month} is placed at the second level. Here, square brackets [] indicate that the string will be replaced with the OCR string, and curly brackets {} indicate that the string is a variable that will be replaced with the scanned information. These OCR strings and variables change depending on the scanned form data, allowing you to sort scanned form data files according to the rules you set.

[0076] Then, when Save button 1005 is pressed, in S608, information about the destination folder selected by the user is sent to the MFP linkage service 120. As a result, in S609, the MFP linkage service 120 saves the received destination folder information as the destination folder for the scanned form data. The MFP linkage service 120 then sends a screen with the updated destination folder to the client PC 111. As a result, the client PC 111 displays a screen with the root folder button 806 updated on the list screen for scanned form data in FIG. 8(A), for example, as shown in FIG. 12.

[0077] Next, when the user clicks the file format button 807, in S610 a request for an output setting edit screen is sent to the MFP collaboration service 120. In response, the MFP collaboration service 120 sends the output setting edit screen to the client PC 111, and the client PC 111 displays that screen.

[0078] FIG. 12 is a diagram showing an example of a setting screen for the file format of scanned form data displayed on the client PC 111 according to the embodiment.

[0079] Area 1201 displays information about the scanned form data to be edited, similar to area 901 in FIG. 9B and area 1001 in FIG. 10A. Area 1202 displays selectable output settings. In this example, the save file format is displayed, with cloud compressed PDF selected as the default. When the user selects an output setting from area 1202 and clicks save button 1203, information about the output setting selected by the user is sent to the MFP collaboration service 120 in S611. The MFP collaboration service 120 In S612 The client PC 111 saves the received output setting information as the output setting for the scanned form data and transmits the information required for the updated screen to the client PC 111. In this way, the client PC 111 updates the file format button 807 on the list screen of scanned form data in Figure 8(A) and displays a screen with the updated output settings.

[0080] Next, when the user clicks the Edit File Name button 808, in S613 a request for a file name edit screen is sent from the client PC 111 to the MFP collaboration service 120. In response, the MFP collaboration service 120 sends the file name edit screen to the client PC 111, which displays it.

[0081] FIG. 13 is a diagram showing an example of a file name editing screen displayed on the client PC 111 according to the embodiment.

[0082] Area 1301 displays information about the scanned form data to be edited, similar to area 901 in FIG. 9B, area 1001 in FIG. 10A, and area 1201 in FIG. 12. Area 1302 is a file name rule configuration area. Unlike folder rule configuration area 1006 in FIG. 10B, there is no hierarchy, so a single line is displayed. Areas 1303 to 1305, new buttons 1306 and 1308, and areas 1307 and 1309 are the same as areas 1007 to 1013 in FIG. 10B, so their description will be omitted. These items can be used to set file name rules. Save button 1310 is a button for saving the set file name. As shown in fixed character display area 1307 and OCR character string display area 1309 in FIG. 13, items created when setting folder name rules can be reused within the same settings. 13 also shows a state in which an OCR string with a field name of "Document Name" has been added to the filename rule. The filename rule combines the OCR strings [Document Name] and [Company Name] with the fixed character "underscore" and the scan information {year}, {month}, and {day}. When the user clicks Save button 1310, in S614, information about the selected filename is sent from client PC 111 to MFP linkage service 120. Then, in S615, MFP linkage service 120 saves the filename of the selected scanned form data. Thereafter, when the user clicks Save button 809, in S616, transmission setting information is sent from client PC 111 to MFP linkage service 120.

[0083] As a result, in S617, the MFP linkage service 120 associates the setting information set up to this point, such as the destination, destination folder, output settings, file name, and character area used in the folder rule and file name rule, with a form ID (details to be described later) that uniquely indicates the type of scanned form data, and with user information, and saves it. That is, it generates or updates a setting information management table 1601 (details to be described later) as shown in Fig. 16. The timing for saving this setting information may be when the user sets the destination, file name, etc. Here, the reason for associating it with user information is because it is expected that the file name to be saved and the destination will differ for each user.

[0084] The setting information saved in association with the form ID and user information is automatically assigned based on the currently saved setting information the next time the same type of form data is determined. This eliminates the need for the same user to repeatedly make the same settings for the same type of form data. Furthermore, when saving the setting information in S615, if information with the same form ID as the form data to be saved this time is already saved in the MPF linkage service 120, the transmission setting information associated with that form ID is overwritten with the currently saved information. At this time, the user may be asked each time whether or not to overwrite.

[0085] Furthermore, if the set destination is cloud storage 130, which has metadata, in S618, MFP collaboration service 120 issues a metadata acquisition request to cloud storage 130. In response, cloud storage 130 transmits the metadata set in the destination folder to MFP collaboration service 120. Then, MFP collaboration service 120 transmits screen information that displays the confirmed transmission information and metadata to client PC 111. Then, client PC 111 displays the acquired screen information in job property area 804.

[0086] FIG. 14A shows an example of a list screen of scanned form data displayed on the client PC 111 according to the embodiment, where confirmed transmission information and metadata information are displayed in the job property area.

[0087] Here, the display of button 809 changes from "Save" to "Send." In area 1401, instead of buttons 805 to 808 in FIG. 8(A), the display has switched to displaying the corresponding setting values. This is to prevent the user from easily changing the destination, etc., after the sending settings have been finalized. Button 1402 for changing settings is a button that is pressed when editing the sending settings. When button 1402 for changing settings is pressed, setting buttons 805 to 808 are displayed again as shown in FIG. 8(A), and these items can be set again. At this time, the display of button 809 returns from "Send" to "Save."

[0088] Attribute 1403 displays attribute values ​​such as the OCR string used in the transmission settings and cloud storage metadata. In this example, areas 1404 and 1405 display the attribute values ​​of the OCR string used in the transmission settings (here, the company name and document name), and area 1406 displays the date as cloud storage metadata. For OCR strings, area 1407 displays the field name, and area 1408 displays an image of the selected OCR string. The image of the OCR string in area 1408 can be selected by clicking, etc. When selected, the preview opens again and the OCR string can be reselected. Area 1409 displays the text of the OCR result for the selected string. The user can check for errors in the OCR result by comparing the image of the OCR string in area 1408 with the OCR result in area 1409. Edit button 1410 is a button for instructing editing if the OCR result in area 1409 is incorrect. When edit button 1410 is selected, the OCR results in area 1409 are placed in an editable state, allowing the text to be edited using a keyboard or the like. Area 1411 shows date metadata, and shows an example of metadata in which the processing date is automatically entered. The type of metadata depends on the cloud storage, so it is not limited to the metadata shown as an example here. Furthermore, if the metadata is text or numeric, it may be displayed in the same way as area 1404 so that it can be selected from the OCR character string. Button 1412 is a button for editing the date, and when this button 1412 is selected, a calendar is displayed and the date can be changed. Then, when the send button 809 is selected, in S619 the client PC 111 executes a transmission process for the data to be transmitted.

[0089] As a result, in S620, the MFP collaboration service 120 generates a file according to the set output settings and file name. Next, in S621, if any settings have been changed, the MFP collaboration service 120 associates them with the formID and user information and saves the changes. At this time, the user may be prompted to choose whether to overwrite. If not overwriting, a name is entered and saved as new setting information. Then, in S622, the MFP collaboration service 120 sends the generated file to the set destination cloud storage and destination folder, adding the input metadata. When the sending is complete, the MFP collaboration service 120 notifies the client PC 111 that the sending is complete. In this way, the client PC 111 notifies the user that the sending is complete. The scanned form data that has been sent in this way is deleted from the scanned form data list screen.

[0090] Next, with reference to FIG. 8B, a case where an instruction to reuse existing settings for unlearned scanned form data is given by pressing the button 816 will be described.

[0091] When a button 816 for instructing reuse of existing settings is pressed, a screen showing a list of transmission settings previously saved in association with user information and form types is displayed, as shown in FIG. 9(A).

[0092] The user selects the settings to reuse from the transmission setting list 917 in FIG. 9A. This list 917 displays the name, destination, folder, file name, and file format settings previously assigned to the transmission settings by the user of the client PC 111. At this time, to make it easier to understand which type of form the settings were used for, the file name of the file previously sent and its image may be displayed. This will be described in detail later. A cancel button 918 is a button for canceling the settings on this screen and returning to the screen of FIG. 8B. An OK button 919 is a button for confirming the settings selected in the transmission setting list 917 as the settings to reuse. Note that the information in this list 917 may be sent from the MFP collaboration service 120 to the client PC 111 in response to a request for a list screen of scanned form data in S601. Alternatively, the information in this list 917 may be sent from the MFP collaboration service 120 to the client PC 111 in response to a request for a transmission setting list (not shown) from the client PC 111 when the button 816 instructing the reuse of existing settings is clicked.

[0093] 9A, when the user selects the transmission settings to be reused and presses the OK button 919, S616 is executed, and in S617 the current form ID is associated with the selected transmission settings and saved. After that, the screen information for the selected settings is sent from the MFP linkage service 120 to the client PC 111. The client PC 111 then displays the screen shown in FIG. 14B.

[0094] Figure 14(B) shows an example of a list screen of scanned document data displayed on client PC 111 according to the embodiment, in which the scanned document data corresponding to the aforementioned document data 801, whose transmission was completed in Figure 12(A), has been deleted from the list screen of scanned document data.

[0095] As shown in Figure 14(B), the coordinate position of the OCR character string selected in the transmission settings included in the previously stored learning data is not reflected because it is meaningless if the type of form is different. Therefore, the OCR image in area 1408 is displayed in an unselected state, and the OCR result in area 1409 is also displayed as "None." In area 1401, since there is no OCR character string, the field names [Company Name] and [Document Name] are displayed instead. Here, the user can select the OCR character string on the screen shown in Figure 15, which is displayed by selecting "Select OCR Character String" in area 1408.

[0096] FIG. 15 is a diagram showing an example of a screen displayed on the client PC 111 according to the embodiment when selecting a character string to be used as the company name in the file name of scanned form data.

[0097] The image, character area, and OCR character string of the scanned form data may be transmitted from the MFP linkage service 120 when the OCR image display area 1408 is clicked, or may be transmitted when the transmission setting information to be transmitted is confirmed in step S616. Preview image 1513 is a preview screen of unlearned scanned form data. Area 1514 shows the selected OCR character string. This example shows an example of the screen displayed when the user clicks the character string "invoice" after the screen shown in FIG. 15 is displayed. Button 1515 is a button for deselecting the OCR character string. The screen shown in FIG. 15 has two attributes, shown as areas 1404 and 1405, for inputting the OCR character string. The assignment of the selected OCR character string to this attribute is determined by the attribute selected by the user. In FIG. 15, area 1404 is selected, and the next selected OCR character string is assigned to area 1404. Save button 1516 is a button for confirming the OCR character string selected on this screen. Thereafter, when the user clicks the Send button 809, the processing shown in S619 to S622 in FIG. 6 is executed, the learning data of the type of the scanned document data is saved, and then the file of the scanned document data is sent to cloud storage 130.

[0098] In this way, the time and effort required for setting up can be reduced by reusing transmission settings previously configured for other forms for a given user and form type. Also, by associating and saving the form ID of new scanned form data with the same transmission settings, when changing the settings, the changes can be made to all form data associated with the same settings. Each process is explained in detail below.

[0099] FIG. 16 is a diagram showing an example of a setting information management table 1601 according to the embodiment.

[0100] This setting information management table 1601 is a table that stores transmission setting information set by a user for scanned forms, in association with user information and the type of form, and is stored by the data management unit 434 of the MFP linkage service 120. Rows 1602 to 1609 indicate the transmission setting information stored for each user. Number 1610 indicates the table management number. User 1611 indicates the user who will use the service. Name 1612 indicates the name given to the transmission setting by the user. Destination 1613 indicates the cloud storage 130 as the destination set by the user. Root folder 1614 indicates the root folder of the cloud storage 130 set by the user. Folder rule 1615 indicates the folder rule set by the user. This folder rule stores the type of item used in the setting (OCR text, scan information, etc.) and the combination thereof. File name rule 1616 indicates the file name rule set by the user. Like folder rule 1615, file name rule 1616 stores the type of item used in the setting and the combination thereof. File format 1617 indicates the format of the file to be saved. Metadata 1618 holds the attribute name and metadata type (text, numeric, etc.) when an OCR string is used. For items that are automatically entered, such as the processing date, there is no need to remember them, so metadata 1618 is not held in the management table. Form ID 1619 is an ID that uniquely indicates the type of form scanned by the user. OCR 1620 holds the coordinates (x, y) and area information (width, height) of the OCR string to be entered into the OCR string field when an OCR string is used in folder rule 1615, file name rule 1616, and metadata 1618.

[0101] Next, with reference to FIG. 16, an example of transmission settings held for user A will be described.

[0102] In FIG. 16, the four transmission settings stored for User A are shown in rows 1602 to 1605. These correspond to the settings displayed in the transmission setting list described in FIG. 9A. Row 1602 associates two form IDs, indicating that there are two types of forms that use the same transmission setting. Similarly, row 1603 associates one type of form, row 1604 associates three types of form, and row 1605 associates two types of form. If User A selects "Order Documents" in row 1602 in the transmission setting list of FIG. 9A for unlearned scanned form data, the learning data dependent on the form data in metadata 1618 and OCR 1620 is ignored, and the setting information for destination 1613 to file format 1617 is reused. At this time, a new form ID that uniquely represents the unlearned form data is associated with row 1602. The area information for the OCR character string has not yet been specified, so it is empty. Therefore, as described above with reference to FIG. 14B, the display is displayed without the OCR character string set. 15 screen and clicks the send button 809, the information on the specified character area is stored in the OCR 1620. In this way, the user can select whether to share and use the same send settings for different types of form data.

[0103] Next, we will explain what happens when a user scans a form similar to formID "u3n4-azdt-48k8-ukci-5kpe." In this case, a screen reflecting all of the information in destination 1613 through OCR 1620 in FIG. 16 is displayed, as shown in FIG. 14(A). In other words, when a similar form is scanned, the transmission settings and OCR strings shown in the setting information management table 1601 are always reflected. If, after displaying the screen reflecting the settings shown in FIG. 14(A), the user clicks the Change Settings button 1402 to change the settings and then saves the changes, the transmission settings associated with the formID for which the changes were saved are overwritten. For example, if the transmission settings for formID "u3n4-azdt-48k8-ukci-5kpe" are changed and saved, the formID "cb2b-4asa-4cbe-bg8d-yjrr" associated with those settings is also affected.

[0104] In this way, form data that share the same settings can be changed all at once, eliminating the need to change settings for each form. If the setting change involves adding an OCR string field, the character area information for the added OCR string will be blank for other form data. Therefore, the next time similar scanned form data is scanned, the character area information for the OCR string will be blank, and the user will have to select the OCR string on the screen shown in Figure 15.

[0105] In the above description, an example was described in which the settings were changed and then overwritten and saved. However, the user may be allowed to choose whether to overwrite or save as a different transmission setting when pressing the save button 809 (not shown). If the user chooses to save as a different transmission setting, the form ID is deleted from the originally associated setting in the setting information management table 1601 and added to the management table as a new different transmission setting. Alternatively, when the user clicks the change setting button 1402 in FIG. 14(A), a screen may be displayed (not shown) that prompts the user to choose whether to reconfigure using other settings. If the user chooses to reconfigure using other settings, the screen in FIG. 9(A) is displayed again, prompting the user to select the settings to reuse. Thereafter, the form ID of the changed form is deleted from the original setting information management table 1601 and saved in association with the newly associated user's transmission setting. As such, it is important to determine which transmission settings to associate, so when displaying the list of transmission settings on the screen in Figure 9(A), it is easier for the user to determine which type of form data the transmission settings were used with in the past. For example, if you associate them with the formID in Figure 16 and store each file name and image of previously saved form data as an example, the file name and image can be displayed on the screen in Figure 9(A) as an example of form data that uses the same settings. This makes it easier for the user to determine which form data should use the same settings to operate unlearned form data.

[0106] 17 is a flowchart illustrating image analysis processing executed by image processing unit 432 of MFP collaboration service 120 according to an embodiment. Each process shown in this flowchart is realized by CPU 311 loading into RAM 313 and executing a program stored in ROM 312 or HDD 314 of MFP collaboration service 120. This flowchart explains the details of the processes of S514 to S516 executed by image processing unit 432 after image processing unit 432 of MFP collaboration service 120 receives an image processing request from request control unit 431 in S512 of FIG.

[0107] First, in S1701, the CPU 311 functions as the image processing unit 432, analyzes the character areas of the form image data obtained by scanning in S509, and acquires a group of character areas from the form data. Next, the process proceeds to S1702, where the CPU 311 performs character recognition processing on all character string areas detected by the analysis in S1701. Next, the process proceeds to S1703, where the CPU 311 determines whether the form is similar using the information detected in S1701 and S1702. This similarity determination is made by comparing the layout information of image data obtained in a previous scan with the layout information of image data obtained in the current scan, using information such as the layout of the character areas. If there is image data obtained by a previous scan that has a similar layout of character areas, it is determined that a similar form exists. In other words, the process determines whether the setting information management table 1601 of the MFP linkage service 120 holds transmission setting information for the same form ID as the form ID of the form data analyzed this time.

[0108] If similar form data is found in S1704 as a result of this determination, the process proceeds to S1705. In S1705, the CPU 311 generates analysis result information from the setting information stored in association with the similar form (i.e., the transmission setting information shown in the setting information management table 1601 stored in association with the form ID in S616 of FIG. 6, etc.), and proceeds to S1708. This analysis result information is information about the character strings in the image used for the transmission settings set in the similar form. Information about the character areas used in the folders, file names, and metadata as OCR character strings in the similar form is obtained, and character areas in similar positions in the image data obtained by this scan are detected, and the character strings in those areas are obtained.

[0109] On the other hand, if no similar form is found in S1704, the process proceeds to S1706. In S1706, the CPU 311 newly registers the image data obtained by the current scan as new form data (i.e., no similar form). The registered information is used as one piece of form information to determine whether or not the form is similar the next time the analysis process of FIG. 17 is performed. The process then proceeds to S1707, where the CPU 311 generates analysis result information, and the process proceeds to S1708. Here, since there are no similar forms, only information indicating that the form has not been learned is generated. Then, in S1708, the CPU 311 saves the analysis result information generated in S1705 or S1707 in the HDD 314 of the MFP linkage service 120.

[0110] When this process determines that the scanned form data is similar to form data obtained in a previous scan, the system obtains information about the text area in the image used in the transmission settings associated with the similar form and saved.The system then detects the text area, obtains the character string in that area, and acquires the transmission settings for the scanned form data.

[0111] Next, we will explain the process from when a list screen of scanned form data to be sent is requested in S601, until the MFP collaboration service 120 acquires the information necessary to display the list screen of scanned form data and sends it to the client PC 111.

[0112] 18 is a flowchart describing the processing by which the MFP collaboration service 120 according to the embodiment acquires information for displaying a list screen of scanned form data and transmits it to the client PC 111. The processing shown in this flowchart is realized by the CPU 311 loading into the RAM 313 a program stored in the ROM 312 or HDD 314 of the MFP collaboration service 120 and executing the program. When the MFP collaboration service 120 receives a request to acquire a list screen of scanned form data from the client PC 111 in S601, the MFP collaboration service 120 references the list of scanned form data currently held by the MFP collaboration service 120 and the analysis result information thereof. The information referenced here corresponds to the user information authenticated by the MFP collaboration service 120.

[0113] First, as shown in S1801 to S1806, this process is repeated the number of times the number of scanned form data corresponding to the user information currently held by the MFP linkage service 120 is equal to. In S1802, the CPU 311 functions as the display control unit 435 and determines whether there is a similar form in the scanned form data. If there is no similar form, that is, if the scanned form data is unlearned, the process proceeds to S1803, where initial values ​​for new settings are obtained, and the process proceeds to S1805. Then, in S1805, the CPU 311 saves the initial values ​​as settings for the scanned form data.

[0114] On the other hand, if it is determined in S1802 that a similar form exists, the process proceeds to S1804, where the CPU 311 obtains setting information from the analysis result information stored in association with the similar form, and the process proceeds to S1805, where the setting information is stored in association with the scanned form data.

[0115] 6 and 18, if there are initial values ​​for the metadata in the cloud storage 130, or if separate settings are made so that information that can be referenced by the MFP linkage service 120 is entered, then in S1805, that information is also saved as setting information for the scanned form data. Note that if the connected cloud storage service 130 is no longer accessible or if there is no destination folder, the setting value may not be saved and the location of the error may be notified. Once processing for all scanned form data has been completed in S1801 to S1806, the process proceeds to S1807.

[0116] In S1807, the CPU 311 determines whether there are any transmission settings that can be reused by the user. That is, it is determined whether there are any transmission settings associated with the user information in the setting information management table 1601, and if there are any such transmission settings, the process proceeds to S1808, where the CPU 311 acquires a list of existing transmission settings and proceeds to S1809. On the other hand, if the CPU 311 determines in S1807 that there are no transmission settings that can be reused by the user, the process proceeds to S1809, where the CPU 311 transmits information including the setting values ​​saved for the form data to the client PC 111.

[0117] By this process, if there is form data similar to the scanned form data, the client PC 111 can present the setting information set for the similar form on the list screen of the scanned form data.

[0118] Next, when the Save button 809 on the list screen of scanned form data is clicked, or when the OK button 919 on the transmission setting list in Fig. 9(A) is clicked, the setting information for the scanned form data is saved. In other words, the information in the setting information management table 1601 is updated, and from the next time onwards, the updated setting information is reflected in similar scanned form data.

[0119] 19 is a flowchart illustrating processing by the MFP collaboration service 120 according to an embodiment to save setting information for scanned form data. The processing shown in this flowchart is realized by the CPU 311 loading a program stored in the ROM 312 or HDD 314 of the MFP collaboration service 120 into the RAM 313 and executing the program.

[0120] When the save button 809 is clicked on the screen listing scanned form data, in S1901 the CPU 311 determines whether the form data has the same form ID as that in the setting information management table 1601. If the form data has a form ID that is not in the setting information management table 1601, the process proceeds to S1902, where the CPU 311 determines whether the settings in the screen of FIG. 9A have been reused. The determination of whether the settings have been reused may be made based on whether the OK button 919 in the screen of FIG. 9A has been pressed, or the determination of whether the settings have been reused may be stored in the client PC 111 or the like. If it is determined that the settings have not been reused, the process proceeds to S1903, where the CPU 311 saves the new transmission setting information in the setting information management table 1601 in association with the user information and the new form ID, and then the process proceeds to S1909.

[0121] On the other hand, if it is determined that the settings are being reused on the screen of FIG. 9A, the process proceeds to step S1913, where the CPU 311 stores the new form ID in the setting information management table 1601 in association with the reused transmission settings, and then the process proceeds to step S1909.

[0122] On the other hand, if the CPU 311 determines in S1901 that the form ID is the same as that in the setting information management table 1601, the process proceeds to S1904, where it determines whether the transmission settings have been changed from those already registered in the setting information management table 1601. If it determines in S1904 that there have been no changes, the process proceeds to S1909 without performing the save process.

[0123] On the other hand, if it is determined in S1904 that the transmission settings have been changed, the process proceeds to S1905. In S1905, the CPU 311 transmits to the client PC 111 a screen for confirming whether to overwrite and update the transmission settings or to save them as new transmission settings in the setting information management table 1601, and prompts the user to select. Then, the process proceeds to S1906, and if the user on the client PC 111 selects to overwrite and save, the process proceeds to S1907, where the CPU 311 overwrites and saves the existing transmission settings associated with the current formID, and proceeds to S1909. On the other hand, if the user selects to save as different transmission settings in S1906, the process proceeds to S1908, where the CPU 311 saves as different transmission settings, and proceeds to S1909.

[0124] In S1909, the CPU 311 determines whether the cloud storage 130 where the current save was executed is a storage containing metadata. If it is determined that there is no metadata, the process proceeds to S1912, where the save result is sent to the client PC 111, and the process is completed. On the other hand, if it is determined in S1909 that the storage contains metadata, the process proceeds to S1910, where the CPU 311 acquires the metadata from the cloud storage service 130. Then, in S1911, the CPU 311 sets the setting information in the metadata, if there is any setting information to be set in the metadata. This is updated when the character area of ​​the OCR character string has been determined or when there is a numerical value that can be processed automatically. Then, the process proceeds to S1912, where the CPU 311 sends the save result to the client PC 111. 14A or 14B, reflecting the data received from the MFP linkage service 120. If the OK button 919 is pressed in the transmission setting list of FIG. 9A, the processing flow is the same as when there is no formID registered in the setting information management table 1601 in S1901. Then, in S1902, it is determined that the settings are being reused, and the process proceeds to S1913, where processing is executed to associate the formID with the reused transmission settings and save them.

[0125] Next, the processing of the MFP linkage service 120 when a button 1402 for changing the settings of the destination cloud storage service and destination folder is selected on the screen of FIG. 14 will be described.

[0126] Fig. 20 is a flowchart for explaining the processing performed by the MFP collaboration service 120 according to the embodiment when the button 1402 for changing the settings is pressed on the screen of Fig. 14. The processing shown in this flowchart is realized by the CPU 311 loading into the RAM 313 and executing a program stored in the ROM 312 or HDD 314 of the MFP collaboration service 120.

[0127] When the user presses button 1402 to change the destination settings, in S2001, CPU 311 causes client PC 111 to display a message (not shown) asking whether it is OK to clear the metadata. Next, the process proceeds to S2002, where CPU 311 determines whether the user of client PC 111 has instructed OK (not shown), i.e., whether it is OK to clear the metadata. If it is OK to clear the metadata, the process proceeds to S2003, where CPU 311 discards the set metadata. In other words, it deletes the metadata acquired from cloud storage service 130 from the settings of the scanned form data. Then, the process proceeds to S2004, where CPU 311 transmits screen update information to client PC 111. When client PC 111 receives this screen update information, the screen changes as follows: The display of the metadata is deleted from job property area 804 in FIG. 8A. Then, the display of button 809 is changed from "Send" to "Save." Then, the display of the setting values ​​in the setting information display area 1401 in Fig. 14 and the button 1402 for changing the settings return to buttons 805 to 808 in Fig. 8(A). On the other hand, if the user determines in S2002 not to clear the metadata, this process ends immediately.

[0128] In step S2004, a screen may be displayed (not shown) that prompts the user to select whether to reuse the existing settings and change the settings. If the user selects to reuse the existing settings, the form ID to be edited is deleted from the setting information management table 1601, and the list of existing transmission settings shown in Fig. 9(A) is displayed. If the user selects the transmission settings to reuse, the same processing is executed as when the OK button 919 is selected in the transmission setting list described in Fig. 19.

[0129] 21 is a flowchart illustrating the process in which the MFP collaboration service 120 according to the embodiment generates a file using information set in scanned form data and transmits the file to a set destination. This flow corresponds to the process from S619 to S622 in FIG. 6. The process shown in this flowchart is realized by the CPU 311 loading a program stored in the ROM 312 or HDD 314 of the MFP collaboration service 120 into the RAM 313 and executing the program.

[0130] When the save button 809 is pressed on the scanned form data list screen, the process proceeds to S2101, where the CPU 311 saves the setting information indicated in the job properties 804 to the scanned form data. Next, the process proceeds to S2102, where the CPU 311 generates a file with the set output settings and file name. The process then proceeds to S2103, where the CPU 311 functions as the cloud storage access unit 433, and sends the file generated in S2102 to the set destination cloud storage folder. At this time, if there are any metadata setting values, the setting values ​​are also sent at the same time. In this way, the scanned form data is saved in the cloud storage 130.

[0131] Next, the process proceeds to S2104, where the CPU 311 determines whether the transmission setting is newly registered in the setting information management table 1601. If it is determined that the transmission setting is newly registered, the process proceeds to S2105; if not, the process proceeds to S2107. In S2105, the CPU 311 transmits screen information for entering the name of the transmission setting to the client PC 111, and prompts the user to enter the name of the current transmission setting. The process then proceeds to S2106, where the CPU 311 receives the name entered by the user from the client PC 111, associates it with the transmission setting, and stores it in the setting information management table 1601, before proceeding to S2107.

[0132] In S2107, CPU 311 determines whether any information has been updated since Save button 809 was clicked. This mainly applies to changes to the character area of ​​the OCR character string. If it is determined that the character area of ​​the OCR character string has been changed by the time of transmission, the process proceeds to S2108; otherwise, the process ends. In S2108, CPU 311 updates the associated form ID in setting information management table 1601 and ends the process.

[0133] This allows you to assign a name to the newly entered transmission settings and manage them in the settings information management table. Also, for the next similar form data, you can use the character string in the same area as the updated OCR character string.

[0134] Next, a case where the user selects settings to be reused in Fig. 9(A) and then changes some of the settings will be described. In the example above, it was explained that Fig. 14(B) is displayed after the settings to be reused are selected in Fig. 9(A), but the settings may be displayed in a state where they are reflected on the screen where settings can be changed in Fig. 8(A). In this case, the settings can be changed without pressing the button 1402 for changing the settings in Fig. 14(B). Therefore, for users who often reuse existing settings, change some of the settings, and save them as different transmission settings, it is convenient to be able to skip the screen in Fig. 14(B).

[0135] After changing some of the settings from the state in which the settings are reflected on the screen in Fig. 8(A), when the save button 809 is pressed, it is inconvenient that the confirmation of whether to overwrite and save is displayed every time in S1905 in Fig. 19. For this reason, it is possible to reuse the settings for unlearned form data, and if some of the settings have been changed, skip the processing of S1905 and execute the processing of S1907 to save as separate form data.

[0136] Furthermore, it is also possible to manage unchanged transmission settings as common settings, and only changed settings as individual settings. For example, if all cloud storages 130 are set to the same common settings, it is convenient because if the cloud storage is changed, it can be changed all at once. Also, if only the destination is set as a common setting, changing the destination for one scanned form data can also change the destination for other form data. In this case, other settings that are not shared, such as file name rules, will not be affected by the change. This can be achieved, for example, by associating form IDs with settings such as destinations, root folders, and folder rules in the setting information management table 1601.

[0137] As described above, according to the embodiment, when a user sets up the sending of image data to a cloud service, the user can reflect the settings of similar image data that the user previously made, thereby improving the operability of the setting. Furthermore, the user can reuse only the sending settings associated with other image data that the user previously made for the sending settings of new image data, thereby improving the operability of the setting change.

[0138] (Other embodiments) The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC) that realizes one or more functions.

[0139] The present invention is not limited to the above-described embodiments, and various modifications and variations can be made without departing from the spirit and scope of the present invention. Therefore, the following claims are appended to apprise the public of the scope of the present invention. [Explanation of symbols]

[0140] 110...MFP, 111...client PC, 120...MFP linkage service, 130...cloud storage, 1601...setting information management table

Claims

1. A server that can access a cloud service, a storage means for storing the type of image data and a transmission setting for transmitting the image data to the cloud service in association with each other; a selection screen presenting means for presenting a list of the transmission settings stored in the storage means to the information processing device and presenting a selection screen on the information processing device for allowing the user to select a transmission setting to be used for the image data to be newly transmitted from the list, when the type of image data to be newly transmitted is not similar to any of the types of image data stored in the storage means and an instruction to reuse the transmission setting stored in the storage means is given by a user of the information processing device; and a setting screen presenting means for presenting to the information processing device, when a transmission setting is selected by the user via the selection screen, a setting screen for making transmission settings for the new image data to be transmitted, in a state where the selected transmission settings, excluding settings related to character strings to be OCR-generated, are reflected; the determination of whether the type of the image data to be newly transmitted is similar to any of the types of image data stored in the storage means is made by comparing the layout information of character regions of the image data to be newly transmitted and the image data stored in the storage means; The server is characterized in that the storage means stores the type of image data to be newly sent in association with the transmission setting selected via the selection screen and stored in the storage means.

2. The server described in claim 1, characterized in that the transmission settings stored in the storage means include settings regarding at least one of the cloud service to which the image data to be transmitted will be sent, rules regarding the destination folder, rules regarding the file name of the image data, and the file format in which the image data will be saved.

3. 3. The server according to claim 1, wherein the server is capable of communicating with an image forming apparatus, and the image data to be newly transmitted is image data generated by scanning an original document with the image forming apparatus.

4. A server as described in any one of claims 1 to 3, characterized in that when the type of image data to be newly sent is similar to the image data stored in the storage means, the setting screen presentation means presents to the information processing device a setting screen for making transmission settings for the image data to be newly sent, reflecting the transmission settings associated with the type of similar image data and stored in the storage means.

5. A server as described in any one of claims 1 to 4, characterized in that when a setting screen for making transmission settings for the new image data to be sent is presented to the information processing device by the setting screen presentation means, reflecting the transmission settings selected by the user via the selection screen, excluding settings related to the character string to be OCR, the setting screen accepts instructions from the user to make settings related to the character string to be OCR.

6. the server further comprises an authentication means for authenticating a user of the information processing device; The server according to any one of claims 1 to 5, characterized in that the storage means stores the type of image data, transmission settings for transmitting the image data to the cloud service, and information about the user in association with each other.

7. The server described in claim 6, characterized in that when the type of image data to be newly sent is not similar to any of the types of image data stored in the storage means and an instruction to reuse the transmission settings stored in the storage means is given by the user of the information processing device, the selection screen presentation means presents a list of the transmission settings stored in the storage means in association with information of the user authenticated by the authentication means, and presents a selection screen to the information processing device to allow the user to select from the list the transmission settings to be reused for the image data to be newly sent.

8. A server as described in any one of claims 1 to 7, characterized in that when the user changes the transmission settings on the setting screen to be different from the reflected transmission settings, the server further has a means for presenting a screen to the information processing device that allows the user to choose whether to reflect the changed transmission settings in the original transmission settings stored in the storage means or to store them as separate transmission settings.

9. The server described in claim 8 is characterized in that after presenting the setting screen to the information processing device for setting transmission settings for the new image data to be transmitted, reflecting the transmission settings selected by the user via the selection screen, excluding the settings related to the character string to be OCRed, if the user changes the transmission settings on the setting screen to be different from the transmission settings in the reflected state, the screen for selecting whether to store the different transmission settings is omitted and the different transmission settings are stored in the storage means.

10. A control method for controlling a server that can access a cloud service, comprising: a storage step of storing the type of image data and a transmission setting for transmitting the image data to the cloud service in association with each other; a selection screen presenting step of presenting a list of the transmission settings stored in the storage step to the information processing device and presenting a selection screen on the information processing device for allowing the user to select a transmission setting to be used for the image data to be newly transmitted from the list, when the type of image data to be newly transmitted is not similar to any of the types of image data stored in the storage step and an instruction to reuse the transmission setting stored in the storage step is given by a user of the information processing device; a setting screen presenting step of presenting, when a transmission setting is selected by the user via the selection screen, a setting screen for making transmission settings for the new image data to be transmitted, on the information processing device, in a state where the selected transmission settings, excluding settings related to character strings to be OCR-generated, are reflected; the determination of whether the type of the image data to be newly transmitted is similar to any of the types of image data stored in the storage step is made by comparing the layout information of character regions of the image data to be newly transmitted and the image data stored in the storage step; Further, the control method is characterized in that the server is controlled so as to store the type of image data to be newly transmitted in association with the transmission setting selected via the selection screen and stored in the storage process.

11. A program for causing a computer to function as all of the means of the server according to any one of claims 1 to 9.

Images