Information processing device, its control method and program

Abstract

To enable a user to more easily set rules relating to distribution to a folder or naming of a file when filing and storing a scan image of a document, data of received FAX, etc.SOLUTION: A user interface screen for setting rules relating to property information to be used for storing a file while distributing it to a folder is provided with a first area for editing the rules and a second area for displaying items that a user can select. The item is a unit element for the user to set a character string constituting the property information and correspondent to a character string of any attribute that the user can set. The rules are created by disposing the items selected from the second area by the user at predetermined positions in the first area designated by the user.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] The present invention relates to a technique for setting rules when sorting files into folders.

Background Art

[0002] Conventionally, in an information processing apparatus such as an MFP (Multifunction Peripheral), a method of filing image data obtained by scanning a document, received data of a fax, etc., and transmitting it to a storage server on a network for storage has been widely used. And when storing the filed data, it is also automatically sorted into folders. For example, Patent Document 1 discloses a technique for automatically creating a folder and sorting fax data into the folder according to a previously set folder naming rule. As the folder naming rule in the technique of this Patent Document 1, it is assumed that the attribute name "registered name" is set for the folder name of the first layer, the attribute name "fax number" is set for the folder name of the second layer, and the attribute name "received date" is set for the folder name of the third layer. In this case, when a new fax is received, a new folder is created by fitting the information (registered name, fax number, received date) specified from the received data of the fax as attribute values to the corresponding attribute names. Then, the fax received data file is stored in the created folder.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the case of the technology described in Patent Document 1, the input fields for attribute names (1st to 3rd levels) are predetermined for each hierarchy level. For example, suppose a user has entered attribute value "A" in the input field for a 1st level folder and attribute value "B" in the input field for a 2nd level folder. Furthermore, suppose the user wants to create a new folder between the 1st and 2nd levels using attribute value "C". In such a case, with the technology described in Patent Document 1, all the input fields for folders from the 2nd level onward had to be changed. Specifically, it was necessary to change the input content from attribute value "B" to "C" in the input field for the new 2nd level folder, and then enter attribute value "B" in the input field for the new 3rd level (formerly 2nd level) folder. In other words, with the technology described in Patent Document 1, because the folder hierarchy and its input fields are fixed, inserting a new folder between an N-level folder and an N+1-level folder required a complicated process.

[0005] Furthermore, in the case of Patent Document 1, the attribute name is selected from a pull-down menu in each input field, but the user cannot create a new attribute name and apply it to rules regarding folder sorting rules or file naming rules.

[0006] Therefore, the technology disclosed herein aims to make it easier for users to set rules regarding folder organization and file naming when saving scanned images of documents, received faxes, and other data as files. [Means for solving the problem]

[0007] The information processing device according to this disclosure is an information processing device having means for providing a user interface screen for receiving operations from a user regarding settings for generating a file name, and setting means for performing settings for generating the file name based on operations received from the user on the user interface screen, wherein the user interface screen includes a first area for arranging a plurality of items selected by the user, the plurality of items arranged in the first area can include a first item for using the OCR results of characters included in a selected area in a scanned image as the file name, further, the first item can be configured to use the OCR results of some of the characters among the plurality of characters included in the selected area as the OCR results for the file name, and the setting means performs settings for generating the file name based on the arrangement order of the plurality of items arranged in the first area. [Effects of the Invention]

[0008] The technology disclosed herein makes it possible to more easily set rules for folder organization and file naming when saving scanned images of documents, received faxes, and other data as files. [Brief explanation of the drawing]

[0009] [Figure 1] Diagram showing the overall configuration of the image processing system. [Figure 2] Block diagram showing the hardware configuration of the MFP. [Figure 3] Block diagram showing the hardware configuration of the MFP integration server and storage server. [Figure 4] Block diagram showing the software configuration of the image processing system [Figure 5] A diagram showing an example of the folder sorting rule settings screen. [Figure 6] A diagram showing an example of the folder sorting rule settings screen. [Figure 7] Figure showing an example of a folder sorting rule setting screen [Figure 8] Figure showing an example of a folder sorting rule setting screen [Figure 9] Figure showing an example of a folder sorting rule setting screen [Figure 10] Figure showing an example of displaying the set folder sorting rules [Figure 11] Figure showing an example of a folder sorting rule setting screen [Figure 12] Figure showing an example of a folder sorting rule setting screen [Figure 13] Figure showing an example of a file naming rule setting screen [Figure 14] Figure showing an example of a property setting screen [Figure 15] Flowchart showing the process flow when setting properties [Figure 16] (a) is a figure showing an example of a folder sorting rule setting screen, (b) is a figure showing an example of a file naming rule setting screen [Figure 17] Flowchart showing the details of the property setting screen display process [Figure 18] Figure showing the state where the attribute value of a custom token is input on the property setting screen. [Figure 19] Figure showing an example of a scan profile setting screen [Figure 20] Figure showing an example of an editing screen for a scan profile [Figure 21] Figure showing an example of an addition screen for a scan profile [Figure 22] Figure showing an example of an addition screen for a scan profile [Figure 23] Figure showing an example of a destination setting screen [Figure 24] Figure showing an example of a custom token normalization rule setting screen [Figure 25] Flowchart showing the details of the process where the attribute value of a custom token is input on the property setting screen [Figure 26]This diagram shows how to select a custom token normalization rule on the folder sorting rule settings screen. [Figure 27] This diagram shows how to select a custom token normalization rule in the property settings screen. [Modes for carrying out the invention]

[0010] The embodiments for carrying out the present invention will be described below with reference to the drawings. Note that the following embodiments are not intended to limit the invention as defined in the claims, and not all combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0011] [Embodiment 1] <System Configuration> Figure 1 shows the overall configuration of the information processing system according to this embodiment. The information processing system includes an MFP (Multifunction Peripheral) 110, a client PC 111, and server devices 120 and 130 that provide cloud services over the Internet. The MFP 110 and the client PC 111 are connected to various devices that provide various services over the Internet via a LAN (Local Area Network) in a communication-enabled manner.

