Information processing device, control method therefor 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 for sorting files into folders. [Background technology]

[0002] Conventionally, a technique has been widely used in information processing devices such as MFPs (Multifunction Peripherals) to file image data obtained by scanning documents or received fax data, and then transmit and store the data to a storage server on a network. When saving the filed data, the data can also be automatically sorted into folders. For example, Patent Document 1 (Patent Document 1) discloses a technology that automatically creates folders and sorts fax data into folders according to a predefined folder naming rule. The folder naming rule in Patent Document 1 assumes that the first-level folder name has an attribute name "Registered Name," the second-level folder name has an attribute name "Fax Number," and the third-level folder name has an attribute name "Received Date." In this case, when a new fax is received, a new folder is created by assigning information identified from the received fax data (Registered Name, Fax Number, and Received Date) to the corresponding attribute names as attribute values. The received fax data file is then saved in the created folder. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-169951 Summary of the Invention [Problem to be solved by the invention]

[0004] In the technology of Patent Document 1, attribute name input fields (first to third hierarchies) are predetermined for each hierarchy. For example, suppose a user inputs an attribute value "A" in the input field for a folder in the first hierarchy and an attribute value "B" in the input field for a folder in the second hierarchy. Furthermore, suppose the user wants to create a new folder between the first and second hierarchies using an attribute value "C." In such a case, the technology of Patent Document 1 requires the user to change all input fields for folders in the second hierarchy and beyond. Specifically, the user must change the input content in the input field for the new folder in the second hierarchy from "B" to "C," and then enter the attribute value "B" in the input field for the new folder in the third hierarchy (the former second hierarchy). In other words, in the technology of Patent Document 1, because the folder hierarchy and its input fields are fixed, inserting a new folder between a folder in the Nth hierarchy and a folder in the N+1th hierarchy requires cumbersome work.

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

[0006] Therefore, the technology disclosed herein aims to enable users to more easily set rules regarding folder allocation and file naming when converting scanned images of documents, received faxes, and other data into files and saving them. [Means for solving the problem]

[0007] The information processing device of the present disclosure is an information processing device having a means for providing a user interface screen for receiving operations from a user regarding settings for generating a file name, and a setting means for making settings for generating the file name based on the operations received from the user on the user interface screen, wherein the user interface screen includes a first area in which multiple items selected by the user are arranged side by side, and the multiple items arranged in the first area can include a first item for using the OCR results of characters included in a selected area in the scanned image for the file name, and further, for the first item, it is possible to set a rule for using the OCR results of some of the multiple characters included in the selected area as the OCR result to be used for the file name, and the setting means makes settings for generating the file name based on the arrangement order of the multiple items arranged in the first area. [Effects of the Invention]

[0008] According to the technology disclosed herein, it becomes possible to more easily set rules regarding folder allocation and file naming when converting and saving data such as scanned images of documents and received faxes into files. [Brief explanation of the drawings]

[0009] [Figure 1] A diagram showing the overall configuration of an image processing system [Figure 2] Block diagram showing the hardware configuration of an MFP [Figure 3] Block diagram showing the hardware configuration of the MFP linked server and storage server [Figure 4] Block diagram showing the software configuration of the image processing system [Figure 5] Figure 10 shows an example of a folder distribution rule setting screen [Figure 6] Figure 10 shows an example of a folder distribution rule setting screen [Figure 7] Figure 10 shows an example of a folder distribution rule setting screen [Figure 8] Figure 10 shows an example of a folder distribution rule setting screen [Figure 9] Figure 10 shows an example of a folder distribution rule setting screen [Figure 10] Figure showing an example of displaying the set folder distribution rules [Figure 11] Figure 10 shows an example of a folder distribution rule setting screen [Figure 12] Figure 10 shows an example of a folder distribution 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 for setting properties [Figure 16] FIG. 1A is a diagram showing an example of a folder allocation rule setting screen, and FIG. 1B is a diagram showing an example of a file naming rule setting screen. [Figure 17] Flowchart showing details of the property setting screen display process [Figure 18] FIG. 10 is a diagram showing how attribute values ​​of a custom token are entered on a property setting screen. [Figure 19] A diagram showing an example of a scan profile setting screen [Figure 20] A diagram showing an example of a screen for editing a scan profile. [Figure 21] A diagram showing an example of a screen for adding a scan profile. [Figure 22] A diagram showing an example of a screen for adding a scan profile. [Figure 23] FIG. 10 is a diagram showing an example of a destination setting screen. [Figure 24] Figure showing an example of the custom token normalization rule setting screen [Figure 25] 10 is a flowchart showing details of a process for inputting attribute values ​​of a custom token on a property setting screen. [Figure 26]Figure showing how to select a custom token normalization rule on the folder distribution rule settings screen [Figure 27] Figure showing how to select a custom token normalization rule in the property settings screen DETAILED DESCRIPTION OF THE INVENTION

[0010] The following describes embodiments of the present invention with reference to the drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0011] [Embodiment 1] <System configuration> 1 is a diagram showing the overall configuration of an 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 client PC 111 are connected via a LAN (Local Area Network) to be able to communicate with various devices that provide various services over the Internet.

