Document scanning device and document management system

Abstract

To make it possible, when storing a scanned document in a cloud, to easily store the scanned document into a location intended by a user, on the basis of an operation history of a storage destination.SOLUTION: A document scanning device is connected to a cloud storage using a network, transmits scanned image data to the cloud storage, and stores the data into the cloud storage as an image data file. The document scanning device includes: means for acquiring a cloud history, an access history related to a storage location of the image data file stored in the cloud storage; and means for displaying a scanning setting screen for setting the storage location in the cloud storage for the image data file for the scanned image data. Information on the cloud history acquired from the cloud storage is made to be reflected in an input field of the storage location for the image data file on the scanning setting screen.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to a document scanning device and a document management system, and more particularly to a document scanning device and a document management system that are suitable for easily saving scanned documents in a location intended by a user when scanning documents and saving them in the cloud. [Background technology]

[0002] Multifunction peripherals (MFPs), the mainstay of office work, have traditionally provided the ability to scan paper documents, convert them into digital data, and store the digital documents in cloud storage for document management. When specifying a storage destination in cloud storage, for example, a destination folder is selected on the MFP display screen and set as the storage destination.

[0003] A technology for specifying a storage location in cloud storage (document management server) for a document scanned by an MFP in this way is disclosed, for example, in Patent Document 1. Patent Document 1 discloses a technology for determining a destination folder based on an operation history. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-247814 Summary of the Invention [Problem to be solved by the invention]

[0005] The system in Patent Document 1 automatically corrects the destination folder based on the folder operation history when the destination folder is moved to another folder or otherwise changed. This is said to reduce the sender's effort even when there is a change in the folder on the document management server where the document is stored. However, because the system in Patent Document 1 automatically changes the destination of scanned documents based on the folder operation history, the user cannot select the intended folder from the operation history and set it as the destination. This raises the risk of documents being stored in an unintended location.

[0006] The object of the present invention is to provide a document scanning device and document management system that, when scanning a document and saving it in the cloud, can easily save the scanned document in the location intended by the user based on the operation history of the storage destination. [Means for solving the problem]

[0007] The configuration of the document scanning device of the present invention is preferably a document scanning device that is connected to cloud storage via a network, transmits scanned image data to the cloud storage, and stores it as an image data file in the cloud storage, and has a means for acquiring a cloud history, which is an access history regarding the storage location of the image data file stored in the cloud storage, and a means for displaying a scan settings screen for setting the storage location in cloud storage of the image data file of the scanned image data, and is configured to reflect the cloud history information acquired from the cloud storage in the input field for the storage location of the image data file on the scan settings screen. [Effects of the Invention]

[0008] According to the present invention, a document scanning device and a document management system can be provided that, when scanning a document and saving it in the cloud, can easily save the scanned document in the location intended by the user based on the operation history of the storage destination. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is an overall configuration diagram of a document management system. [Figure 2] FIG. 2 is a functional configuration diagram of a document management system. [Figure 3] FIG. 1 is a hardware configuration diagram of an MFP. [Figure 4] FIG. 2 is a diagram illustrating the hardware configuration of an MFP collaboration server. [Figure 5] FIG. 1 is a hardware configuration diagram of cloud storage. [Figure 6] FIG. 10 is a diagram illustrating an example of a history data table held by the cloud storage. [Figure 7] FIG. 10 illustrates an example of a history data table held by the MFP cooperation server. [Figure 8] FIG. 10 is a sequence diagram showing a series of processes for converting an image scanned by an MFP into a file and storing it in cloud storage. [Figure 9] FIG. 10 is a diagram illustrating an example of a main screen. [Figure 10] FIG. 10 is a diagram illustrating an example of a login screen. [Figure 11] FIG. 10 is a diagram showing an example of a scan setting screen (part 1). [Figure 12] FIG. 10 is a diagram showing an example of a scan setting screen (part 2). [Figure 13] 10 is a flowchart showing detailed processing of user interface processing using cloud history in the MFP. [Figure 14] FIG. 10 is a sequence diagram showing a series of processes for accessing cloud storage from a client PC 140. [Figure 15] FIG. 10 is a diagram illustrating an example of a Web upload screen. [Figure 16] 10 is a flowchart showing detailed processing of user interface processing using cloud history in the MFP. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, each embodiment of the present invention will be described with reference to FIGS.

[0011] [Embodiment 1]

[0012] Hereinafter, the first embodiment will be described with reference to FIGS.

[0013] First, the configuration of a document management system according to the first embodiment will be described with reference to FIGS.

[0014] In this embodiment, a multifunction peripheral (MFP) is used as an example of a document scanning device, and a document management system in which documents are scanned by the document scanning device and stored in cloud storage will be described. First, the overall configuration of the document management system will be explained using FIG. FIG. 1 is a diagram showing the overall configuration of a document management system.

[0015] 1, the document management system of this embodiment includes an MFP 110, an MFP linkage server 120, a cloud storage 130, and a client PC 140. The MFP 110 is connected via a LAN (Local Area Network) so as to be able to communicate with the MFP linkage server (client device linkage server) 120, which provides various services over the Internet 5, and the cloud storage 130.