[0012] The MFP110 is an example of an information processing device having a scanning function. The MFP110 is a multifunction peripheral having a plurality of functions such as a printing function and a BOX storage function in addition to the scanning function. The client PC111 is an information processing device such as a desktop terminal or a mobile terminal that can receive the provision of cloud services via the Internet. The server devices 120 and 130 are both information processing devices that provide cloud services. The server device 120 of the present embodiment provides a cloud service that performs image analysis on a scanned image received from the MFP110 or transfers a request from the MFP110 to the server device 130 that provides another service. Hereinafter, the cloud service provided by the server device 120 will be referred to as the "MFP cooperation service". The server device 130 provides a cloud service (hereinafter referred to as the "storage service") that stores file data sent via the Internet in a predetermined folder or provides a stored file in response to a request from the web browser of the client PC111. In the present embodiment, the server device 120 that provides the MFP cooperation service will be referred to as the "MFP cooperation server", and the server device 130 that provides the storage service will be referred to as the "storage server".

[0013] The information processing system of the present embodiment is configured to include the MFP110, the client PC111, the MFP cooperation server 120, and the storage server 130, but is not limited thereto. For example, the MFP110 may also serve as the client PC111 or the MFP cooperation server 120. Further, the MFP cooperation server 120 may be arranged on a LAN instead of on the Internet. Further, the storage server 130 may be replaced with a mail server or the like and applied to a scenario where a scanned image of a document is attached to and transmitted by mail.

[0014] <Hardware Configuration of MFP110> Figure 2 is a block diagram showing the hardware configuration of the MFP110. The MFP110 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 is composed of the following units 211 to 219 and controls the operation of the entire MFP110. The CPU 211 reads and executes the control program (a program corresponding to the various functions shown in the software configuration diagram described later) stored in the ROM 212. The RAM 213 is used as the main memory of the CPU 211, a temporary storage area for the work area, etc. In this embodiment, one CPU 211 uses one memory (RAM 213 or HDD 214) to execute each process shown in the flowchart described later, but it is not limited to this. For example, multiple CPUs or multiple RAMs or HDDs may work together to execute each process.

[0015] HDD214 is a large-capacity storage unit that stores image data and various programs. The operation interface (I / F215) connects the operation unit (220) and the control unit (210). The operation unit (220) is equipped with a touch panel and keyboard, and accepts user operation / input / instructions. Touch operation on the touch panel includes operation with a human finger and operation with a stylus. The printer interface (I / F216) connects the printer unit (221) and the control unit (210). Image data for printing is transferred from the control unit (210) to the printer unit (221) via the printer interface (I / F216) and printed onto the recording medium.

[0016] The scanner I / F 217 is an interface that connects the scanner unit 222 and the control unit 210. The scanner unit 222 reads documents placed on a document glass (not shown) or ADF (Auto Document Feeder), generates scanned image data, and inputs it to the control unit 210 via the scanner I / F 217. The scanned image data generated by the scanner unit 222 can be printed (copied) by the printer unit 221, saved to the HDD 214, or sent as a file or email to an external device such as the MFP linkage server 120 via LAN. 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 (not shown) on the PSTN. The network I / F 219 is an interface that connects the control unit 210 (MFP 110) to the 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. The hardware configuration of the MFP110 described above is just one example; it may have other configurations as needed, or it may not have some of the configurations.

[0017] <Hardware configuration of client PCs and server devices> Figure 3 is a block diagram showing the hardware configuration of the client PC 111, MFP-linked server 120, and storage server 130. The client PC 111, MFP-linked server 120, and storage server 130 consist of a CPU 311, ROM 312, RAM 313, HDD 314, and network interface 315. The CPU 311 controls the overall operation by reading control programs stored in the ROM 312 and executing various processes. The RAM 313 is used as the main memory and temporary storage area for the CPU 311, such as the work area. The HDD 314 is a large-capacity storage unit that stores image data and various programs. The network interface 315 is an interface that connects the client PC 111 / MFP-linked server 120 / storage server 130 to the internet. The MFP-linked server 120 and storage server 130 receive requests for various processes from other devices (such as the MFP 110 and client PC 111) via the network interface 315 and return processing results corresponding to those requests.

[0018] <Software configuration of the information processing system> Figure 4 is a block diagram showing the software configuration of the information processing system according to this embodiment. The software configurations corresponding to the roles of the MFP 110, MFP linkage server 120, and storage server 130 will be described in order below. In the following description, we will focus on the functions related to the process from scanning a document with the MFP 110, creating a file of the scanned image, and saving it to the storage server 130 via the MFP linkage server 120, among the various functions of each device.

[0019] ≪MFP Software Configuration≫ The MFP110's functional modules are broadly divided into two categories: native functional modules 410 and additional functional modules 420. Native functional modules 410 are applications that come standard with the MFP110, while additional functional modules 420 are applications that are installed on the MFP110 as an add-on. Additional functional modules 420 are Java®-based applications, making it easy to add functionality to the MFP110. Note that other additional applications not shown in the diagram may also be installed on the MFP110.

[0020] The native function module 410 includes a scan execution unit 411 and a scan image management unit 412. The additional function module 420 includes a display control unit 421, a scan control unit 422, a cooperative service request unit 423, and an image processing unit 424.

[0021] The display control unit 421 displays a user interface screen (UI screen) on the touch panel of the operation unit 220 to accept various user operations. These various user operations include, for example, entering login authentication information to access the MFP linkage server 120, setting scan settings, setting rules for folder sorting and file naming, issuing a scan start command, and issuing a file save command.

[0022] The scan control unit 422, in response to user operations performed on the UI screen (for example, pressing the "Start Scan" button), instructs the scan execution unit 411 to execute the scan process along with scan setting information. The scan execution unit 411, following the scan processing execution instruction from the scan control unit 422, causes the scanner unit 240 to perform a document reading operation via the scanner I / F 217 and generates scanned image data. The generated scanned image data is saved to the HDD 214 by the scan image management unit 412. At this time, information on a scan image identifier that uniquely identifies the saved scanned image data is notified to the scan control unit 422. The scan image identifier is a number, symbol, or alphabet used to uniquely identify the image scanned by the MFP 110. The scan control unit 422, for example, obtains the scanned image data to be filed from the scan image management unit 412 using the above scan image identifier. Then, it instructs the linkage service request unit 423 to make a request to the MFP linkage server 120 for the processing necessary for file creation.

[0023] The collaborative service request unit 423 makes requests for various processes to the MFP collaborative server 120 and receives responses thereto. These processes include, for example, login authentication, analysis of scanned images, and transmission of scanned image data. Communication protocols such as REST and SOAP are used for communication with the MFP collaborative server 120.

[0024] The image processing unit 424 performs predetermined image processing on the scanned image data to generate an image used for the UI screen displayed by the display control unit 421.