[0012] The MFP110 is an example of an information processing apparatus 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 apparatus such as a desktop terminal or a mobile terminal that can receive the provision of cloud services via the Internet. The server apparatuses 120 and 130 are both information processing apparatuses that provide cloud services. The server apparatus 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 apparatus 130 that provides another service. Hereinafter, the cloud service provided by the server apparatus 120 will be referred to as the "MFP cooperation service". The server apparatus 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 apparatus 120 that provides the MFP cooperation service will be referred to as the "MFP cooperation server", and the server apparatus 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> FIG. 2 is a block diagram showing the hardware configuration of the MFP 110. The MFP 110 includes a control unit 210, an operation unit 220, a printer unit 221, a scanner unit 222, and a modem 223. The control unit 210 is composed of the following units 211 to 219 and controls the overall operation of the MFP 110. The CPU 211 reads and executes control programs (programs corresponding to various functions shown in the software configuration diagram described below) stored in the ROM 212. The RAM 213 is used as a temporary storage area such as the main memory and work area of ​​the CPU 211. Note that in this embodiment, one CPU 211 uses one memory (RAM 213 or HDD 214) to execute each process shown in the flowcharts described below, but this is not limiting. For example, each process may be executed by using multiple CPUs, multiple RAMs, or multiple HDDs in cooperation with each other.

[0015] The HDD 214 is a mass storage unit that stores image data and various programs. The operation unit I / F 215 is an interface that connects the operation unit 220 and the control unit 210. The operation unit 220 is equipped with a touch panel, a keyboard, etc., and accepts operations / inputs / instructions from the user. Note that touch operations on the touch panel include operations with a person's finger and operations with a touch pen. The printer I / F 216 is an interface that connects the printer unit 221 and the control unit 210. Image data to be printed is transferred from the control unit 210 to the printer unit 221 via the printer I / F 216 and printed on a 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 an original placed on a platen or an auto document feeder (ADF), not shown, to generate scanned image data, which is then input 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 in the HDD 214, or sent as a file or email to an external device such as the MFP linked server 120 via a LAN. The modem I / F 218 is an interface that connects the modem 223 and the control unit 210. The modem 223 transmits image data via facsimile to a facsimile machine (not shown) on the PSTN. The network I / F 219 is an interface that connects the control unit 210 (MFP 110) to a LAN. The MFP 110 uses the network I / F 219 to transmit image data and information to various services on the Internet and to receive various information. The hardware configuration of the MFP 110 described above is an example, and other components may be included as needed, or some components may not be included.

[0017] <Hardware configuration of client PC and server device> 3 is a block diagram showing the hardware configuration of client PC 111, MFP collaboration server 120, and storage server 130. Client PC 111, MFP collaboration server 120, and storage server 130 are each composed of a CPU 311, ROM 312, RAM 313, HDD 314, and network I / F 315. CPU 311 controls overall operation by reading out control programs stored in ROM 312 and executing various processes. RAM 313 is used as temporary storage area such as the main memory and work area of ​​CPU 311. HDD 314 is a mass storage unit that stores image data and various programs. Network I / F 315 is an interface that connects client PC 111, MFP collaboration server 120, and storage server 130 to the Internet. MFP collaboration server 120 and storage server 130 receive various processing requests from other devices (such as MFP 110 and client PC 111) via network I / F 315 and return processing results corresponding to the requests.

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

[0019] <MFP software configuration> The function modules of the MFP 110 are broadly divided into two: a native function module 410 and an additional function module 420. The native function module 410 is an application that is provided as standard in the MFP 110, whereas the additional function module 420 is an application that is additionally installed in the MFP 110. The additional function module 420 is an application based on Java (registered trademark), and makes it easy to add functions to the MFP 110. Note that other additional applications (not shown) may also be installed in the MFP 110.

[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] Display control unit 421 displays a user interface screen (UI screen) for accepting various user operations on the touch panel of operation unit 220. The various user operations include, for example, input of login authentication information for accessing MFP linked server 120, scan settings, setting rules related to folder allocation and file naming, instructions to start scanning, instructions to save files, and the like.

[0022] In response to a user operation performed on the UI screen (for example, pressing the "Start Scan" button), scan control unit 422 instructs scan execution unit 411 to execute a scan process along with scan setting information. In accordance with the scan process execution instruction from scan control unit 422, scan execution unit 411 causes scanner unit 240 to execute a document reading operation via scanner I / F 217 and generates scanned image data. The generated scanned image data is stored in HDD 214 by scanned image management unit 412. At this time, information about a scanned image identifier that uniquely identifies the stored scanned image data is notified to scan control unit 422. The scanned image identifier is a number, symbol, alphabet, or the like that uniquely identifies an image scanned by MFP 110. Scan control unit 422, for example, acquires scanned image data to be converted into a file from scanned image management unit 412 using the scanned image identifier. Then, scan control unit 422 instructs collaboration service request unit 423 to request the MFP collaboration server 120 to perform the processing required for the file conversion.

[0023] Cooperation service request unit 423 requests various processes from MFP cooperation server 120 and receives the responses. The various 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 MFP cooperation server 120.

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

[0025] <Server device software configuration> First, the software configuration of the MFP linked server 120 will be described. The MFP linked server 120 includes 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 waits to receive a request from an external device and instructs the image processing unit 432, the storage server access unit 433, and the data management unit 434 to execute a predetermined process according to the content of the received request. The image processing unit 432 performs image analysis processes, such as character region detection, character recognition, and similar document determination, as well as image processing processes, such as rotation and tilt correction, on scanned image data sent from the MFP 110. The storage server access unit 433 makes processing requests to the storage server 130. Cloud services expose various interfaces for saving files to storage servers and retrieving saved files using protocols such as REST and SOAP. The storage server access unit 433 uses the exposed interfaces to make requests to the storage server 130. Data management unit 434 holds and manages user information and various setting data managed by MFP linkage server 120. Display control unit 435 receives requests from a web browser running on MFP 110 or client PC 111 connected via the Internet, and returns screen configuration information (HTML, CSS, etc.) required for screen display. Via the screen displayed by the web browser, the user can check registered user information and change rule settings related to scan settings, folder allocation, and file naming.