[0016] The MFP 110 is a multifunction peripheral with multiple functions such as a scanner, printer, and fax machine. The MFP linkage server 120 is a server that links with the MFP 110, storing image data files scanned by the MFP 110 on its own server and relaying the image data scanned by the MFP 110 to transfer it to cloud storage 130. The cloud storage 130 is a server that can store files via the Internet 5 and retrieve files using a web browser. The client PC 140 is an information processing device that allows a user to receive services such as downloading and displaying image data files stored in the cloud storage 130.

[0017] The document management system of the present embodiment is configured to include MFP 110, MFP linked server 120, cloud storage 130, and client PC 140, but is not limited to this. For example, MFP 110 may also serve as MFP linked server 120. Furthermore, MFP linked server 120 may be connected to a server on a LAN rather than on Internet 5. Furthermore, cloud storage 130 may be replaced by a mail server or the like, and scanned image data files may be attached to emails and sent.

[0018] Next, the functional configuration of the document management system will be described with reference to FIG. FIG. 2 is a functional configuration diagram of the document management system. As shown in Fig. 2, the MFP 110 is roughly divided into two parts: a native function unit 410 and an additional function unit 420. While the functional units included in the native function unit 410 are provided as standard in the MFP 110, the additional function unit 420 is a functional unit executed by application software additionally installed on the MFP 110. The functions of the additional function unit 420 are executed by, for example, Java (registered trademark)-based application software, and a system administrator can easily add functions to the MFP 110 by executing the application software. Note that other additional applications not shown in Fig. 2 may be installed on the MFP 110.

[0019] The native function unit 410 has a scan execution unit 411 and an image data storage unit 412. The scan execution unit 411 is a functional unit that receives a scan request including scan setting information from a scan instruction unit 422 and generates scanned image data. The image data storage unit 412 is a functional unit that stores image data scanned by the scan execution unit 411.

[0020] Additional function unit 420 includes a display control unit 421, a scan instruction unit 422, and an integrated service request unit 423. Display control unit 421 is a functional unit that displays a UI screen on the liquid crystal display device of MFP 110 to accept user operations. Display control unit 421 displays UI (user interface) screens, such as a UI for entering authentication information for accessing MFP linked server 120, scan settings, scan start operations, and a preview screen. Scan instruction unit 422 is a functional unit that requests scan processing from scan execution unit 411 along with scan settings according to user instructions entered via the UI screen. Integrated service request unit 423 is a functional unit that requests various processes from MFP linked server 120. For example, it requests login, analysis of scanned images, and transmission of scanned images. Protocols such as REST (Representational State Transfer) and SOAP (Simple Object Access Protocol) are used for communication with MFP linked server 120, although other communication protocols may also be used.

[0021] When a document is scanned by the MFP 110, the scan execution unit 411 reads the document as an image and generates image data. The generated scanned image data is sent to the image data storage unit 412. At that time, the scan execution unit 411 sends a scanned image identifier that uniquely identifies the stored scanned image data to the scan instruction unit 422. The scanned image identifier is an identifier consisting of a string of numbers, symbols, alphabets, etc. that uniquely identifies an image scanned by the MFP 110. The image data storage unit 412 stores the scanned image data received from the scan execution unit 411 in a storage device such as an HDD.

[0022] Scan instruction unit 422 acquires, from image data storage unit 412, scan image data corresponding to the scan image identifier received from scan execution unit 411. Scan instruction unit 422 then requests cooperation service request unit 423 to instruct MFP cooperation server 120 to process the acquired image data.

[0023] The MFP linkage server 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 .

[0024] The request control unit 431 is a functional unit that receives requests from external devices and controls each unit in accordance with the requests. The request control unit 431 stands by in a state where it can receive requests from external devices, and upon receiving a processing request, instructs the image processing unit 432, cloud storage access unit 433, and data management unit 434 to perform processing as appropriate in accordance with the request.

[0025] The image processing unit 432 is a functional unit that performs OCR (Optical Character Recognition) processing on image data and performs file conversion processing. The cloud storage access unit 433 is a functional unit that issues processing requests to the cloud storage 130. The cloud services provided by the cloud storage 130 generally communicate using protocols such as REST or SOAP, and publish various interfaces for saving files in the cloud storage and retrieving saved files. The cloud storage access unit 433 operates the cloud storage using the published cloud storage interface.

[0026] Data management unit 434 holds user information, various setting data, and the like managed by MFP link server 120. Display control unit 435 is a functional unit that controls the display on client PC 140 connected via the Internet. Display control unit 435 receives a request from a web browser running on client PC 140 and transmits screen configuration information (HTML, CSS, etc.) required for screen display. The user can check user information registered in MFP linked server 120 and change scanning settings via the screen displayed by the web browser.

[0027] Cloud storage 130 has external I / F unit 441 and storage access unit 442. External I / F unit 441 is a functional unit that performs interface processing with external devices such as MFP linked server 120 and client PC 140. Storage access unit 442 is a functional unit that receives requests from external devices and accesses and sets data stored in a storage device.

[0028] Client PC 140 has a user instruction acceptance unit 451, a scan setting unit 452, and a cloud storage access unit 453. User instruction acceptance unit 451 is a functional unit that accepts instructions related to scanning and file processing through commands or on-screen operations. Scan setting unit 452 is a functional unit that makes settings related to document scanning for MFP linkage server 120. Cloud storage access unit 453 is a functional unit that makes file uploads and downloads to cloud storage and other settings.