[0025] ≪Server device software configuration≫ First, the software configuration of the MFP linkage server 120 will be described. The MFP linkage server 120 has a request control unit 431, an image processing unit 432, a storage server access unit 433, a data management unit 434, and a display control unit 435. The request control unit 431 is in standby mode to receive requests from external devices and, according to the content of the received request, instructs the image processing unit 432, the storage server access unit 433, and the data management unit 434 to execute predetermined processes. The image processing unit 432 performs image analysis processing such as character area detection processing, character recognition processing, and similar document determination processing on the scanned image data sent from the MFP 110, as well as image processing processing such as rotation and tilt correction. The storage server access unit 433 makes processing requests to the storage server 130. Cloud services expose various interfaces for saving files to and retrieving saved files using protocols such as REST and SOAP. The storage server access unit 433 makes requests to the storage server 130 using the exposed interfaces. The data management unit 434 holds and manages user information and various setting data managed by the MFP linkage server 120. The display control unit 435 receives requests from the MFP 110 and web browsers running on client PCs 111 connected via the internet and returns screen configuration information (HTML, CSS, etc.) necessary for screen display. Users can check registered user information and change scan settings, folder sorting, and file naming rules via the screen displayed in the web browser.

[0026] Next, the software configuration of the storage server 130 will be described. The storage server 130 has a request control unit 441, a file management unit 442, and a display control unit 443. The request control unit 441 is in a state where it can receive requests from external devices, and in this embodiment, in response to a request from the MFP linkage server 120, it instructs the file management unit 442 to save the received file or read the saved file. It then returns a response corresponding to the request to the MFP linkage server 120. The display control unit 443 receives requests from the MFP 110 connected via the internet or from a web browser running on the client PC 111, and returns screen configuration information (HTML, CSS, etc.) necessary for screen display. Users can check and retrieve saved files via the screen displayed in the web browser.

[0027] Although not shown in Figure 4, it is assumed that the client PC 111 also has the same function module as the additional function module 420 mentioned above.

[0028] <Setting folder sorting rules> Next, we will explain how to set rules for distributing destination folders when scanned document images are saved as files to the storage server 130. In this embodiment, various settings, including the setting of folder distribution rules, are described as being performed on the client PC 111. Note that the display of various UI screens and the saving of the set rules described below are implemented by the aforementioned additional function module 420 equipped on the client PC 111. In other words, the contents described below can also be performed on the MFP 110 equipped with the additional function module 420.

[0029] Figure 5 shows an example of a UI screen (hereinafter referred to as the "folder sorting rule setting screen") displayed on the client PC 111's display (not shown) for the user to set rules regarding the destination (save folder) for files. The folder sorting rule setting screen 500 shown in Figure 5 is in its initial display state and has four areas: a rule editing area 501, a system token area 502, a delimiter token area 503, and a custom token area 504. The rule editing area 501 has a token drop area 507, and at the bottom of the screen there is a "Save" button 505 for confirming and saving the set rules.

[0030] In this specification, "token" refers to a unit item used by the user to specify a string (including symbols) for property information required when saving a file to the storage server 130, taking its attributes into account. Tokens include general tokens (general items) corresponding to strings with predetermined attributes, and special tokens (special items) corresponding to strings with arbitrary attributes that the user can customize and freely set. System tokens and delimiter tokens described later fall under the category of general tokens, while custom tokens described later fall under the category of special tokens. These tokens are represented as UI elements that are the target of user operations such as drag and drop in the various setting screens described below.

[0031] The system token area 502, the delimiter token area 503, and the custom token area 504 display a list of various tokens. The rule editing area 501 displays the folder sorting rules created using these various tokens. Here, the folder sorting rules include information about the folder path (save location folder) where the scanned data will be sorted and the folder hierarchy, and are set in advance by the user.

[0032] ≪Token Settings≫ The user can select one of the tokens displayed in the system token area 502, the delimiter token area 503, and the custom token area 504 by dragging and dropping it into the token drop area 507. As a result, a new folder is simulated with the string corresponding to the selected token included in the folder name (folder path).

[0033] The system token area 502 is where tokens with user environment variables such as "login user's display name," "time," and "date" as attribute values ​​are displayed. The delimiter token area 503 is where tokens with delimiters (symbols) such as "underscores" and "hyphens" as attribute values ​​are displayed. The custom token area 504 is where tokens with arbitrary strings selected (or manually entered) from the OCR results (recognized strings) of scanned images as attribute values ​​are displayed. Users can freely create custom tokens. For example, if you drop the "Drag to create token" token 506 displayed in the custom token area 504 into the token drop area 507, an input field will appear for entering the attribute name representing that token. In other words, the string "Drag to create token" displayed on token 506 has a different meaning than the strings displayed on system tokens and delimiter tokens. In the case of token 506, it is not the attribute name that represents the content of the token itself, but rather serves as an explanatory text prompting the user to enter an attribute name and create a new token. Details about custom tokens, such as how to specifically set the attribute names to be assigned to custom tokens, will be described later.

[0034] The rule information displayed in the rule editing area 501 is sent to the MFP linkage server 120 in response to the pressing of the "Save" button 505 and is managed by the data management unit 434. Also, if the "Back" button is pressed, the rules currently displayed in the rule editing area 501 are discarded and the setting process ends.

[0035] Here, we will review the rules for sorting destination folders in this embodiment. First, there are no particular restrictions on the combinations or order of tokens that can be set as folder sorting rules. For example, a rule may be created that consists only of delimiter tokens in the delimiter token area 503 for a single folder name, or a rule may be created that uses only the same system tokens. However, the contents of each token displayed in the system token area 502 and the delimiter token area 503 cannot be changed. On the other hand, with regard to custom tokens, the attribute names of custom tokens displayed in the custom token area 504 can be freely changed, or the custom tokens themselves can be deleted.