[0026] Next, the software configuration of storage server 130 will be described. Storage server 130 has a request control unit 441, a file management unit 442, and a display control unit 443. Request control unit 441 stands by in a state in which it can receive requests from external devices, and in this embodiment, instructs file management unit 442 to save received files or read saved files in response to requests from MFP-linked server 120. It then returns a response in response to the request to MFP-linked server 120. Display control unit 443 receives requests from a web browser running on MFP 110 or client PC 111 connected via the Internet, and returns screen configuration information (HTML, CSS, etc.) required for screen display. The user can check or obtain saved files via a screen displayed in the web browser.

[0027] Although not shown in FIG. 4, the client PC 111 also includes the same function module as the aforementioned additional function module 420.

[0028] <Folder sorting rule settings> Next, a description will be given of setting rules for allocating destination folders when a scanned image of a document is converted into a file and saved in the storage server 130. In this embodiment, various settings, including the setting of folder allocation rules, are performed in the client PC 111. Note that control such as displaying the various UI screens described below and saving the set rules is realized by the aforementioned additional function module 420 provided in the client PC 111. In other words, the contents described below can also be performed by the MFP 110 provided with the additional function module 420.

[0029] 5 is a diagram showing an example of a UI screen (hereinafter referred to as a "folder allocation rule setting screen") that is displayed on the display (not shown) of client PC 111 and that allows the user to set rules regarding file allocation destinations (save destination folders). The folder allocation rule setting screen 500 shown in FIG. 5 shows an 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 has a "Save" button 505 for confirming and saving the set rule.

[0030] In this specification, the term "token" refers to a unit item that allows a user to specify a character string (including symbols) used in property information required when saving a file to the storage server 130, taking into account its attributes. Tokens include general tokens (general items) that correspond to character strings with predetermined attributes, and special tokens (special items) that correspond to character strings with any attributes that can be customized and freely set by the user. The system tokens and delimiter tokens described below are general tokens, while the custom tokens described below are special tokens. These tokens are represented as UI elements that are the target of user operations such as dragging and dropping on the various setting screens that will be described below.

[0031] Various tokens are displayed in a list in the system token area 502, delimiter token area 503, and custom token area 504. Folder allocation rules created using the various tokens are displayed in the rule editing area 501. The folder allocation rules include information about the folder path of the destination (save folder) for the scanned data and the hierarchical structure of the folders, 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, delimiter token area 503, and custom token area 504 by dragging it, and drop it into the token drop area 507. As a result, a new folder is created in a pseudo-manner, with the folder name (folder path) containing the character string corresponding to the token selected by dragging.

[0033] The system token area 502 displays tokens whose attribute values ​​are user environment variables, such as the "logged-in user's display name," "time," and "date." The delimiter token area 503 displays tokens whose attribute values ​​are delimiters (symbols), such as an underscore or a hyphen. The custom token area 504 displays tokens whose attribute values ​​are arbitrary strings selected from the OCR results (recognized strings) of a scanned image (or manually entered). Users can freely create custom tokens. For example, when a "Drag to create token" token 506 displayed in the custom token area 504 is dropped into the token drop area 507, an input field for entering the attribute name representing the token is displayed. In other words, the "Drag to create token" string displayed on the token 506 has a different meaning from the strings displayed on the system token and delimiter token. In the case of the token 506, it is not the attribute name itself that represents the content of the token, but rather serves as a description prompting the user to enter the attribute name and create a new token. Details of custom tokens, such as the specific method for setting the attribute name assigned to a custom token, will be described later.

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

[0035] Here, we will review the destination folder allocation rules in this embodiment. First, there are no particular restrictions on the combination or order of tokens that can be set as folder allocation rules. For example, a rule may be created in which a folder name is composed only of delimiter tokens in the delimiter token area 503, or a rule may be created that uses only the same system tokens. However, the content 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, it is possible to freely change the attribute names of custom tokens displayed in the custom token area 504, or to delete the custom tokens themselves.

[0036] FIG. 6 shows the state of the folder allocation rule setting screen 500 when a user drags and drops a system token from the system token area 502 into the rule editing area 501. Specifically, the state is shown when a system token 511, which has the attribute name "login user's display name" among the multiple system tokens displayed in the system token area 502, is dropped into the token drop area 507. Looking at the rule editing area 501 in FIG. 6, a new token 508, which has the attribute name "login user's display name," is placed in the position of the token drop area 507 where the user performed the drop operation (see FIG. 5). At the same time, new token drop areas 514 and 515 are also created. In the state shown in FIG. 6, if a token from the group of tokens present in the various token areas 502 to 504 is selected and dragged and dropped into the token drop area 514, a new token drop area is created (not shown). Then, if another token is dragged and dropped into the newly created token drop area, another token drop area is created. FIG. 7 shows the state of the folder allocation rule setting screen 500 after repeating these operations. 7, two new tokens (token 516 with "{space}" as the attribute name and token 517 with "scan profile name" as the attribute name) have been added, and token drop area 518 has also been created. In this case, the three tokens 508, 516, and 517 are set as the folder names of folders in the first hierarchy (top hierarchy). According to the example in FIG. 7, a folder with "(login user's display name) (scan profile name)" as the folder path will be created as the top hierarchy folder. On the other hand, in rule editing area 501 shown in FIG. 6, if an arbitrary token is dragged and dropped into token drop area 515 in the second hierarchy, a new token drop area will also be created. In rule editing area 501 in FIG. 7, token 519 with "date (year, 4 digits)" has been added, and two more token drop areas 520 and 521 have also been created.Token drop area 521 is used when adding a new token to a second-level folder that is determined to use token 519. Token drop area 520 is used when setting the first token for a third-level folder.