[0029] Next, the hardware configuration of the document management system will be described with reference to FIGS. FIG. 3 is a diagram showing the hardware configuration of the MFP. FIG. 4 is a diagram illustrating the hardware configuration of the MFP cooperation server. FIG. 5 is a hardware configuration diagram of the cloud storage.

[0030] As shown in FIG. 3, the MFP 110 is configured with the following hardware components: a control device 210, an operation device 220, a printer 221, a scanner 222, and a modem 223.

[0031] The control device 210 is composed of the following devices and controls the overall operation of the MFP 110. The CPU (Central Processing Unit) 211 reads control programs stored in a ROM (Read Only Memory) 212 and executes and controls various functions of the MFP 110, such as reading, printing, and communication. The RAM (Random Access Memory) 213 functions as the CPU 211's main memory and is used as a temporary storage area such as a work area. In this embodiment, one CPU 211 executes each process using the RAM 213 as the main memory and the ROM 212 as the programs. However, this is not limited thereto. For example, multiple CPUs 211 may be used, and some of the control programs may be executed using programs stored in the ROM 212, and some of the application programs may be executed using programs stored in the HDD 214. The HDD (Hard Disk Drive) 214 is a large-capacity storage device that stores image data and various programs. In this embodiment, the HDD 214 stores a user management table 701 and image data 702 as data. The user management table 701 is a table for managing information on users who log in to the system. The image data 702 is image data captured by the scanner 222.

[0032] The operation I / F 215 is an interface that connects the operation device 220 and the control device 210. The operation device 220 may include a touch panel, a keyboard, or the like, and receives operations, inputs, and instructions from a user. The printer I / F 216 is an interface that connects the printer 221 and the control device 210. Image data to be printed is transferred from the control device 210 to the printer 221 via the printer I / F 216 and printed on a recording medium such as paper. The scanner I / F 217 is an interface that connects the scanner 222 and the control device 210. The scanner 222 reads a document placed on a document tray (not shown) or an automatic document feeder (ADF) (not shown) to generate image data, which is then input to the control device 210 via the scanner I / F 217. The MFP 110 can print (copy) the image data generated by the scanner 222 from the printer 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 device 210. The modem 223 transmits image data via facsimile communication with a facsimile device on a fixed-line telephone network (PSTN: Public Switched Telephone Network). The network I / F 219 is an interface that connects the control device 210 of the MFP 110 to a network. The MFP 110 transmits image data and information to various servers and cloud storages on the Internet and receives various types of information via the network I / F 219.

[0033] As shown in FIG. 4, the MFP linked server 120 includes a CPU 311, a ROM 312, a RAM 313, a HDD 314, and a network I / F 315.

[0034] CPU 311 controls the overall operation by reading out control programs stored in ROM 312 and executing various processes. RAM 313 functions as the main memory of CPU 311 and is used as a temporary storage area such as a work area. HDD 314 is a mass storage unit that stores image data and various programs. In this embodiment, HDD 314 stores an image data file 711 and a history data table 712 as data. Image data file 711 is a file that stores image data received from MFP 110 and is a file of image data to be sent to cloud storage 130. History data table 712 is a table that holds history information stored in cloud storage (details will be described later). Network I / F 315 is an interface that connects MFP collaboration server 120 to a network. MFP collaboration server 120 receives processing requests from other devices (such as MFP 110) via network I / F 315 and sends and receives various information.

[0035] As shown in Fig. 5, cloud storage 130, like MFP linked server 120, is composed of CPU 611, ROM 612, RAM 613, HDD 614, and network I / F 615. The function of each piece of hardware is the same as that of MFP linked server 120 described in Fig. 4. HDD 614 of cloud storage 130 stores image data file 721 and history data table 722. Image data file 721 is a file that stores image data files transmitted from MFP linked server 120 in cloud storage 130. History data table 711 is a table that stores the history of storing image data files in cloud storage 130 (details will be described later).

[0036] Although not shown, client PC 140 also has the same hardware configuration as MFP link server 120, which is a typical information processing device.

[0037] Next, the structure of the history data table will be described with reference to FIGS. FIG. 6 is a diagram illustrating an example of a history data table held by the cloud storage. FIG. 7 illustrates an example of a history data table held by the MFP linked server.

[0038] The history data table 722 is a table held by the cloud storage 130. As shown in Fig. 7, the history data table 722 includes fields for a history ID 722a, a source IP address 722b, a storage folder name 722c, a storage file name 722d, a creation date and time 722e, an update date and time 722f, an access date and time 722g, and a user ID 722.

[0039] The history ID 722a stores a unique identifier for identifying a history entity. The source IP 722b stores the source of the image data file or the IP address of the device that accessed the cloud storage 130. The storage folder name 722c stores the name of the folder on the cloud storage 130 in which the image data file is stored. The storage file name 722d stores the name of the file on the cloud storage 130 in which the image data file is stored. Note that if this does not apply, such as in the history of folder creation, "-" representing NULL is stored. The creation date and time 722e stores the date and time when the folder or file was created. The update date and time 722f stores the date and time when the folder or file was updated. The access date and time 722g stores the date and time when the folder or file was accessed. The user ID 722 stores a unique identifier for identifying the user who owns the folder or file.