[0036] Figure 6 shows the state of the folder sorting rule setting screen 500 when a user drags and drops an arbitrary system token from the system token area 502 to the rule editing area 501. Specifically, it shows the state when a system token 511, whose attribute name is "display name of the logged-in user," is dropped into the token drop area 507 from among the multiple system tokens displayed in the system token area 502. Looking at the rule editing area 501 in Figure 6, a new token 508 with the attribute name "display name of the logged-in user" is placed at the location of the token drop area 507 where the user performed the drop operation (see Figure 5), and new token drop areas 514 and 515 are generated at the same time. In the state shown in Figure 6, if the user selects one token from the group of tokens in the various token areas 502 to 504 and drags and drops it into the token drop area 514, a new token drop area will be generated (not shown). Then, if the user drags and drops another arbitrary token into the newly generated token drop area, even more token drop areas will be generated. Figure 7 shows the state of the folder sorting rule setting screen 500 after repeating these operations. Looking at the rule editing area 501 in Figure 7, two new tokens (token 516 with the attribute name "{space}" and token 517 with the attribute name "name of scan profile") have been added, and a token drop area 518 has also been created. In this case, the three tokens 508, 516, and 517 are set as the folder name of the first-level (top-level) folder. Following the example in Figure 7, a folder with the folder path "(display name of logged-in user) (name of scan profile)" will be created as the top-level folder. On the other hand, if you drag and drop any token into the token drop area 515 in the second-level in the rule editing area 501 shown in Figure 6, another new token drop area will be created. Looking at the rule editing area 501 in Figure 7, a token 519 of "date (year, 4 digits)" has been added, and two more token drop areas 520 and 521 have been created.Token drop area 521 is used when adding a new token to a second-level folder that is already designated to use token 519. Token drop area 520 is used when setting the initial token for a third-level folder.

[0037] As is clear from the explanation so far, the hierarchy differs between folders that use the three tokens 508, 516, and 517 in their folder names and folders that use token 519 in their folder names (see Figure 7). In other words, in terms of folder structure, folders that use token 519 in their folder names are located lower down than folders that use the three tokens 508, 516, and 517 in their folder names. Furthermore, even tokens set in the rule editing area 501 as described above can be rearranged by dragging, for example, by swapping adjacent tokens or inserting tokens between them.

[0038] ≪Token Deletion≫ Next, we will explain how a user can delete tokens for each folder hierarchy set as described above. When a user hovers their mouse over any token displayed in the rule editing area 501, an "×" button appears on that token (not shown). The user can delete any token by pressing this "×" button. Figure 8 shows the state of the folder sorting rule setting screen 500 after a token set in the rule editing area 501 has been deleted by the deletion operation described above. In the rule editing area 501 in Figure 8, UI blocks 522 and 523 labeled "Deleted" are displayed where the token was deleted. These UI blocks 522 and 523 labeled "Deleted" function as token drop areas, and when a new token is dragged and dropped onto these UI blocks, the new token is set in the position labeled "Deleted". Thus, in this embodiment, even if a token displayed in the rule editing area 501 is deleted, the area where the token existed is maintained. However, instead of displaying the "Deleted" UI block and allowing a new token to be placed there, the area where the token was deleted may be displayed in a more compact manner. In the state shown in Figure 8, when the user presses the "Save" button 505, the folder sorting rule settings screen 500 transitions to the state shown in Figure 9, and the "Deleted" UI block disappears.

[0039] ≪Checking the configured folder sorting rules≫ Figure 10 shows an example of how folder sorting rules created and saved by a user via the aforementioned folder sorting rule setting screen 500 are displayed on the main screen (not shown). In the example shown in Figure 10, a folder path 1001 is displayed, with folder hierarchy divisions represented by slashes. Note that the folder path 1001 shown in Figure 10 corresponds to the result of setting predetermined tokens for each of the first to third level folders, as shown in the rule editing area 501 in Figure 12 described later. If the tokens set in the rule editing area 501 shown in Figure 8 are followed, the content of the displayed folder path will be "{display name of the logged-in user} / date (month)". In other words, in the case of Figure 8, the token for the second level folder is deleted, and the folder path according to the tokens set for the first and third level folders is displayed. Thus, if a token for a folder at a particular level no longer exists due to the deletion of a set token, the folder path will be displayed with the folders at that level removed.

[0040] <Custom Token> Next, we will explain the user operations and corresponding UI screen transitions when setting folder sorting rules using a custom token, which is a feature of this embodiment. Figure 11 shows the state of the folder sorting rule setting screen when a custom token 506 is dropped into the third-level token drop area in the rule editing area 501. At this point, the text "Adding..." 1100 is displayed in the token drop area where the custom token 506 was dropped, and the string "Company Name" is entered into the text field 1101 that pops up in response to the drop operation. The string entered into the text field 1101 will be set as the attribute name of the token for the third-level folder when the "Save" button 1102 in the text field 1101 is pressed. The "Cancel" button is used to cancel the setting of the custom token.

[0041] Figure 12 shows the state of the folder sorting rule setting screen 500 after a custom token has been set by pressing the "Save" button 1102 by the user. Token 1201, which has the string "Company Name" entered in the text field 1101 as its attribute name, is displayed as the token for the third-level folder in the rule editing area 501. Furthermore, in the custom token area 504, custom token 1202, which has the string "Company Name" as its attribute name, is displayed so that the custom token created this time can be reused. Note that the timing at which the string entered in the text field 1101 is saved as the attribute name of a reusable custom token may be immediately after entering the attribute name in the text field 1101 (i.e., before pressing the "Save" button 1102). Also, if a token with the same content as an attribute name that already exists as a system token or delimiter token is newly created as a custom token, it will be added to the custom token area 504 as a new custom token. However, even if a user enters a string in text field 1101 that is identical to the attribute name of a custom token already existing in custom token area 504, the custom token with the same attribute name will not be displayed in custom token area 504. Furthermore, if a string already used as an attribute name for an existing custom token is entered in text field 1101, the user may be notified by displaying a message indicating that the string cannot be used as an attribute name. Alternatively, the user may be allowed to enter the previously used string into text field 1101 and to set a custom token based on that input, but only the addition to custom token area 504 may be prevented. Additionally, even if a custom token with the same attribute name as a system token or delimiter token is created, it may be prevented from being registered or used as a custom token.

[0042] <Setting custom token extraction and validation rules> This section describes how to configure string extraction rules and string validation rules for custom tokens. In this embodiment, the explanation will be based on the case where the string extraction rules and string validation rules are configured on client PC 111.

[0043] String extraction rules are rules that normalize (extract or delete) the values ​​entered in attribute value input fields when setting properties. In other words, they are rules that are referenced when extracting or deleting specific strings from the values ​​entered in attribute value input fields. On the other hand, string validation rules are rules that validate the values ​​entered in attribute value input fields when setting properties. If, as a result of validating the string validation rules, the string entered in the attribute value input field does not conform to the specified format, the user will be warned accordingly.