[0037] As is clear from the explanation so far, a folder that uses the three tokens 508, 516, and 517 in its folder name and a folder that uses the token 519 in its folder name are at different levels (see FIG. 7). In other words, in terms of the folder structure, the folder that uses the token 519 in its folder name is at a lower level than the folder that uses the three tokens 508, 516, and 517 in its folder name. Note that 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 tokens.

[0038] Deleting a token Next, a case where a user deletes a token for each folder hierarchy set as described above will be described. When a user hovers the mouse over any of the tokens displayed in the rule editing area 501, an "x" button (not shown) appears on the token. The user can delete any token by pressing this "x" button. FIG. 8 shows the state of the folder allocation 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 of FIG. 8, UI blocks 522 and 523 labeled "Deleted" are displayed at the location where the token was deleted. These UI blocks 522 and 523 labeled "Deleted" function as token drop areas. When a new token is dragged and dropped onto these UI blocks, the new token is set in the location labeled "Deleted." As described above, in this embodiment, even if a token displayed in the rule editing area 501 is deleted, the area where the deleted token existed is maintained. However, the area where the deleted token was deleted may be displayed by narrowing the area without displaying the "Deleted" UI block to allow a new token to be placed there. When the user presses the "Save" button 505 in the state shown in FIG. 8, the folder sorting rule setting screen 500 transitions to the state shown in FIG. 9, and the "Deleted" UI block disappears.

[0039] <<Checking the set folder sorting rules>> FIG. 10 is a diagram showing an example of a state in which a folder allocation rule created and saved by a user via the folder allocation rule setting screen 500 is displayed on a main screen (not shown). In the example shown in FIG. 10, a folder path 1001 is displayed, with slashes representing the separators between folder levels. The folder path 1001 shown in FIG. 10 corresponds to the result of setting a predetermined token for each of the folders in the first to third levels, as in the rule editing area 501 in FIG. 12 (described later). If the token set in the rule editing area 501 shown in FIG. 8 is followed, the displayed folder path would be "{login user's display name} / date (month)." In other words, in the case of FIG. 8, the token for the folder in the second level is deleted, and folder paths according to the tokens set for the folders in the first and third levels are displayed. In this way, if a token for a folder in a specific level no longer exists due to the deletion of a set token, a folder path with the folders in that level collapsed is displayed.

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

[0041] FIG. 12 shows the state of the folder sorting rule setting screen 500 after a custom token has been set by the user pressing the "Save" button 1102. A token 1201 having the character string "company name" entered in the text field 1101 as its attribute name is displayed as a token for a third-level folder in the rule editing area 501. Furthermore, a custom token 1202 having the character string "company name" as its attribute name is displayed in the custom token area 504 so that the custom token created this time can be reused. The character string entered in the text field 1101 may be saved as the attribute name of a reusable custom token immediately after the attribute name is entered in the text field 1101 (i.e., before the "Save" button 1102 is pressed). Furthermore, if a new custom token is created with the same attribute name as an existing system token or delimiter token, it is also added to the custom token area 504 as a new custom token. However, even if a character string identical to the attribute name of a custom token already existing in the custom token area 504 is entered into the text field 1101, a duplicate custom token with the same attribute name will not be displayed in the custom token area 504. When a character string that is already being used as an attribute name of an existing custom token is entered into the text field 1101, the user may be notified by, for example, displaying a message informing them that the character string cannot be used as an attribute name. Alternatively, the entry of the already used character string into the text field 1101 and the setting of a custom token based on that input may be permitted, but the addition of the character string to the custom token area 504 may not be allowed. Furthermore, even if a custom token with the same attribute name as a system token or delimiter token is created, it may not be possible to register or use it as a custom token.

[0042] <Setting custom token extraction rules and validation rules> A method for setting string extraction rules and string verification rules for a custom token will be described. In this embodiment, the setting of string extraction rules and string verification rules will also be described on the client PC 111.

[0043] String extraction rules are rules that normalize (extract or delete) 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 values ​​entered in attribute value input fields. On the other hand, string validation rules are rules that validate values ​​entered in attribute value input fields when setting properties. If the result of verifying the string validation rules shows that the string entered in the attribute value input field does not conform to the specified format, a warning to that effect is displayed to the user.

[0044] FIG. 24 is a diagram showing an example of a UI screen (hereinafter referred to as the "custom token normalization rule setting screen") that is displayed on the display of the client PC 111 and that allows the user to set string extraction rules and string verification rules. The custom token normalization rule setting screen 2400 shown in FIG. 24 shows an 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 on the folder sorting rule setting screen 500 of FIGS. 11 and 12. Alternatively, a custom token registration screen (not shown) may be provided separately, and may be displayed when the "Add" button on the custom token registration screen is pressed and an attribute name is subsequently entered.