[0040] In this embodiment, the storage location of a file in cloud storage is expressed by a path in the file system of the cloud storage, but it may also be expressed by DNS (Domain Name System).

[0041] History data table 712 held by MFP collaborative server 120 has a structure similar to that of history data table 722 held by cloud storage 130. However, as shown in Figure 7, one difference is that relay request date and time 712e is used instead of creation date and time 722e, update date and time 722f, and access date and time 722g. Relay request date and time 712e stores the date and time when MFP collaborative server 120 requested cloud storage 130 to store the image data file of the scanned image data or the document file to be uploaded.

[0042] Next, an outline of a series of processes in the document management system for converting an image scanned by an MFP into a file and storing the file in cloud storage will be described with reference to FIG.

[0043] FIG. 8 is a sequence diagram showing a series of processes for converting an image scanned by an MFP into a file and storing the file in cloud storage.

[0044] First, in response to a user's operation on the main screen, MFP 110 displays on operation device 220 a login screen for inputting authentication information for accessing MFP linked server 120 (S101). The main screen and login screen will be described in detail later.

[0045] Next, the user enters a user name and password registered with MFP linked server 120 on the login screen, and these are sent as login information together with a login request to MFP linked server 120 (A101).

[0046] Next, as part of the login process, MFP linkage server 120 verifies whether the user name and password included in the login request are valid (S102), and if they are valid, returns an access token to MFP 110 (A102). This access token is included with each subsequent request made by MFP 110 to MFP linkage server 120, and this information can be used to identify the user who is the target of processing. User authentication is performed using a commonly known method (Basic authentication, Digest authentication, authorization using OAuth, etc.).

[0047] Next, after receiving the access token, MFP 110 requests MFP linked server 120 to acquire the access history of the cloud storage where the data is stored (hereinafter simply referred to as "cloud history") (A103).

[0048] Next, MFP linked server 120 requests cloud storage 130 to acquire the user's operation history for the cloud storage (A104). User authentication for the cloud storage is performed using a commonly known method (Basic authentication, Digest authentication, authorization using OAuth, etc.), and may be set in advance. The operation history to be acquired includes the history of folder creation in the cloud storage, access history, etc. These operation histories are operation histories recorded on the cloud storage side when the cloud storage is accessed from, for example, a web browser on client PC 140. A history of sending image data scanned from MFP 110 is also acquired.

[0049] In response to the request from MFP collaboration server 120, cloud storage 130 obtains the history from history data table 722 of cloud storage 130 (S103) and sends a cloud history response (A105). MFP collaboration server 120 obtains the history from history data table 712 of MFP collaboration server 120 (S104) and returns the history received from cloud storage 130 and the history obtained by MFP collaboration server 120 to MFP 110 (A106). The cloud history to be sent is determined based on the system settings to specify a period of time in the past to be sent, and for example, cloud history recorded on MFP 110 for the past three months is obtained and sent.

[0050] After receiving the cloud history, the MFP 110 displays a scan setting screen on the operation device 220, such as a touch panel (S105). The scan setting screen is a screen for setting scan settings, setting a storage folder, and displaying the cloud history. Details of the scan setting screen will be described later.

[0051] When a user places a paper document to be scanned on the platen glass or ADF and issues a command to start document scanning from the scan settings screen, MFP 110 executes the scan and generates image data by digitizing the paper document (S106). MFP 110 then transmits the digitized image data and management information related to the image data to MFP linked server 120 via the network, makes a request to generate an image data file (A107), and receives a receipt response (A108).

[0052] Next, MFP collaboration server 120 obtains information about the file format to be sent to cloud storage 130 from the scan setting information registered in the MFP collaboration server, and generates a file from the sent image data based on the settings (S107). MFP collaboration server 120 then transmits the image data file generated in A110 together with the folder and file information, which is storage information for cloud storage 130, set on the scan setting screen (A109). Cloud storage 130 stores the sent image data file in the specified folder (S108), and stores the corresponding cloud storage history in history data table 722 (S109). After storage, a response is sent to MFP collaboration server 120 indicating that the image data has been stored in cloud storage 130 (A110).

[0053] Next, MFP linked server 120 saves the history of requests to cloud storage 130 to store image data files in history data table 712 (S110).

[0054] 8, MFP collaboration server 120 transfers the cloud history of cloud storage 130 in response to a request from MFP 110. However, it is also possible to receive the cloud history each time a file is stored in cloud storage 130, store the cloud history in MFP collaboration server 120, and send the matching cloud history in response to a request from MFP 110.

[0055] Next, the user interface provided by the document management system according to the first embodiment will be described with reference to FIGS. FIG. 9 is a diagram showing an example of the main screen. FIG. 10 is a diagram illustrating an example of the login screen. FIG. 11 is a diagram showing one example of the scan setting screen. FIG. 12 is a diagram showing an example of the scan setting screen (part 2).

[0056] Main screen 800 is a screen that allows the user to select a main function and is displayed on the touch panel of MFP 110. To allow the user to select a main function, main screen 800 displays, for example, copy selection button 801, scan selection button 802, and scan (save to cloud storage) selection button 803. When the user touches copy selection button 801 or scan selection button 802, the copy function and scan function are executed, respectively. When the user touches scan (save to cloud storage) selection button 803, a series of operations are performed by MFP 110 to scan a document image and store the image data file in cloud storage 130, as described in FIG. 8 .