[0044] Figure 24 shows an example of a UI screen (hereinafter referred to as the "custom token normalization rule setting screen") for users to set string extraction rules and string validation rules displayed on the client PC 111's display. The custom token normalization rule setting screen 2400 shown in Figure 24 is shown in its initial display state. There are no particular limitations on how the custom token normalization rule setting screen 2400 is displayed. For example, it may be displayed when a registered custom token is selected in the folder sorting rule setting screen 500 in Figures 11 and 12. Alternatively, a separate custom token registration screen (not shown) may be provided, and the screen may be displayed when the "Add" button on that custom token registration screen is pressed and an attribute name is subsequently entered.

[0045] On the custom token normalization rule setting screen 2400, there are setting items for display name 2401, default value 2402, data extraction rule 2403, and data verification rule 2404. By entering an arbitrary string in the text field corresponding to each setting item, the setting value for each setting item is determined. In the display name 2401, the attribute name is set. In the default value 2402, the value that is defaultly entered in the attribute value input field can be set. In the data extraction rule 2403, the above-mentioned string extraction rule can be set. In the data verification rule 2404, the above-mentioned string verification rule can be set. The default value 2402, the data extraction rule 2403, and the data verification rule 2404 may remain blank, or values may be entered in any combination.

[0046] Also, the format for entering setting values in the data extraction rule 2403 and the data verification rule 2404 is not limited. For example, in addition to the user directly entering a regular expression, a format where options are displayed in a pull-down form and the user selects from them can be considered. For example, when setting a rule to delete the string "Limited Company" included in the company name as the string extraction rule, it may be possible to achieve this by directly entering ".+(?=Limited Company)|(?<=Limited Company).+" in the data extraction rule 2403. Also, when setting a rule to verify whether the entered string is composed only of half-width numbers as the string verification rule, it may be possible to achieve this by directly entering "[0-9]+" in the data verification rule 2404. As an example of displaying options instead of such direct input, for the string extraction rule, options such as "Delete company names such as Limited Company" can be displayed. Or for the string verification rule, it is conceivable to display options such as "Date format: YYYYMMDD" or "Date format: YYYY year MM month DD day".

[0047] <Setting of file naming rules> Next, we will explain how to set naming rules for filenames assigned when scanning images and the like are converted into files. In this embodiment, the explanation will also be based on the case where the file naming rules are set on the client PC 111. Figure 13 is a diagram showing an example of a UI screen (hereinafter referred to as the "file naming rule setting screen") for setting file naming rules, which is displayed on the display (not shown) of the client PC 111. The file naming rule setting screen 1300 shown in Figure 13 shows the initial display state and has the same screen configuration as the folder sorting rule setting screen 500 described above. That is, the file naming rule setting screen 1300 also has four areas: a rule editing area 1301, a system token area 1302, a delimiter token area 1303, and a custom token area 1304. Furthermore, there is a token drop area 1305 in the rule editing area 1301, and at the bottom of the screen there is a "Save" button 1306 for confirming and saving the set file naming rules. The following explanation will focus on the differences from the folder sorting rule setting screen 500.

[0048] Creating file naming rules is also done by dragging and dropping the various tokens displayed in the system token area 1302, the delimiter area 1303, and the custom token area 1304 into the rule editing area 1301. The difference from the folder sorting rule settings screen 500 is that, in the case of file names, there is no hierarchical structure, and even if a new token is added to the rule editing area 1301, multiple token drop areas will not be displayed.

[0049] One or more tokens placed in the rule editing area 1301 become components of a single file name. In other words, if multiple tokens are set, a single file name is generated by concatenating the attribute values ​​of each token.

[0050] Currently, in the custom token area 1304 of the file naming rule setting screen 1300 shown in Figure 13, custom token 1311 with the attribute name "Company Name" and custom token 1312 with the attribute name "Quotation" are displayed. Of these two custom tokens, the custom token 1311 for "Company Name" corresponds to the custom token 1202 created in the folder sorting rule setting screen 500 mentioned above. In other words, the custom token created when setting up folder sorting rules is displayed as a custom token that can also be used when setting up file naming rules. Similarly, the custom token 1312 for "Quotation" displayed in the custom token area 1304 of the file naming rule setting screen 1300 will also be displayed in the custom token area 504 when the folder sorting rule setting screen 500 is opened after its creation. In this way, custom tokens can be shared between the folder sorting rule setting screen and the file naming rule setting screen.

[0051] <Property settings when creating a file> Next, we will explain the specific processing flow for setting properties when creating files from scanned images, etc. Here, properties refer to the file name, folder path, metadata, etc., required for each piece of data to be filed. For example, when scanning a document, creating a file from it, and saving it to storage server 130, the user will set the necessary properties through a property settings screen that reflects the destination folder sorting rules and file naming rules set as described above.

[0052] Figure 14 shows an example of a property settings screen. The property settings screen 1400 shown in Figure 14 is in its initial display state and consists of two panes: a preview pane 1401 and a property pane 1402. Currently, a scanned image of a "Quotation" form is displayed as a preview in the preview pane 1401. In the preview pane 1401, the scanned image can be scrolled and zoomed to display any position in the scanned image. The property pane 1402 is a pane for displaying and editing the properties to be assigned to the scanned image to be processed. Currently, the property pane 1402 displays a folder path display area 1403, a file name display area 1404, an attribute value input field 1405 corresponding to the folder path, and an attribute value input field 1406 corresponding to the file name. The " / tokita / {company name} / 2020.02.27" displayed in the folder path display area 1403 is based on the folder sorting rule set in the folder sorting rule settings screen 500 mentioned above. Furthermore, the file name displayed in the file name display area 1404, "{Quote}_20200227_{Company Name}_1", is based on the file naming rules set in the file naming rule settings screen 1300. Details on the display of folder paths and file names based on each rule will be described later.

[0053] <Property setting process flow> Figure 15 is a flowchart showing the processing flow when a user sets file properties on the MFP110 via the property setting screen 1400 described above. This flow is triggered when the display control unit 421 of the MFP110 receives a user instruction to open the property setting screen 1400. Now, the folder sorting rules and file naming rules are set to the following contents as shown in the setting screens of Figures 16(a), (b), and (c), respectively.