[0045] The custom token normalization rule setting screen 2400 has setting items for display name 2401, default value 2402, data extraction rule 2403, and data validation rule 2404. The setting value for each setting item is determined by entering any string in the text field corresponding to each setting item. In display name 2401, an attribute name is set. In default value 2402, a value to be entered by default in the attribute value input field can be set. In data extraction rule 2403, the above-mentioned string extraction rule can be set. In data validation rule 2404, the above-mentioned string validation rule can be set. The default value 2402, data extraction rule 2403, and data validation rule 2404 may be left blank, or values ​​may be entered in any combination.

[0046] Furthermore, the format for inputting setting values ​​into the data extraction rule 2403 and the data validation rule 2404 is not limited. For example, the user can directly input a regular expression, or alternatively, a pull-down menu of options can be displayed and selected from. For example, if a user wants to set a string extraction rule that removes the character string "Kaisho" (Corporation) from a trade name, this can be achieved by directly entering ".+(?=Kaisho)|(?<=Kaisho).+" into the data extraction rule 2403. Furthermore, if a user wants to set a string validation rule that verifies whether an input string consists only of half-width numbers, this can be achieved by directly entering "[0-9]+" into the data validation rule 2404. Instead of such direct input, an example of displaying options is, for example, displaying an option such as "Remove trade name (Corporation, etc.)" for the string extraction rule. Alternatively, displaying options such as "Date format: YYYYMMDD" or "Date format: YYYY year MM month DD day" for the string validation rule.

[0047] <File naming rule settings> Next, a description will be given of the setting of a naming rule for file names assigned when a scanned image or the like is filed. In this embodiment, the setting of the file naming rule is also performed on the client PC 111. FIG. 13 is a diagram showing an example of a UI screen (hereinafter referred to as a "file naming rule setting screen") that is displayed on a display (not shown) of the client PC 111 and allows a user to set a file naming rule. The file naming rule setting screen 1300 shown in FIG. 13 shows an initial display state, and has the same screen configuration as the folder allocation 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. The rule editing area 1301 includes a token drop area 1305, and a "Save" button 1306 at the bottom of the screen for confirming and saving the set file naming rule. The following description will focus on the differences from the folder allocation rule setting screen 500.

[0048] File naming rules are also created by dragging and dropping various tokens displayed in the system token area 1302, delimiter area 1303, and custom token area 1304 and placing them in the rule editing area 1301. The difference from the folder allocation rule setting screen 500 is that file names do not have a hierarchical structure, and multiple token drop areas are not displayed even if a new token is added to the rule editing area 1301.

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

[0050] 13 displays a custom token 1311 with an attribute name of "company name" and a custom token 1312 with an attribute name of "quote." Of these two custom tokens, the custom token 1311 for "company name" corresponds to the custom token 1202 created on the folder allocation rule setting screen 500 described above. In other words, the custom token created when setting the folder allocation rule is displayed as a custom token that can also be used when setting the file naming rule. Similarly, the custom token 1312 for "quote" 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 of the folder allocation rule setting screen 500 when the folder allocation rule setting screen 500 is opened after its creation. In this way, custom tokens can be shared between the folder allocation rule setting screen and the file naming rule setting screen.

[0051] <Property settings when creating a file> Next, a specific process flow for setting properties when converting scanned images or the like into files will be described. Here, properties refer to the file name, folder path, metadata, and the like required for each piece of data to be converted into a file. For example, when scanning a document, converting it into a file, and saving it in the storage server 130, the user sets the required properties via a property setting screen that reflects the destination folder allocation rules and file naming rules set as described above.

[0052] FIG. 14 illustrates an example of a property setting screen. The property setting screen 1400 shown in FIG. 14 is initially displayed and has two panes: a preview pane 1401 and a property pane 1402. A preview of a scanned image of the "Quote" form is currently displayed in the preview pane 1401. The preview pane 1401 allows users to scroll and zoom the scanned image to display any position on the scanned image. The property pane 1402 is a pane for displaying and editing properties to be assigned to the scanned image to be processed. The property pane 1402 currently 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 allocation rule set in the folder allocation rule setting screen 500 described above. Furthermore, "{quotation}_20200227_{company name}_1" displayed in the file name display area 1404 is based on the file name naming rules set on the file naming rule setting screen 1300. Details of the display of folder paths and file names based on each rule will be described later.

[0053] <Property setting process flow> 15 is a flowchart showing the flow of processing when a user sets file properties via the above-described property setting screen 1400 on the MFP 110. Execution of this flow is triggered by the display control unit 421 of the MFP 110 receiving a user instruction to open the property setting screen 1400. Assume that the following folder allocation rules and file naming rules are set on the setting screens in FIGS. 16(a), 16(b), and 16(c), respectively.

[0054] <Folder sorting rule settings> "'Login user's display name' (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)'" <<Custom Token Normalization Rule Settings for Company Name (Custom Token)>> "Display name: Company name, Default value: Empty, Data extraction rule: ".+(?=Inc.)|(?<=Inc.).+" (remove "Inc.") from the beginning and end, Data validation rule: ".+" (not empty)" Below, we will explain in detail using the flow in Figure 15. In the following explanation, the symbol "S" represents a step.