[0057] Login screen 900 is a screen on which a user enters user information and logs in to the document management system. Login screen 900 is displayed on a touch panel and has input fields: user name input field 901 and password input field 902. The user can enter their user name and password into these input fields using a touchpad (not shown), which can input alphabets, numbers, symbols, etc. After the user enters the user information, when the user touches login button 910, MFP 110 sends a login request and related login information to MFP linked server 120.

[0058] The scan setting screen 1000 is a screen for setting the folder path for storing scanned documents and for setting various scan reading settings. The scan setting screen 1000 displays cloud history information to assist the user in selecting and inputting the location for storing the documents in the cloud storage 130.

[0059] As shown in FIG. 11, the scan setting screen 1000 has a storage destination folder path input area 1001, a scan image information setting area 1010, a cloud history information area 1020, and a scan start button 1030.

[0060] The storage destination folder path input area 1001 is an area for inputting the path of the folder in which the image data file created by scanning is stored in the cloud storage 130.

[0061] The scanned image information setting area 1010 is an area for setting scanned image information, and has a color setting menu 1011 and a resolution setting menu 1012. The color setting menu 1011 is a pull-down menu for setting the color of the scanned image, such as "monochrome," "color," or "automatic." The resolution setting menu 1012 is a pull-down menu for setting the resolution of the scanned image from values ​​such as "300 dpi," "500 dpi," etc.

[0062] The cloud history information area 1020 is an area that displays information about the cloud history in the cloud storage 130. The cloud history information area 1020 has a display filter setting area 1021, a user setting area 1022, a display period setting area 1023, a cloud history list 1024, and a scan start button 1030. The display filter setting area 1021 is an area where radio buttons are arranged for selecting a filter for selecting the cloud history to be displayed in the cloud history list 1024. The display filter setting area 1021 has radio buttons for "Access," "Create Folder," and "Scan." When the user selects "Access," the cloud history list 1024 displays the history of folder paths accessed for reading and writing. When the user selects "Create Folder," the cloud history list 1024 displays the history of folder creation. When the user selects "Scan," the cloud history list 1024 displays the history of scanning from the MFP 110 and storing image data files in folder paths. The user setting area 1022 is a history of which user's cloud history is to be displayed in the cloud history list 1024. The user setting area 1022 displays the history of the logged-in user as a default, and if another user's user name is specified, the cloud history of the specified user is obtained and displayed if a user with administrator privileges is logged in. If the logged-in user is a general user, the cloud history of the specified user is obtained and displayed only if the specified user has permitted sharing with that user. The display period setting area 1023 is a pull-down menu that is set to display the cloud history from and to the specified date in the cloud history list 1024. The cloud history list 1024 displays a list of cloud history corresponding to the period between the start date and the end date specified in the display period setting area 1023.

[0063] The cloud history list 1024 is a list consisting of a pair of entries, each of which is a file storage path display 1025 and a corresponding date display 1026. The file storage path display 1025 displays the folder path in which the image data file is stored. The corresponding date display 1026 displays the date as time information of the "access," "folder creation," and "scan" of the corresponding folder path, in accordance with the specification in the display filter setting area 1021. The cloud history list 1024 is displayed in chronological order. For example, as shown in FIG. 11, the most recent date is displayed at the top.

[0064] The scan start button 1030 is a button for instructing that a document set in the MFP 110 be scanned and stored in a specified storage location in the cloud storage 130 .

[0065] Before the user sets the file, the storage destination folder path input area 1001 displays the most recent corresponding date display 1026 in the cloud history list 1024 as a default. In the example shown in FIG. 11, the storage destination folder path input area 1001 displays the top of the list, " / Development / Design / Scan Function / 20230513." This is because users often have the habit of using folders they have recently accessed multiple times. Furthermore, when the cloud history list 1024 is touched, the character string in the file storage path display 1025 is reflected in the storage destination folder path input area 1001, as shown in FIG. 12. The example shown in FIG. 12 shows that the second list was touched and the character string " / Development / Regular / Scan Function / 20230512" was reflected in the file storage path display 1025.

[0066] The user can also input a new character string from the touchpad to input a new storage destination in the storage destination folder path input area 1001. Furthermore, when the user selects the text box in the storage destination folder path input area 1001 instead of selecting it from the cloud history list 1024, a tree showing the folder structure of the cloud storage 130 may be displayed so that the user can select the storage destination.

[0067] In this way, when the user touches the start scan button 1030 after setting the folder path for storing scanned documents and various scan reading settings on the scan setting screen 1000, the set document is scanned. Then, an image data file of the scanned image is stored in the specified folder path in the cloud storage 130.

[0068] Next, details of user interface processing using cloud history in the MFP will be described with reference to Fig. 13. This processing is based on the scan setting screen 1000 shown in Fig. 11 and Fig. 12, and is processing for setting a character string in the storage destination folder path input field in Fig. 11 using cloud history.

[0069] FIG. 13 is a flowchart showing detailed processing of the user interface processing using the cloud history in the MFP.