[0054] ≪Folder sorting rule settings≫ "Display name of logged-in user" (system token) / "Company name" (custom token) / "Year" (system token) "Period" (delimiter token) "Month" (system token) "Period" (delimiter token) "Day" (system token)" ≪File naming rule settings≫ "Quote (custom token) Underscore (delimiter token) Year (system token) Month (system token) Day (system token) Underscore (delimiter token) Company name (custom token)" ≪Settings for the custom token normalization rule for the company name (custom token)≫ "Display name: Company name, Default value: Empty, Data extraction rule: ".+(?=Co., Ltd.)|(?<=Co., Ltd.).+" (Remove Co., Ltd. from the beginning and end), Data validation rule: ".+" (Not empty)" The following will explain in detail according to the flow in Figure 15. In the following explanation, the symbol "S" represents a step.

[0055] First, in S1501, information on the folder sorting rules set by the user is obtained. In the following S1502, information on the file naming rules set by the user is obtained. In the next S1503 and S1504, the process of obtaining the attribute values ​​is repeated for each system token included in the information obtained in S1501 and S1502. Specifically, the strings corresponding to the user's environment variables corresponding to the system tokens are obtained from the data management unit 434 of the MFP linkage server 120. For example, for the system tokens "year", "month", and "day", the strings "2020", "2", and "27", representing the scanned date, are obtained, respectively. Also, for the system token "display name of logged-in user", the string "tokita", representing the username of the user registered in the system, is obtained. In the above example, there are 4 system tokens in the folder sorting rules and 3 in the file naming rules, so the acquisition of attribute values ​​is repeated 7 times. If the acquired rules do not include a system token, processes S1503 and S1504 are skipped, and the process proceeds to S1505. Unlike custom tokens and delimiter tokens, the attribute value of a system token changes dynamically according to the system settings. Therefore, the corresponding string (attribute value) for each system token must be updated whenever there are changes to the system settings.

[0056] In S1505, folder paths are generated using the folder sorting rules obtained in S1501 and the strings for each system token obtained in S1504. In the subsequent S1506, file names are generated using the file naming rules obtained in S1502 and the strings for each system token obtained in S1504. At this time, delimiter tokens will contain the corresponding delimiter character, such as a period or a space. Custom tokens will temporarily contain the string of the corresponding attribute name.

[0057] In the next step, S1507, the aforementioned property setting screen 1400 is displayed on the client PC 111's display (not shown). Figure 17 is a flowchart detailing the process of displaying the property setting screen. The following will explain this in detail following the flow shown in Figure 17.

[0058] In S1701, the folder path generated in S1505 is displayed in the folder path display area 1403 of the property settings screen 1400. As mentioned above, in the example in Figure 14, " / tokita / (company name) / 2020.02.27" will be displayed. In this case, the system token whose attribute name is "display name of the logged-in user" contains the string "tokita". The custom token whose attribute name is "company name" contains a string, for example, by selecting a desired text block from the scanned image, so at this stage, the string "company name" which indicates the attribute name is temporarily placed there. The system tokens whose attribute names are "year", "month", and "day" respectively contain the numbers "2020", "02", and "27", which represent the date the scanned image in the preview pane 1401 was acquired, separated by the delimiter token "." (period). If the date on which the scan was performed changes, the numbers assigned to these system tokens will change each time.

[0059] In S1702, it is determined whether the folder sorting rule obtained in S1501 contains a custom token. If a custom token is included, the process proceeds to S1703; otherwise, it proceeds to S1705. In the example above, a custom token with "Company Name" as the attribute name is included, so the process proceeds to S1703.

[0060] In S1703 and S1704, the process of displaying the attribute value input field 1405 for each custom token included in the folder sorting rule is repeated. In the example above, there is only one custom token included in the folder sorting rule, so only one attribute value input field is displayed (see Figure 14). However, if there are multiple custom tokens, multiple attribute value input fields will be displayed. Note that if there are no custom tokens in the folder sorting rule (No in S1702), the attribute value input field will not be displayed.

[0061] In the next step, S1705, the file name generated in S1506 is displayed in the file name display area 1404 of the property settings screen 1400. As mentioned above, in the example in Figure 14, "{quote}_20200227_{company name}_1" will be displayed. In this case, for the system tokens "year", "month", and "day", the numbers "2020", "02", and "27", which represent the date the scanned image in the preview pane 1401 was acquired, are displayed concatenated without the use of delimiters. Also, for the custom tokens with "quote" and "company name" as attribute names, as mentioned above, temporary strings representing each attribute name are inserted.

[0062] In S1706, it is determined whether the file naming rule obtained in S1502 contains a custom token. If a custom token is included, the process proceeds to S1707; otherwise, the process is exited. As mentioned above, the custom token contains "quote" and "company name" as attribute names, so the process proceeds to S1707.

[0063] In S1707 and S1708, the process of displaying attribute value input fields 1406 for custom tokens is repeated for each custom token included in the file naming rule. In the example above, there are two custom tokens included in the file naming rule, so there are also two attribute value input fields 1406 displayed (see Figure 14). Note that if the file naming rule does not include a custom token (No in S1706), attribute value input field 1406 will not be displayed.

[0064] The above describes the process for displaying the property settings screen. In this embodiment, a common token (custom token, system token) can be used when creating rules for folder paths and file names. Even if a common token is used, the property pane 1402 will display folder paths and file names separately.

[0065] Figure 18 shows how the user enters the attribute values ​​of custom tokens in the property settings screen 1400 after the property settings screen display process described above has finished. The attribute value input fields 1405 / 1406 corresponding to each custom token display the attribute name 1801, the attribute value 1802, and the cropped image 1803 corresponding to the attribute value. When the user has not selected a text block containing the attribute value (string) of a custom token from the preview pane 1401, the attribute value 1802 will be displayed as "none (empty)," as in the attribute value input field 1406 for a custom token with "quotation" as the attribute name. The cropped image 1803 corresponding to the attribute value will also be blank.

[0066] To input attribute values ​​for a custom token, the user first selects the attribute value input field for the target custom token from the attribute value input fields displayed in the properties pane 1402. In Figure 18, attribute value input field 1405 is selected and highlighted. In this state, the user specifies (for example, by clicking) a text block containing the custom token's attribute value (string) from the scanned image displayed in the preview pane 1401. The clicked text block is highlighted in the preview pane 1401 with a border and color. At the same time, the selected attribute value input field 1405 in the properties pane 1402 displays the string contained in the specified text block as attribute value 1802. At this time, attribute value 1802 displays the value after the data extraction rules and data validation rules set in the "Custom Token Normalization Rule Settings Screen" have been applied. Furthermore, the image portion corresponding to the text block is displayed as a cropped image 1803 corresponding to the attribute value. In this way, when attribute values ​​are entered into the custom token, their contents are reflected in the folder path display area 1403 and the file name display area 1404.