[0055] First, in S1501, information about the folder allocation rule set by the user is acquired. Subsequently, in S1502, information about the file naming rule set by the user is acquired. In S1503 and S1504, the process of acquiring attribute values ​​is repeated for the number of system tokens included in the information acquired in S1501 and S1502. Specifically, character strings corresponding to the user's environment variables corresponding to the system tokens are acquired from data management unit 434 of MFP linked server 120. For example, for the system tokens "year," "month," and "day," the character strings "2020," "2," and "27," representing the scanned date, are acquired, respectively. Furthermore, for the system token "logged-in user's display name," the character string "tokita," representing the user name of the user registered in the system, is acquired. In the above example, because the folder allocation rule contains four system tokens and the file naming rule contains three system tokens, the process of acquiring attribute values ​​is repeated seven times. If the acquired rules do not contain a system token, the processes of S1503 and S1504 are skipped and the process proceeds to S1505. Unlike custom tokens and delimiter tokens, the attribute values ​​of system tokens change dynamically depending on the system settings. Therefore, the corresponding character strings (attribute values) for each system token must be updated every time the system settings are changed.

[0056] In S1505, a folder path is generated using the folder allocation rule acquired in S1501 and the character string for each system token acquired in S1504. In the following S1506, a file name is generated using the file naming rule acquired in S1502 and the character string for each system token acquired in S1504. At this time, for delimiter tokens, the corresponding delimiter, such as a period or space, is inserted. For custom tokens, the character string for the corresponding attribute name is provisionally inserted.

[0057] In the next step S1507, the above-mentioned property setting screen 1400 is displayed on the display (not shown) of the client PC 111. Fig. 17 is a flowchart showing the details of the property setting screen display process. A detailed explanation will be given below along the flow of Fig. 17.

[0058] In S1701, the folder path generated in S1505 is displayed in the folder path display area 1403 of the property setting screen 1400. As described above, in the example of FIG. 14, " / tokita / (company name) / 2020.02.27" is displayed. In this case, the system token with the "logged-in user's display name" as its attribute name contains the string "tokita." Furthermore, the custom token with the "company name" as its attribute name contains the string "company name," indicating the attribute name, because the string is entered by selecting a desired text block from the scanned image, for example. Furthermore, for each system token with the attribute names "year," "month," and "day," the numbers "2020," "02," and "27," representing the date the scanned image in the preview pane 1401 was acquired, are inserted between the delimiter token "." (period). If the scan date changes, the numbers assigned to these system tokens will change.

[0059] In S1702, it is determined whether or not a custom token is included in the folder sorting rule acquired in S1501. If a custom token is included, the process proceeds to S1703; if not, the process proceeds to S1705. In the above example, 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 the custom token is repeated the number of times equal to the number of custom tokens included in the folder sorting rule. In the example above, since the folder sorting rule contains one custom token, only one attribute value input field is displayed (see FIG. 14), but if multiple custom tokens are included, multiple attribute value input fields will be displayed. Note that if the folder sorting rule does not contain a custom token (No in S1702), the attribute value input field is not displayed.

[0061] In the next step S1705, the file name generated in step S1506 is displayed in the file name display area 1404 of the property setting screen 1400. As described above, in the example of FIG. 14, "{quote}_20200227_{company name}_1" is 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 connected together without using delimiters. Also, for the custom tokens with "quote" and "company name" as attribute names, character strings indicating the respective attribute names are temporarily entered, as described above.

[0062] In S1706, it is determined whether or not the file naming rule acquired in S1502 includes a custom token. If a custom token is included, the process proceeds to S1707; if not, the process exits. In this case, as described above, the custom tokens with the attribute names "quote" and "company name" are included, so the process proceeds to S1707.

[0063] In S1707 and S1708, the process of displaying the attribute value input field 1406 for the custom token is repeated the same number of times as the number of custom tokens included in the file naming rule. In the above example, since the number of custom tokens included in the file naming rule is two, the number of displayed attribute value input fields 1406 is also two (see FIG. 14). If the file naming rule does not include a custom token (No in S1706), the attribute value input field 1406 is not displayed.

[0064] The above is the content of the property setting screen display process. As described above, in this embodiment, when creating rules for folder paths and file names, common tokens (custom tokens, system tokens) can be used. Even if common tokens are used, folder paths and file names are displayed separately in the property pane 1402.

[0065] 18 shows how the user inputs custom token attribute values ​​on the property setting screen 1400 after the above-described property setting screen display process has been completed. The attribute value input fields 1405 / 1406 corresponding to each custom token display an attribute name 1801, an attribute value 1802, and a clipped image 1803 corresponding to the attribute value. When the user does not select a text block containing the custom token's attribute value (character string) from the preview pane 1401, the attribute value 1802 displays "none (empty)," as in the attribute value input field 1406 of a custom token with the attribute name "quote." The clipped image 1803 corresponding to the attribute value also displays blank.

[0066] A user entering an attribute value for a custom token first selects the attribute value input field for the target custom token from among the attribute value input fields displayed in the property pane 1402. In FIG. 18 , attribute value input field 1405 is selected and highlighted. In this state, the user specifies (e.g., clicks on) a text block containing the attribute value (character string) of the custom token from the scanned image displayed in the preview pane 1401. The clicked text block is highlighted in the preview pane 1401, perhaps by adding a border or color. At the same time, the selected attribute value input field 1405 in the property pane 1402 displays the character string contained in the specified text block as attribute value 1802. At this time, the attribute value 1802 displays the value after applying the data extraction rules and data validation rules set on the "Custom Token Normalization Rule Setting Screen." Furthermore, the image portion corresponding to the text block is displayed as a clipped image 1803 corresponding to the attribute value. When an attribute value is input to the custom token in this way, the content is reflected in the folder path display area 1403 and the file name display area 1404 .

[0067] Here, the process of inputting the value of a text block selected by the user into the attribute value input field will be described with reference to the flowchart shown in Figure 25. In the following description, the symbol "S" represents a step.

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