[0070] First, linked service request unit 423 of MFP 110 acquires cloud history from cloud storage 130 via request control unit 431 (S201). The operation history to be acquired includes folder creation history, access history, and so on. If cloud storage 130 provides an API for acquiring history, that API is used to acquire the history. If cloud storage 130 does not provide an API for acquisition, a list of folders whose creation dates and times fall within a certain period from the present is acquired, and a folder creation history is generated. When this cloud history is acquired, storage history indicating in which folder the scanned and transmitted document was stored is also acquired. This storage history is the history that MFP linked server 120 retains in history data table 712 and saved in S110 of FIG. 8.

[0071] Next, the display control unit 421 of the MFP 110 uses the acquired cloud history to display the scan setting screen 1000 (S202). A display example of the scan setting screen 1000 has already been shown in FIG.

[0072] Next, MFP 110 determines whether the selection of display filter 1021 in cloud history information area 1020 on scan setting screen 1000 has been changed (S203). If the selection of display filter 1021 has been changed (S203: YES), MFP 110 updates the display of cloud history list 1024 (S204). For example, if the history of "Create folder" is displayed in display filter 1021 and the selection is changed to "Access," the display is updated to display the folder path based on the access history among the history obtained from cloud storage 130. Furthermore, if "Scan" is selected, the display shows the history of MFP linked server 120 storing the scanned image data file in the target cloud storage 130. This history of MFP linked server 120 storing the scanned image data file in the target cloud storage 130 is the history stored in history data table 712 in the processing of S110 in FIG. 8.

[0073] Next, the MFP 110 determines whether a user name has been entered in the user setting area 1022 of the scan setting screen 1000 (S205). If a user name has been entered (S205: YES), the cooperative service request unit 423 acquires the cloud history of the target user in the cloud storage 130 via the request control unit 431 (S206), and the process proceeds to S204. At this time, for security reasons, it is desirable that only users with administrator privileges be allowed to acquire the cloud history of other users. The MFP 110 then updates the display of the cloud history list 1024 based on the cloud history acquired in S206 (S204).

[0074] It is also determined whether the user has selected a desired list from the cloud history list 1024 (S207). When the desired list is selected (S207: YES), the character string in the storage destination folder path input field 1001 is updated so that it matches the character string of the folder path set in the file storage path display 1025 of the selected list. As shown in FIG. 12, an example has already been shown in which the third list is touched and the character string " / development / regular / 20230512" is reflected in the storage destination folder path input field 1001.

[0075] As described above, in the document management system of this embodiment, the MFP 110 displays a list of cloud history entries, allowing the user to select from the list, making it easy for the user to specify the cloud storage folder of their choice. This reduces the amount of input required by the user when scanning a document from the MFP 110 and uploading the image data file to cloud storage. Furthermore, a display filter can be used to display the history of the process the user intends.

[0076] [Embodiment 2]

[0077] The second embodiment will be described below with reference to FIGS.

[0078] In the first embodiment, an example was described in which an image scanned by an MFP is stored in a folder in cloud storage. In this embodiment, an example will be described in which image data files and office document files are uploaded to a folder in cloud storage by client PC 140 and stored therein. The following description of this embodiment will focus on the differences from the first embodiment. The system configuration of this embodiment is the same as that of the first embodiment shown in FIG. 1, but the MFP 110 is not necessarily required.

[0079] First, a series of processes in the document management system of this embodiment will be described with reference to FIG. FIG. 14 is a sequence diagram showing a series of processes for accessing cloud storage from the client PC 140.

[0080] This embodiment is similar to the processing of FIG. 8 in the first embodiment. However, as shown in FIG. 14, the difference is that the entity that uploads the file to the cloud storage 130 is the client PC 140. Another difference is that a web upload screen (details of which will be described later) is displayed on the client PC 140, and operations are performed from that screen. Also, scanning is not necessarily required, and what is uploaded to the client PC 140 is not limited to scanned image data files, but may be general office document files.

[0081] In this embodiment, a form will be described in which a folder path for a file uploaded from a web browser of the client PC 140 is set using the cloud history.

[0082] Next, a user interface provided by the document management system according to the second embodiment will be described with reference to FIG. FIG. 15 is a diagram showing an example of the Web upload screen.

[0083] Web upload screen 2000 is a screen that is displayed when MFP linked server 120 is accessed from the web browser of client PC 140. As shown in FIG. 15 , web upload screen 2000 includes a file name input field 2001, a storage destination folder path input field 2002, a cloud history information field 2020, an upload selection button 2030, and an upload button 2031. File name input field 2001 is an area for inputting the name of the file to be uploaded to cloud storage 130. Storage destination folder path input field 2002 is an area for inputting the path of the folder where the file to be uploaded is stored in cloud storage 130. Display filter 2021 is a filter for the history of uploads to cloud storage 130, with "upload" replacing "scan" in display filter 1021 in FIG. 12 of the first embodiment.

[0084] Cloud history information area 2020 is similar to cloud history information area 1020 in FIG. 11 of the first embodiment. Cloud history list 2024 is a list consisting of a pair of file storage path display 2025 and relevant date display 2026. File storage path display 2025 displays the folder path where a file in cloud storage 130 is stored, and when that path is selected, the corresponding character string is similarly reflected in storage destination folder path input area 2002. Furthermore, storage destination folder path input area 2002 displays, by default, the file storage path display 2025 of the most recent list in relevant date display 1026 of cloud history list 2024.