[0067] Here, referring to the flowchart shown in Figure 25, we will explain the process by which the value of the text block selected by the user is entered into the attribute value input field. In the following explanation, the symbol "S" represents a step.

[0068] First, S2501 detects the user's selection of a text block. Then, S2502 determines whether an attribute value input field is selected. If it is not selected, the process returns to S2501. If it is selected, the process proceeds to S2503.

[0069] In S2503, the OCR string of the text block selected by the user is obtained. Specifically, the Linkage Service Request Unit 423 sends an analysis request for the selected text block to the MFP Linkage Server 120, and the Image Processing Unit 432 performs OCR processing based on that request. The result of the OCR processing is then returned to the Linkage Service Request Unit 423, and the Display Control Unit 421 obtains the result. For example, in the Properties pane 1402, with the attribute value input field 1405 of the custom token whose attribute name is "Company Name" selected, the user clicks the text block 1804 of "Plastic Mold Co., Ltd." in the Preview pane 1401. Then, as described above, OCR processing is performed on the text block 1804, and "Plastic Mold Co., Ltd." is obtained as the OCR string.

[0070] Next, in S2504, it is determined whether a string extraction rule is set for the selected attribute value input field. If it is not set, the process proceeds to S2507; if it is set, the process proceeds to S2505.

[0071] In S2505, the configured string extraction rule is retrieved. Here, we assume that the string extraction rule obtained is "remove 'Kabushiki Kaisha' from the company name." In the following S2506, the attribute value data is extracted from the OCR string obtained in S2503 according to the string extraction rule. Currently, the OCR string "Plastic Mold Co., Ltd." has been obtained, so "Plastic Mold" is extracted by removing "Kabushiki Kaisha."

[0072] In the next step, S2507, an attribute value is entered into the attribute value input field. Here, the string "plastic mold" is entered as the attribute value into the attribute value input field 1405. Once the attribute value is entered in this way, the "{company name}" part in the folder path display area 1403 is replaced with "plastic mold". Also, since a custom token with "company name" as the attribute name is set in the file naming rules, synchronization processing is performed on its attribute value input field 1406. In other words, the "{company name}" part in the file name display area 1404 is also replaced with "plastic mold". Synchronization processing is also performed when the string to be used as an attribute value is entered manually using a soft keyboard (not shown), in addition to specifying an arbitrary text block from the preview pane 1401. That is, for common custom tokens, the same attribute value will be set regardless of how the attribute value is entered. Note that if you select an attribute value input field for a custom token whose attribute values ​​have already been set, and specify a different text block than the currently specified text block, the existing attribute values ​​will be overwritten by the newly entered attribute values.

[0073] Next, in S2508, it is determined whether a string validation rule is set for the selected attribute value input field. If it is not set, the process terminates. If it is set, the process proceeds to S2509. In S2509, the set string validation rule is retrieved. Then, in S2510, the attribute value entered in S2507 is validated according to the string validation rule retrieved in S2509. If the validation result is invalid, the process proceeds to S2511, and a message indicating that the entered attribute value is invalid is displayed (not shown). On the other hand, if there are no problems with the validation result, the process terminates.

[0074] After completing the above process for all custom tokens, the user presses the "Send" button 1805. This sends the scanned image data, along with the folder path and file name information set on the property settings screen 1400, from the MFP 110 to the MFP linkage server 120. The MFP linkage server 120's storage server access unit 433 then uses the received information and data to create a file with the specified file name assigned to the scanned image data, and saves it to the specified folder on the cloud server 130. If the user presses the "Send" button 1805 with no attribute values ​​set for the custom token, the folder path and file name will be generated and saved with the attribute value portion left blank. For example, in the property settings screen 1400 in Figure 18, no attribute values ​​are set for the custom token with "Quotation" as the attribute name. If the "Send" button 1805 is pressed in this state, the MFP linkage server 120 will request the storage server 130 to save the scanned image data displayed in the preview pane 1401 under the following conditions.

[0075] Save location folder: " / tokita / Plastic Mold Co., Ltd. / 2020.02.27" File name: "_20200227_Plastic Mold Co., Ltd._1" <Scan Profile> The folder sorting rules and file naming rules configured as described above can be set for each type of scan workflow. Here, a scan workflow refers to a workflow for scanning documents such as forms and sending the scanned image data obtained to a specific destination (for example, storage server 130) under specific conditions. The conditions and destination information for each scan workflow are managed by the scan profile. By creating scan profiles in advance, users can easily implement their desired scan workflows.

[0076] Figure 19 shows an example of a UI screen (hereinafter referred to as the "scan profile setting screen") for setting scan profiles, which is displayed on the operation panel 220 of the MFP110 (or client PC 111). The scan profile setting screen 1900 shown in Figure 19 consists of a side menu area 1901 and a menu area 1902. Selecting "Scan" from the items displayed in the side menu area 1901 transitions to a UI screen (hereinafter referred to as the "scan profile editing screen") for editing scan profiles, such as adding and deleting them, as described later. The menu area 1902 displays multiple icons corresponding to scan profiles. Each time a user creates a scan profile, an icon corresponding to that scan profile is added to the menu area 1902. Pressing the button 1903 at the bottom of the menu area 1902 displays icons for other scan profiles that could not be displayed, making them viewable.

[0077] Note that the scan profile settings screen 1900 shown in Figure 19 is the UI screen displayed when a user with the user ID "user a" logs into the MFP110. The scan profile displayed may differ depending on the user logging in, or there may be a scan profile that can be used in common by multiple users.

[0078] Suppose a user selects an icon corresponding to a desired scan profile on the scan profile settings screen 1900 and then instructs the system to perform a scan. Then, the properties settings screen 1400 is displayed, which determines folder and file names according to the folder sorting rules and file naming rules corresponding to the selected scan profile. For example, suppose the scan profile indicated by icon 1904 is associated with the following folder sorting rules and file naming rules.

[0079] Folder sorting rule: " / {display name of logged-in user} / {company name} / {year}{month}{day} / " File naming rule: "{quote}_{year}{month}{day}_{company name}" In this case, the scanned image generated after icon 1904 is selected is displayed in the preview pane 1401 of the properties settings screen 1400. The folder sorting rule described above, associated with the scan profile corresponding to the selected icon 1904, is then displayed in the folder path display area 1403. Additionally, the file naming rule described above, associated with the same scan profile, is displayed in the file name display area 1404.