[0069] In S2503, the OCR character string of the text block selected by the user is obtained. Specifically, the cooperation service request unit 423 sends an analysis request for the selected text block to the MFP cooperation server 120, and the image processing unit 432 performs OCR processing based on the request. The execution result of the OCR processing is then returned to the cooperation service request unit 423, and the display control unit 421 acquires the execution result. For example, with the attribute value input field 1405 of a custom token with "Company Name" as the attribute name selected in the property pane 1402, the user clicks on the text block 1804 of "Plastic Mold Co., Ltd." in the preview pane 1401. Then, the OCR processing is performed on the text block 1804 as described above, and "Plastic Mold Co., Ltd." is acquired as the OCR character string.

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

[0071] In S2505, the set string extraction rule is acquired. In this case, it is assumed that the string extraction rule acquired is one that states, "Delete 'Co., Ltd.' from the trade name." In the following S2506, data that will become attribute values ​​is extracted from the OCR string acquired in S2503 in accordance with the string extraction rule. Currently, the OCR string for "Plastic Mold Co., Ltd." has been acquired, so "Plastic Mold" will be extracted from it with the "Co., Ltd." removed.

[0072] In the next step S2507, an attribute value is entered into the attribute value input field. In this case, the character string "Plastic Mold" is entered as the attribute value in the attribute value input field 1405. When the attribute value is entered in this manner, the "{Company Name}" portion in the folder path display area 1403 is replaced with "Plastic Mold." Furthermore, since a custom token with "Company Name" as the attribute name is also set in the file naming rule, synchronization processing is performed on the attribute value input field 1406. In other words, the "{Company Name}" portion in the file name display area 1404 is also replaced with "Plastic Mold." Note that synchronization processing is also performed when a method other than specifying an arbitrary text block in the preview pane 1401 is used, for example, when a character string to be used as the attribute value is manually entered using a soft keyboard (not shown). In other words, the same attribute value is set for all common custom tokens, regardless of the method of inputting the attribute value. Note that if you select an attribute value input field for a custom token for which an attribute value has already been set and specify a text block other than the currently specified text block, the existing attribute value will be overwritten by the newly entered attribute value.

[0073] Next, in S2508, it is determined whether a string verification rule has been set for the selected attribute value input field. If not, the process ends. If a string verification rule has been set, the process proceeds to S2509. In S2509, the set string verification rule is acquired. Then, in S2510, the attribute value entered in S2507 is verified in accordance with the string verification rule acquired in S2509. If the verification results in an invalid attribute value, the process proceeds to S2511, where a message indicating that the entered attribute value is invalid is displayed (not shown). On the other hand, if there is no problem with the verification results, the process ends.

[0074] After completing the above-described processing for all custom tokens, the user presses “Send” button 1805. This causes the scanned image data to be sent from MFP 110 to MFP linked server 120, along with the folder path and file name information set on property setting screen 1400. Then, in MFP linked server 120, storage server access unit 433 uses the received information and data to assign the specified file name to the scanned image data, file it, and save it in the specified folder on cloud server 130. If the user presses “Send” button 1805 when no attribute value is set for the custom token, a folder path and file name are generated and saved with the attribute value section left blank. For example, in property setting screen 1400 in FIG. 18 , no attribute value is set for the custom token with the attribute name “Quote.” Pressing “Send” button 1805 in this state causes MFP linked server 120 to request that the scanned image data displayed in preview pane 1401 be saved to storage server 130 under the following conditions:

[0075] Destination folder: " / tokita / Plastic Mold Co., Ltd. / 2020.02.27" File name: "_20200227_Plastic Mold Co., Ltd._1" <Scan profile> The folder allocation rules and file naming rules set as described above can be set for each type of scan workflow. Here, a scan workflow refers to a workflow for sending scanned image data obtained by scanning a document such as a form to a specific destination (e.g., storage server 130) under specific conditions. The conditions and destination information for each scan workflow are managed by a scan profile. By creating a scan profile in advance, a user can easily achieve a desired scan workflow.

[0076] FIG. 19 shows an example of a UI screen (hereinafter referred to as a "scan profile setting screen") for setting a scan profile, which is displayed on the operation unit 220 of the MFP 110 (or the client PC 111). The scan profile setting screen 1900 shown in FIG. 19 is composed of a side menu area 1901 and a menu area 1902. When "Scan" is selected from the items displayed in the side menu area 1901, the screen transitions to a UI screen (hereinafter referred to as a "scan profile editing screen") for performing editing tasks such as adding and deleting scan profiles, which will be described later. The menu area 1902 displays multiple icons corresponding to scan profiles. Each time the user creates a scan profile, an icon corresponding to that scan profile is added to the menu area 1902. Furthermore, when a button 1903 at the bottom of the menu area 1902 is pressed, icons of other scan profiles that could not be displayed are displayed and can be viewed.

[0077] 19 is a UI screen that is displayed when a user with a user ID of "user a" logs in to the MFP 110. The scan profile displayed may differ depending on the logged-in user, or there may be a scan profile that can be commonly used by multiple users.

[0078] Suppose the user selects an icon corresponding to an arbitrary scan profile on the scan profile setting screen 1900 and then instructs execution of a scan. Then, the property setting screen 1400 is displayed, which determines folder names and file names according to the folder allocation rule and file naming rule corresponding to the selected scan profile. For example, suppose the following folder allocation rule and file naming rule are associated with the scan profile indicated by the icon 1904:

[0079] Folder allocation rule: " / {Login user's display name} / {Company name} / {Year}{Month}{Day} / " File naming rule: "{Quote}_{Year}{Month}{Day}_{Company name}" In this case, the scanned image generated after the icon 1904 is selected is displayed in the preview pane 1401 of the property setting screen 1400. Then, the folder allocation rule of the above content associated with the scan profile corresponding to the selected icon 1904 is displayed in the folder path display area 1403. Furthermore, the file naming rule of the above content associated with the same scan profile is displayed in the file name display area 1404.

[0080] <<Creating a scan profile>> Next, a method for creating a scan profile will be described. A user logs in to MFP linked server 120 via client PC 111, for example, and can display a UI screen for editing a scan profile (hereinafter referred to as the "editing screen") as shown in FIG. 20 by transitioning from a main screen (not shown) that is displayed after logging in. Editing screen 2000 shown in FIG. 20 includes menu list area 2001, profile list area 2002, and profile setting area 2003. Profile list area 2002 displays a list of scan profiles that are being created or have already been created. Profile setting area 2003 displays the settings of a scan profile that the user selects from the list displayed in profile list area 2002. Profile list area 2002 and profile setting area 2003 are displayed by selecting the item "scan profile" in menu list area 2001.

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

[0082] Fig. 22 shows the state in which setting items are displayed when the "Workflow Settings" tab is selected on the addition screen 2100 of Fig. 21. The displayed setting items include a "Set rules for destination folder" button 2201, and selecting this button 2201 displays the folder allocation rule setting screen 500 described above. At this time, if folder allocation rules have already been created, the created folder allocation rules are displayed around the "Set rules for destination folder" button 2201 (directly above it in the example of Fig. 10 described above).

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

[0084] Once the minimum information required to realize the scan workflow has been set as described above, the screen returns to the edit screen 2000 of Fig. 20. At this time, the newly created scan profile is added and displayed in the profile list area 2002.

[0085] <Modification> Next, we will explain a modified example that makes it easier for users to set string verification rules and string extraction rules for custom tokens that have specific attribute names that are frequently used, such as "company name" or "date." Here, we will refer to the specific custom tokens in this modified example as "attribute type custom tokens."

[0086] FIG. 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. A context menu 2602 is displayed in a pull-down format below the dropped custom token. This context menu 2602 includes radio buttons 2602a to 2602c. The radio buttons correspond to "Set Data Normalization Rules," "Remove Trade Name (remove characters such as "Kaisho" from the trade name)," and "Do Not Set Data Normalization Rules." For example, a user who wants to set data normalization rules selects radio button 2602a. This sets the string verification rules and / or string extraction rules pre-associated with the attribute-type custom token. This allows the user to easily set a desired custom token with a string verification rule or string extraction rule attached without using the custom token normalization rule setting screen 2400. On the other hand, when radio button 2602c is selected, no normalization rules are set for the dropped attribute-type custom token. When radio button 2602b is selected, the dropped attribute type custom token is set to automatically delete characters such as "Kabushiki Kaisha" included in the trade name.

[0087] The display mode of this attribute type custom token may be changed depending on the scan profile selected by the user and the document type to be scanned. For example, when creating a scan profile for scanning business cards, the attribute type custom tokens that can be used in folder sorting rules and file name sorting rules may be limited to "company name," "department," "name," "phone number," and "email address." Furthermore, if the desired rule is not available in the options in the context menu, a text field may be provided so that the user can freely customize it using regular expressions, etc.

[0088] Furthermore, normalization rules may be set for custom tokens when a text block is selected in the preview pane 1401 of the property setting screen 1400. FIG. 27 shows the property setting screen 1400 when an attribute type custom token with "Company Name" as its attribute name is set as a folder allocation rule and a file name rule. The attribute value input field 2701 is currently selected and highlighted. When the user hovers the mouse over a text block 2702 in this state, a pop-up menu 2703 appears below the text block 2702. The contents displayed in the pop-up menu 2703 are the string validation rules and / or string extraction rules previously associated with the "Company Name" attribute type custom token. In this example, the user can set a normalization rule to remove the characters "Kaisho" ("Inc.") from the trade name by selecting "Remove Trade Name" from the displayed pop-up menu. In this way, normalization rules may be set when entering attribute values.

[0089] According to this modification, the effort required to set normalization rules for custom tokens is eliminated, making it easier for users to use string verification rules and string extraction rules.

[0090] As described above, according to this embodiment, a user can easily create and edit folder allocation rules and file naming rules that are required when saving scanned images of documents and the like as files.

[0091] The object of the present invention can also be achieved by performing the following process: a storage medium storing program code of software that realizes the functions of the above-described embodiments is supplied to a system or device, and a computer (or CPU, MPU, etc.) of the system or device reads 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 embodiments, and the program code and the storage medium storing the program code constitute the present invention. [Explanation of symbols]

[0092] 110 MFP 111 Client PC 120 MFP Collaboration Server 130 Storage Server 420 Additional Function Module 421 Display control unit

Claims

[Claim 1] means for providing a user interface screen for receiving operations relating to settings for generating a file name from a user; a setting means for performing settings for generating the file name based on an operation received from the user on the user interface screen; An information processing device having: the user interface screen includes a first area in which a plurality of 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 an OCR result of characters included in a selected area in the scanned image as the file name, Furthermore, for the first item, it is possible to set a rule for using the OCR result of some characters among the plurality of characters included in the selected area as the OCR result to be used for the file name, the setting means performs setting for generating the file name based on the arrangement order of the plurality of items arranged in the first area; 1. An information processing device comprising:

Images