[0085] The upload selection button 2030 is a button for selecting a file to upload to the cloud storage 130. When this button is clicked with a pointing device such as a mouse to open a file explorer and the target file is selected, the file name is reflected in the file name input area 2001. Alternatively, a file name may be directly entered into the file name input area 2001 using a keyboard. The upload button 2031 is a button that is clicked to upload the file displayed in the file name input area 2001 to the folder path of the cloud storage 130 displayed in the storage destination folder path input area 2002.

[0086] Next, details of the user interface processing using the cloud history on the client PC will be explained using Fig. 16. This processing is based on the web upload screen 2000 shown in Fig. 15, and is processing for setting a character string in the storage destination folder path input field in Fig. 15 using the cloud history. FIG. 16 is a flowchart showing detailed processing of the user interface processing using the cloud history in the MFP.

[0087] First, client PC 140 acquires cloud history from cloud storage 130 via request control unit 431 (S401). The operation history to be acquired includes folder creation history, access history, and so on. If cloud storage 130 provides an API for acquiring history, that API is used to acquire the history. If cloud storage 130 does not provide an API for acquisition, a list of folders whose creation dates and times fall within a certain period from the present is acquired, and a folder creation history is generated. When acquiring this cloud history, storage history indicating in which folder the uploaded document was stored is also acquired. This storage history is history held by MFP linked server 120 and saved in S308 of FIG. 14.

[0088] Next, the client PC 140 uses the acquired cloud history to display the Web upload screen 2000 (S402). A display example of the Web upload screen 2000 has already been shown in FIG.

[0089] Next, the client PC 140 determines whether the selection of the display filter 2021 in the cloud history information area 2020 on the Web upload screen 2000 has been changed (S403). If the selection of the display filter 2021 has been changed (S403: YES), the display of the cloud history list 1024 is updated (S404). For example, if the display filter 2021 is displaying the history of "folder creation" and the selection is changed to "access," the display is updated to display a folder path based on the access history among the history acquired from the cloud storage 130. Furthermore, if "upload" is selected, the history of storing document files uploaded by the client PC 140 to the target cloud storage 130 is displayed. This history is the history of storing document files uploaded by the client PC 140 to the target cloud storage 130, and is the request history saved in the history data table 712 saved in the process of S310 of FIG. 14.

[0090] Next, the client PC 140 determines whether a user name has been entered in the user setting area 2022 of the Web upload screen 2000 (S405). If a user name has been entered (S405: YES), the client PC 140 obtains the cloud history of the target user in the cloud storage 130 via the request control unit 431 (S406) and proceeds to S404. At this time, for security reasons, it is desirable that only users with administrator privileges be allowed to obtain the cloud history of other users. The client PC 140 then updates the display of the cloud history list 1024 based on the cloud history obtained in S406 (S404).

[0091] It is also determined (S407) whether the user has selected a desired list from the cloud history list 2024. When the desired list is selected (S407: YES), the character string in the storage destination folder path input field 2002 is updated so that it matches the character string of the folder path set in the file storage path display 2025 of the selected list.

[0092] This makes it possible to easily select the destination folder path from the cloud history even from the web upload screen.

[0093] As described above, in the document management system of this embodiment, a list of cloud history files is displayed on the web upload screen of the client PC 140, allowing the user to select from the list. This allows the user to easily specify the cloud storage folder of their choice. This reduces the amount of input required by the user when uploading a document file to cloud storage. Furthermore, a display filter can be used to display the history of the process the user intends.

[0094] (Configuration 1) A document scanning device that is connected to a cloud storage via a network, transmits scanned image data to the cloud storage, and stores the scanned image data in the cloud storage as an image data file, means for acquiring a cloud history, which is an access history relating to the storage locations of image data files stored in the cloud storage; means for displaying a scan setting screen for setting a storage location of the image data file of the scanned image data in cloud storage; The document scanning device is characterized in that cloud history information acquired from the cloud storage is reflected in an input field for storing image data files on the scan setting screen.

[0095] (Configuration 2) The document scanning device according to configuration 1 is characterized in that the cloud history list, which displays the cloud history in a list form, is displayed on the scan setting screen, and when an entry in the cloud history list is selected, information on the cloud history corresponding to the entry is reflected in an input field for the storage location of the image data file.

[0096] (Configuration 3) 3. The document scanning device according to any one of configuration 2, wherein an entry in the cloud history list comprises information on a storage location of a file in the cloud storage and time information of the history.

[0097] (Configuration 4) The document scanning device according to configuration 3, characterized in that the input field for the storage location of the image data file is set as default with information on the storage location of the file of the entry in the cloud history list that has the most recent time information of the history.

[0098] (Configuration 5) a display filter means for filtering the display of cloud history information in the cloud history list; The document scanning device according to any one of configurations 2 to 4, wherein the display filter means filters the display of cloud history information in the cloud history list depending on whether the information is a history of accessing the image data file, creating a storage location for the image data file, or storing scanned images in the cloud storage.

[0099] (Configuration 6) Cloud storage and a client device cooperation server; a document scanning device connected to the cloud storage and the client device cooperation server via a network, which transmits scanned image data to the cloud storage via the client device cooperation server, and stores the scanned image data in the cloud storage as an image data file; The document scanning device A means for acquiring a cloud history, which is an access history relating to storage locations of image data files stored in the cloud storage, from the cloud storage or the client device cooperation server; means for displaying a scan setting screen for setting a storage location of the image data file of the scanned image data in cloud storage; The document scanning device A document management system characterized in that cloud history information acquired from the cloud storage is reflected in an input field for storing image data files on the scan setting screen.