[0080] Creating a scan profile Next, we will explain how to create a scan profile. A user can log in to the MFP linkage server 120 via, for example, client PC 111, and after logging in, can access the UI screen for editing scan profiles (hereinafter referred to as the "editing screen") shown in Figure 20 by navigating from the main screen (not shown). The editing screen 2000 shown in Figure 20 includes a menu list area 2001, a profile list area 2002, and a profile settings area 2003. The profile list area 2002 displays a list of scan profiles that are being created or have already been created. The profile settings area 2003 displays the settings of the scan profile selected by the user from the list displayed in the profile list area 2002. The profile list area 2002 and the profile settings area 2003 are displayed by selecting the item "Scan Profile" in the menu list area 2001.

[0081] Furthermore, pressing button 2004 at the top of the editing screen 2000 displays a UI screen for adding scan profiles (hereinafter referred to as the "addition screen") superimposed on the editing screen 2000, as shown in Figure 21, allowing the addition of a new scan profile. The addition screen 2100 shown in Figure 21 has multiple setting tabs 2102, and selecting one of these tabs displays the multiple setting items included in that tab. In the example in Figure 21, the setting items displayed when the "Output Settings" tab is selected are shown. Among the displayed setting items, the "File Name Prefix" 2101 has a "File Naming Rule Settings" button 2103. Pressing this "File Naming Rule Settings" button 2103 displays the aforementioned file naming rule setting screen 1300, allowing the creation and editing of file naming rules.

[0082] Figure 22 shows the settings displayed when the "Workflow Settings" tab is selected in the additional screen 2100 of Figure 21. Among the displayed settings is the "Set Destination Folder Rules" button 2201, and selecting this button 2201 displays the aforementioned folder sorting rule settings screen 500. In this case, if folder sorting rules have already been created, the created folder sorting rules will be displayed around the "Set Destination Folder Rules" button 2201 (directly above it in the example of Figure 10 above).

[0083] Furthermore, after setting various information for the scan profile, pressing the "Add" button 2104 on the Add screen 2100 closes the Add screen 2100 and switches to a UI screen for setting the destination for the scanned image data that has been saved as a file (hereinafter referred to as the "Destination Setting Screen"). Figure 23 shows an example of the Destination Setting Screen. The Destination Setting Screen 2300 shown in Figure 23 displays a list of multiple destinations, and when one of them is selected, the information of the selected destination is saved in association with the scan profile being created.

[0084] Once the minimum information necessary to implement the scan workflow is set as described above, the system returns to the editing screen 2000 shown in Figure 20. At this point, the newly created scan profile is added and displayed in the profile list area 2002.

[0085] <Variation> Next, as an example, we will describe a modification that makes it easier for users to set string validation rules and string extraction rules for custom tokens that have specific attribute names that are frequently used, such as "company name" and "date". Here, the specific custom tokens related to this modification will be called "attribute type custom tokens".

[0086] Figure 26 shows the state of the folder sorting rule setting screen 500 when an attribute type custom token 2601 with "Company Name" as its attribute name is dropped into the token drop area. Currently, a context menu 2602 is displayed in a pull-down format below the dropped custom token. This context menu 2602 contains radio buttons 2602a to 2602c. Each radio button corresponds to "Set data normalization rules," "Remove company name (remove characters such as "Co., Ltd." included in the company name)," and "Do not set data normalization rules." For example, a user who wants to set data normalization rules selects radio button 2602a. Then, the string validation rules and / or string extraction rules that are pre-associated with the attribute type custom token are set. This allows the user to easily set the desired custom token with string validation rules and string extraction rules without going through the custom token normalization rule setting screen 2400. On the other hand, if radio button 2602c is selected, no normalization rules are set for the dropped attribute type custom token. When radio button 2602b is selected, the system is configured to automatically remove characters such as "Co., Ltd." from the company name of the dropped attribute type custom token.

[0087] This attribute type custom token may be displayed differently depending on the scan profile selected by the user and the type of document being scanned. For example, when creating a scan profile for scanning business cards, the attribute type custom tokens that can be used for folder sorting rules and file sorting rules may be limited to "Company Name," "Department," "Name," "Phone Number," and "Email Address." Additionally, a text field may be provided to allow the user to freely customize the rules using regular expressions or other methods if the desired rule is not available in the context menu options.

[0088] Furthermore, it may be possible to set normalization rules for custom tokens at the time a text block is selected in the preview pane 1401 of the property settings screen 1400. Figure 27 shows the property settings screen 1400 when a custom token of attribute type with "Company Name" as its attribute name is set for folder sorting rules and file name rules. Currently, the attribute value input field 2701 is selected and highlighted. When the user mouses over the text block 2702 in this state, a popup menu 2703 appears below the text block 2702. The contents displayed in the popup menu 2703 at this time are the string validation rules and / or string extraction rules that were previously associated with the custom token of attribute type "Company Name". In this example, the user can set a normalization rule to remove the characters "Kabushiki Kaisha" (Co., Ltd.) from the company name by selecting "Remove Company Name" in the displayed popup menu. In this way, it may be possible to set normalization rules when inputting attribute values.

[0089] This modification reduces the effort required to set normalization rules for custom tokens, making it easier for users to utilize string validation and string extraction rules.

[0090] As described above, according to this embodiment, users can easily create and edit folder sorting rules and file naming rules necessary when saving scanned images of documents and the like as files. Other embodiments

[0091] The object of the present invention can also be achieved by performing the following process: supplying a storage medium containing program code for software that realizes the functions of the above-described embodiment to a system or device, and having the computer (or CPU, MPU, etc.) of the system or device read the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the above-described embodiment, and the program code and the storage medium containing the program code constitute the present invention. [Explanation of symbols]

[0092] 110 MFP 111 Client PCs 120 MFP Integration Servers 130 Storage Servers 420 Additional Function Modules 421 Display Control Unit

Claims

[Claim 1] A means for providing a user interface screen that accepts user input regarding settings for generating filenames, A setting means for generating the file name based on the operation received from the user on the user interface screen, An information processing device having, The user interface screen includes a first area where multiple items selected by the user are arranged side by side. The plurality of items arranged in the first area may include a first item for using the OCR result of characters contained in a selected area within the scanned image as the file name. Furthermore, for the first item, it is possible to set rules for using the OCR results of some of the characters among the multiple characters included in the selection area as the OCR results to be used in the file name. The setting means performs settings for generating the file name based on the arrangement order of the plurality of items arranged in the first area. An information processing device characterized by the following:

Images