[0100] (Configuration 7) Cloud storage and a client device cooperation server; a client PC connected to the cloud storage and the client device cooperation server via a network, which relays document file data via the client device cooperation server, uploads the document file data to the cloud storage, and stores the document file in the cloud storage; The client PC a means for acquiring a cloud history, which is an access history relating to the storage location of a document file stored in the cloud storage, from the cloud storage or the client device cooperation server; means for displaying an upload screen for setting a storage location of the document file to be uploaded in cloud storage; The client PC The document management system is characterized in that cloud history information acquired from the cloud storage is reflected in an input field for storing a document file on the upload screen.

[0101] (Configuration 8) The document management system according to configuration 7, wherein the cloud history list, which displays the cloud history in a list form, is displayed on the upload screen, and when an entry in the cloud history list is selected, the cloud history information corresponding to the entry is reflected in an input field for the storage location of the document file.

[0102] (Configuration 9) 8. The document management system according to configuration 7, wherein the entries in the cloud history list are made up of information about the storage location of the file in the cloud storage and time information of the history.

[0103] (Configuration 10) The document management system of configuration 9, characterized in that the input field for the storage location of the document file is set as default with information on the storage location of the file of the entry in the cloud history list that has the most recent time information of the history.

[0104] (Configuration 11) a display filter means for filtering the display of cloud history information in the cloud history list; The document management system according to any one of configurations 8 to 10, wherein the display filter means filters the display of cloud history information in the cloud history list depending on whether the document file has been accessed, a storage location for the document file has been created, or the document file has been uploaded to the cloud storage. [Explanation of symbols]

[0105] 5...Internet, 110...MFP, 120...MFP linked server, 130...Cloud storage, 140...Client PC

Claims

1. A document scanning device that is connected to a cloud storage via a network, transmits scanned image data to the cloud storage, and stores the scanned image data in the cloud storage as an image data file, means for acquiring a cloud history, which is an access history relating to the storage locations of image data files stored in the cloud storage; means for displaying a scan setting screen for setting a storage location of the image data file of the scanned image data in cloud storage; The document scanning device is characterized in that cloud history information acquired from the cloud storage is reflected in an input field for storing image data files on the scan setting screen.

2. The document scanning device according to claim 1, characterized in that the cloud history list, which displays the cloud history in a list form, is displayed on the scan setting screen, and when an entry in the cloud history list is selected, the cloud history information corresponding to the entry is reflected in an input field for the storage location of the image data file.

3. 2. The document scanning device according to claim 1, wherein an entry in the cloud history list comprises information on a storage location of a file in the cloud storage and time information of the history.

4. The document scanning device according to claim 3, characterized in that the input field for the storage location of the image data file is set as a default with information on the storage location of the file of the entry in the cloud history list that has the most recent time information of the history.

5. a display filter means for filtering the display of cloud history information in the cloud history list; The document scanning device according to claim 2, wherein the display filter means filters the display of cloud history information in the cloud history list based on whether the information is a history of accessing the image data file, creating a storage location for the image data file, or storing scanned images in the cloud storage.

6. Cloud storage and a client device cooperation server; a document scanning device connected to the cloud storage and the client device cooperation server via a network, which transmits scanned image data to the cloud storage via the client device cooperation server, and stores the scanned image data in the cloud storage as an image data file; The document scanning device A means for acquiring a cloud history, which is an access history relating to storage locations of image data files stored in the cloud storage, from the cloud storage or the client device cooperation server; means for displaying a scan setting screen for setting a storage location of the image data file of the scanned image data in cloud storage; The document scanning device A document management system characterized in that cloud history information acquired from the cloud storage is reflected in an input field for storing image data files on the scan setting screen.

7. Cloud storage and a client device cooperation server; a client PC connected to the cloud storage and the client device cooperation server via a network, which relays document file data via the client device cooperation server, uploads the document file data to the cloud storage, and stores the document file in the cloud storage; The client PC a means for acquiring a cloud history, which is an access history relating to the storage location of a document file stored in the cloud storage, from the cloud storage or the client device cooperation server; means for displaying an upload screen for setting a storage location of the document file to be uploaded in cloud storage; The client PC The document management system is characterized in that cloud history information acquired from the cloud storage is reflected in an input field for storing a document file on the upload screen.

8. The document management system of claim 7, wherein the upload screen displays a cloud history list in which the cloud history is displayed in list form, and when an entry in the cloud history list is selected, the cloud history information corresponding to the entry is reflected in an input field for the storage location of the document file.

9. 8. The document management system according to claim 7, wherein the entries in the cloud history list are made up of information about the storage location of the file in the cloud storage and time information of the history.

10. The document management system according to claim 9, characterized in that the input field for the storage location of the document file is set as a default with the information on the storage location of the file of the entry in the cloud history list that has the most recent time information of the history.

11. a display filter means for filtering the display of cloud history information in the cloud history list; The document management system according to claim 8, wherein the display filter means filters the display of cloud history information in the cloud history list depending on whether the document file has been accessed, a storage location for the document file has been created, or the document file has been uploaded to the cloud storage.

Images