Information processing system and program
The system addresses the issue of unintended read data usage by identifying users and their permissions, ensuring read data is handled correctly based on user authority, preventing unauthorized actions and enabling intended updates.
Patent Information
- Application Number
- JP2023085308
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-24
- Publication Date
- 2024-12-05
AI Technical Summary
Existing document processing systems fail to consider user authority when handling read data, leading to unintended usage of read data that does not match original document data.
An information processing system that identifies documents and users through document specifying information, user identification information, and usage authority information, determining how to handle read data based on these factors, including storage modes and updates according to user permissions.
Ensures read data is handled as intended by the user, preventing unauthorized saving or updating, and allowing authorized users to save or update data as needed.
Smart Images

Figure 2024168546000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing system and a program. [Background technology]
[0002] It is common to store document data in a storage device and read and print the document data when necessary. The scanned data generated by scanning a printed matter should essentially match the original document data, but there are cases where the printed matter is tampered with.
[0003] Therefore, for example, in Patent Document 1, address information indicating the storage location of the document data is added to the document data before it is saved on a server. When the approver receives the printout with the address information added in a non-visible manner, he / she reads it with a scanner. The address information is extracted from the read data of the printout obtained in this way, the document data specified by the extracted address information is obtained from the server, and it is determined whether the contents of the obtained document data and the read data match.
[0004] Furthermore, in Patent Document 1, even if the read data does not match the document data, the read data can be stored if the approver approves it. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2008-306650 A Summary of the Invention [Problem to be solved by the invention]
[0006] However, in the conventional technology, if the read data does not match the document data, it is always saved as a separate document. In other words, in the conventional technology, since the user's usage authority set in the document data is not referenced, for example, even if the user wants to update updatable document data with the read data, the read data is always saved as a separate document against the user's intention.
[0007] An object of the present invention is to enable a user to handle scanned document data as intended, as compared to a case where the user's usage authority for document data is not referred to. [Means for solving the problem]
[0008] The information processing system of the present invention is equipped with a processor, which extracts document identification information that identifies the document and user identification information that identifies a user who can use the document, which are attached to the printed document from the read data of the printed document obtained by printing the document data of the document, extracts user identification information that identifies a user who can use the document and usage authority information for the document granted to the user, which are set in the document data of the document identified by the extracted document identification information, and determines how to handle the read data in accordance with the extracted usage authority information.
[0009] The processor is further characterized in that, when the user identification information of an operator who caused a reading means to read the printed document and generate the read data matches the user identification information set in the document data of the document identified by the document identification information, the processor determines the form in which the read data is to be saved according to the writing authority of the operator set in the usage authority information.
[0010] The processor may also store the read data as a separate document from the document if the operator does not have writing authority.
[0011] The processor may also update the document data using the read data if the operator has write authority.
[0012] The processor is also characterized in that it does not allow the read data to be saved if the user identification information of the operator generating the read data does not match the user identification information set in the document data of the document identified by the document identification information.
[0013] In addition, even if the user identification information of the operator does not match the user identification information set in the document data of the document identified by the document identification information, if the usage authority information shows that proxy operation authority has been set for a user who can use the document, the processor requests approval of the proxy operation by the operator from the administrator of the document, and if approval is obtained from the administrator, allows the reading data to be saved.
[0014] The program of the present invention enables a computer to realize the following functions: extracting document identification information that identifies a document and user identification information that identifies a user who can use the document, which are attached to the printed document from the read data of the printed document obtained by printing the document data of the document; extracting user identification information that identifies a user who can use the document and usage authority information for the document granted to the user, which are set in the document data of the document identified by the extracted document identification information; and determining how to handle the read data in accordance with the extracted usage authority information. Effect of the Invention
[0015] According to the invention recited in claim 1, the scanned data of the document can be handled as intended by the user, as compared to a case where the user's usage authority for the document is not referred to.
[0016] According to the invention as recited in claim 2, the read data can be saved in a format according to the writing authority of the operator.
[0017] According to the invention as recited in claim 3, the read data can be treated as a document different from the original document.
[0018] According to the invention as set forth in claim 4, the read data can be treated as the original document.
[0019] According to the invention as set forth in claim 5, it is possible to prevent read data generated by an operation by a person who may be a fraudulent person and is not an authorized user from being stored.
[0020] According to the invention as set forth in claim 6, it is possible to have a person who is not an authorized user act as a proxy to store the read data.
[0021] According to the seventh aspect of the present invention, the scanned data of the document can be handled as intended by the user, compared to a case where the user's usage authority for the document is not referred to. [Brief description of the drawings]
[0022] [Figure 1] 1 is a schematic overall configuration diagram of an information processing system according to a first embodiment. [Diagram 2] 1 is a block diagram showing an information processing system according to a first embodiment. [Diagram 3] 4 is a diagram showing an example of a data configuration of document information added to document data handled in the first embodiment. FIG. [Figure 4] 11 is a flowchart showing processing in a cloud that handles read data in the first embodiment. [Diagram 5] 4 is a flowchart showing a save determination process in the first embodiment. [Figure 6] FIG. 11 is a block diagram showing an information processing system according to a second embodiment. [Figure 7] FIG. 11 is a diagram showing an example of a data configuration of document information added to document data handled in the second embodiment. [Figure 8]13 is a flowchart showing processing in the cloud that handles read data in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0023] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.
[0024] Embodiment 1 Fig. 1 is a schematic diagram showing an overall system configuration of an information processing system according to an embodiment of the present invention. Fig. 1 shows a cloud 10, a multifunction peripheral 20, an administrator terminal 30, and a user terminal 40, which are connected to the cloud 10 via a network 4 such as the Internet. The cloud 10 in this embodiment provides a service for storing and managing document data via the network 4.
[0025] The multifunction device 20 is a form of an image forming device equipped with various functions such as a printing function, a copying function, a scanning function, etc., and is a device with a built-in computer. That is, the multifunction device 20 has a CPU, a ROM, a RAM, a hard disk drive (HDD) as a storage means, a network interface (IF) provided as a communication means, and a user interface such as an operation panel. The multifunction device 20 also includes devices such as a scanner and a printer to provide various functions to the user. The multifunction device 20 in this embodiment may be realized by a conventional hardware configuration.
[0026] The administrator terminal 30 is a terminal device used by an administrator, and the user terminal 40 is a terminal device used by a user who uses documents, and both can be realized with a general-purpose hardware configuration that has existed for a long time, such as a personal computer (PC). That is, each of the terminals 30, 40 has a CPU, ROM, RAM, a hard disk drive (HDD) as a storage means, a network interface (IF) provided as a communication means, input means such as a mouse and keyboard, and a display means such as a display, or a user interface such as a touch panel.
[0027] The administrator who uses the administrator terminal 30 is the administrator of various documents managed by the cloud 10. The various documents are usually created by a user who uses a user terminal 40. The multifunction device 20, the administrator terminal 30, and the user terminal 40 each only need to have the same functions, so FIG. 1 illustrates one of each, but multiple devices may be connected to the network 4. The multifunction device 20 is basically installed in a certain on-premise environment. Since the administrator and the user work within the on-premise environment, it is assumed that the administrator terminal 30 and the user terminal 40 are installed in the same on-premise environment as the multifunction device 20, but they do not necessarily need to be installed in the on-premise environment as long as they can communicate with each other via the network 4.
[0028] Fig. 2 is a block diagram showing an information processing system 2 according to the present embodiment. In Fig. 2, components that are not used in the description of the present embodiment are omitted from the figure.
[0029] The cloud 10 includes a document management unit 11, a read data receiving unit 12, a read data processing unit 13, and a document database (DB) 14.
[0030] The document management unit 11 manages the registration, editing, deletion, etc. of document data in the document database 14. The read data receiving unit 12 receives read data transmitted from the multifunction device 20. The read data processing unit 13 executes processing related to the read data received by the read data receiving unit 12. Specifically, as will be described in detail later, the read data processing unit 13 determines how to handle the read data, for example, in what storage form the read data should be saved, or whether to save the data at all.
[0031] The read data processing unit 13 includes an encryption processing unit 131, a document information acquisition unit 132, a save determination unit 133, a read data saving unit 134, and a process control unit 135. The encryption processing unit 131 encrypts and decrypts the read data. The document information acquisition unit 132 acquires document information set in the document data of a document specified from address information extracted from the read data. The save determination unit 133 determines whether the read data can be saved, and if saved, determines the save format. If saved, the read data saving unit 134 saves the read data in the decided save format. The process control unit 135 cooperates with the above components 131 to 134 to control processing of the read data.
[0032] The document database 14 accumulates document data that the cloud 10 holds and manages. FIG. 3 is a diagram showing an example of the data configuration of document information added to document data handled in the present embodiment. As shown in FIG. 3, the document information includes address information, user-related information, and usage authority information. FIG. 3 also shows a setting example for each data item, specifically, a setting example of document information set for document X. Although various attribute information such as a creation date and a document type is added to the document, FIG. 3 shows only data items for use in explaining the present embodiment. Note that a document can take the form of a printed matter or electronic data (hereinafter referred to as "document data"), and the document information is added to the document data of the document and held and managed in the document database 14. In the present embodiment, for convenience of explanation, "document" and "document data" may be used interchangeably.
[0033] The address information is an example of document specifying information that specifies a document, and specifies the location where the document data is stored in the document database 14. Note that information capable of identifying a document, such as a document ID, may be used as the document specifying information.
[0034] The user-related information includes information about a user related to the document. The user-related information in this embodiment includes a related party, an administrator, and a user. A user related to the document is specified as a related party. For example, if the document is related to a project, the project members are related parties. The related party corresponds to so-called group information. The administrator is set with identification information of the administrator of the document (hereinafter, "administrator ID"). The user is set with identification information of a user who can use the document because he / she is in a position such as the creator or owner of the document (hereinafter, "user ID"). In this embodiment, an example will be described in which only one person from among the related parties is set as a user. FIG. 3 shows an example in which the related party, administrator, and user are set with identification codes "GrpG", "Mng1", and "UserA" as item data, respectively.
[0035] The user authority information contains document usage authority set for a user ("User A" above). In this embodiment, an example is taken of setting usage authority for read authority (Scan), read authority (Read) and write authority (Write), but this is not limiting. Fig. 3 shows an example in which "Yes" is set for items for which the user has authority (Scan, Read) and "No" is set for items for which the user does not have authority (Write).
[0036] Each of the components 11 to 13 in the cloud 10 is realized by the cooperative operation of the computer forming the cloud 10 and a program running on a CPU mounted on the computer. Also, the document database 14 is realized by a HDD, RAM, or the like mounted on the cloud 10.
[0037] The multifunction device 20 has a print processing unit 21, a read processing unit 22, and a read data transmission unit 23. The print processing unit 21 creates a printed matter by executing printing of document data in response to a request from a user. The read processing unit 22 generates read data by reading a printed document (the above-mentioned "printed matter") using a scanner in response to an operation instruction from the user. The read data transmission unit 23 transmits the read data to the cloud 10.
[0038] Each of the components 21 to 23 in the multifunction device 20 is realized by the cooperative operation of a computer built into the multifunction device 20 and a program running on a CPU mounted on the computer. The functions of the multifunction device 20 may be the same as those of the conventional device.
[0039] Further, like the multifunction device 20, the administrator terminal 30 and the user terminal 40 can be realized with the same functions as before, so in FIG. 2, specific components are not shown.
[0040] The information processing system 2 in this embodiment is configured as described above, but is not limited to the above configuration. The cloud 10 may be configured with a single information processing device or multiple information processing devices. Furthermore, the multifunction device 20 that outputs the printed matter and the multifunction device 20 that scans the printed matter may be different devices. Furthermore, the administrator terminal 30 and the user terminal 40 may also be realized by distributing the functions to multiple information processing devices as necessary.
[0041] Furthermore, the programs used in the present embodiment can be provided not only by communication means, but also by being stored in a computer-readable recording medium such as a USB memory. The programs provided from the communication means or recording medium are installed in a computer, and various processes are realized by the computer's CPU sequentially executing the programs.
[0042] Next, the operation of this embodiment will be described.
[0043] As described above, document data is registered and managed in document database 14, and when document management unit 11 stores document data, it creates document information including address information indicating the storage location of the document data and links it to the document data. Next, document management unit 11 sets user-related information and usage authority information in the document information in response to a setting instruction from an administrator, for example. The document information may be stored together with the linked document by being incorporated into header information, or may be stored and managed separately from the document in document database 14 so that the correspondence can be understood.
[0044] When a user logs in from the user terminal 40 or to the multifunction device 20 and requests printing of document data managed by the cloud 10, the print processing unit 21 in the multifunction device 20 obtains the document data from the cloud 10 in response to the request and executes printing. Note that a process may be performed to confirm in advance whether the requesting user has the authority to print the document data.
[0045] In addition, the user may want to have the multifunction device 20 scan a printed matter obtained by printing and store the read data obtained thereby in the cloud 10. The process in the cloud 10 that handles the read data to be stored and transmitted from the multifunction device 20 will be described below with reference to the flowchart shown in FIG.
[0046] Although the above-mentioned process will be described again, the cloud 10 reads out document data to be printed from the document database 14 in response to a transmission request from the multifunction device 20 and transmits it (step S110). At this time, the address information and user-related information included in the document information of the document data to be printed are also transmitted.
[0047] The print processing unit 21 in the multifunction device 20 prints the transmitted document data and outputs a printed matter, and at that time, the address information and user related information are added to the printed matter in an invisible manner. The method of adding the information in an invisible manner may use a conventional technique, for example, embedding the information in the printed matter using a digital watermark technique, or printing it as two-dimensional code data.
[0048] Next, when the user operates the multifunction device 20 to scan the printed matter, the reading processing unit 22 generates read data. Then, the read data transmission unit 23 transmits the read data together with the user ID of the user who has logged in to the multifunction device 20 to the cloud 10 for storage.
[0049] In the cloud 10, the read data receiving unit 12 acquires the read data transmitted from the multifunction device 20 by receiving the read data (step S120). Then, the encryption processing unit 131 encrypts the acquired read data (step S130). However, since the address information and the user related information are used in the process described later, the encryption processing unit 131 needs to extract the address information and the user related information from the read data and convert them into a usable state.
[0050] Next, the document information acquisition unit 132 acquires the document information added to the document data specified by the address information extracted from the read data (step S140). If the document information cannot be acquired (N in step S150), the process control unit 135 assumes that the address information added to the printed matter has been tampered with, and ends the process.
[0051] If the document information can be acquired (Y in step S150), the save determination unit 133 then performs a save determination process to determine whether the read data can be saved (step S160). The save determination process in this embodiment will be described below with reference to the flowchart shown in FIG.
[0052] The save determination unit 133 compares the user-related information extracted from the read data with the user-related information added to the document data specified from the address information extracted from the read data. In particular, the users must match in order to compare the usage authority information in the subsequent stage. Here, if the user-related information does not match (N in step S161), one of the reasons can be assumed to be that the printed document scanned to generate the read data is not a printed matter obtained by printing the document data. In this case, the save determination unit 133 judges that the read data cannot be saved (step S168). That is, the save determination unit 133 does not permit saving of the read data.
[0053] If the user-related information matches (Y in step S161), then the save determination unit 133 checks whether the user who logged in to the multifunction device 20, i.e., the user who scanned the printed document, is a legitimate user set in the user-related information. Specifically, if the user ID of the user who logged in to the multifunction device 20 matches the user ID of the user set in the document data, the logged-in user can be determined to be a legitimate user. If the logged-in user is not a legitimate user (N in step S162), the save determination unit 133 determines that the printed document was scanned by a user other than the legitimate user, and determines that the read data cannot be saved (step S168).
[0054] In the following description, when the term "document data" is used simply, it refers to document data of a document specified by the address information extracted from the read data as described above.
[0055] If the logged-in user is a valid user (Y in step S162), the save determination unit 133 then checks whether the user has the authority to read the document ("Scan" in FIG. 3). If the user who scanned does not have the authority to read (N in step S163), the save determination unit 133 determines that although the read data was actually generated by scanning, it is not possible to scan a printed document, and determines that the read data cannot be saved (step S168). Note that since the read data is encrypted and cannot be used, here it is considered to be equivalent to not being scanned.
[0056] If the user has read authority (Y in step S163), the save determination unit 133 then checks whether the user has read authority ("Read" shown in FIG. 3). If the user who performed the scan does not have read authority (N in step S164), the save determination unit 133 determines that although the received read data has been encrypted, the user does not have the authority to encrypt, and determines that the read data cannot be saved (step S168). Note that since the read data cannot be saved as a result, it is considered to be equivalent to not being encrypted.
[0057] If the user has read authority (Y in step S163), the save determination unit 133 determines the save mode of the read data according to the setting of the write authority ("Write" in FIG. 3). That is, the save determination unit 133 checks whether the user has write authority, but if the user does not have write authority for the document data (N in step S165), the save determination unit 133 determines that the document data cannot be updated with the read data. In this case, although the document data cannot be updated with the read data, the save determination unit 133 determines that the read data can be saved as a save mode of the read data if the read data is a separate document from the document data (step S166).
[0058] On the other hand, if the user has write authority for the document data (Y in step S165), the save determination unit 133 determines that the document data can be updated with the read data. That is, the save determination unit 133 determines that the read data can be saved as the same document as the document data (step S167) as the save format of the read data. Saving as the same document includes saving the document data by overwriting it, or saving it as a new version. In the following explanation, the case of saving by overwriting will be explained as an example.
[0059] Incidentally, an original is basically set to have no write authority so that it cannot be updated. Let us assume that an original printout is written on, for example, illegally altered, and then scanned. The document data identified from the address information extracted from the read data of the original printout is indeed the original document data, but if the write authority of the original is not confirmed, the original document data may be updated by the read data of the original on which writing has been performed. Therefore, in this embodiment, as described above, the presence or absence of write authority is confirmed before the read data is saved, so that it is possible to prevent the original document data set to have no write authority from being overwritten and updated.
[0060] Returning to FIG. 4, if the save determination unit 133 determines that the read data cannot be saved (N in step S170), the process control unit 135 ends the process without saving the read data.
[0061] On the other hand, if it is determined that the read data can be saved (Y in step S170), the encryption processing unit 131 decrypts the read data (step S180). Next, if it is determined that the read data can be saved if it is a separate document from the document data ("separate document" in step S190), the read data saving unit 134 saves the read data as a separate document from the document data (step S200). To do this, the read data saving unit 134 obtains address information indicating the storage location of the read data, creates document information including the address information, and links it to the read data. In this way, the read data can be treated as separate document data.
[0062] On the other hand, if it is determined that the read data can be saved as the same document as the document data ("same document" in step S190), the read data saving unit 134 overwrites the document data with the read data and saves it (step S210). Alternatively, the read data saving unit 134 may save the read data as the latest version of the document data. When saving as the latest version, a different file is created even if it is essentially the same document, so address information is obtained and linked. Also, the read data saving unit 134 or the document management unit 11 sets the document information other than the address information by inheriting it from the document data. Alternatively, it may be configured to have the administrator set it separately.
[0063] As described above, a user with write authority can overwrite and update a document as intended. On the other hand, a user who does not have write authority but wants to save the read data can save the read data without being discarded, although it becomes a separate document from the document data.
[0064] In this embodiment, the read data is automatically saved, but before saving, the user may be asked to confirm the save format and whether or not to save. Also, although this is not a feature of this embodiment and is not included in the process, a process for determining whether the read data and the document data are identical may be included.
[0065] Embodiment 2 Fig. 6 is a block diagram showing an information processing system 2 in this embodiment. The information processing system 2 in this embodiment has a configuration in which an approval request unit 136 and an approval processing unit 31 are added to the configuration in the first embodiment. Fig. 7 is a diagram showing an example of the data configuration of document information added to document data handled in this embodiment. As shown in Fig. 7, the document information includes address information, user-related information, and usage authority information as in the first embodiment, but this embodiment differs from the first embodiment in that the usage authority information further includes proxy operation authority.
[0066] The "proxy operation authority" refers to the authority that indicates whether or not a user other than the user included in the user-related information of the document information can have the logged-in user act on behalf of the user to perform the operation of saving the scanned data when the printed material is scanned by a person other than the user included in the user-related information of the document information, i.e., when the user does not match the logged-in user of the multifunction device 20.
[0067] In the above-mentioned first embodiment, in step S162 shown in Fig. 5, if the logged-in user is not a valid user set in the user-related information, it is determined that the read data cannot be saved. However, in a situation where a valid user is unable to scan a printed document by himself / herself for some reason, it may be inconvenient for the valid user if the read data of the printed document is unconditionally prohibited from being saved.
[0068] Therefore, in this embodiment, a proxy operation authority is provided as one of the usage authority information, and as shown in the example of FIG. 7, if the proxy operation authority is set to "Yes", indicating that the authority is possessed, it is possible to proxy the logged-in user to perform operations for saving read data.
[0069] Although details will be described later, an approval request unit 136 included in the read data processing unit 13 of the cloud 10 makes an approval request to the administrator to obtain approval to have the logged-in user act as a proxy. In addition, an approval processing unit 31 included in the administrator terminal 30 performs approval processing in which the administrator determines whether or not the proxy operation is permitted in response to the approval request from the cloud 10 and returns the determination result. The approval request unit 136 is realized by the cooperative operation of a computer forming the cloud 10 and a program running on a CPU mounted on the computer. In addition, the approval processing unit 31 is realized by the cooperative operation of a computer forming the administrator terminal 30 and a program running on a CPU mounted on the computer.
[0070] Next, in this embodiment, the process in the cloud 10 that handles the scan data to be saved that is sent from the multifunction device 20 will be described. The process in this embodiment may be the same as that in the first embodiment described using the flowchart shown in FIG. 4. In this embodiment, the save determination process in step S160 is different from that in the first embodiment. The save determination process in this embodiment will be described below using the flowchart shown in FIG. 8. Note that the same process steps as those in the first embodiment shown in FIG. 5 are given the same reference numerals, and the description will be omitted as appropriate.
[0071] 8, in the save determination process in this embodiment, steps S251 to S253 are added to the save determination process in the first embodiment. That is, if the logged-in user is not a valid user (N in step S162), it is immediately determined that the read data cannot be saved in the first embodiment, whereas in this embodiment, the presence or absence of proxy operation authority is checked before determining that the read data cannot be saved. If the valid user does not have proxy operation authority (N in step S251), the save determination unit 133 ultimately determines that the read data cannot be saved (step S168) in the same manner as in the first embodiment.
[0072] On the other hand, if the legitimate user has the proxy operation authority (Y in step S251), the approval request unit 136 makes an approval request to the administrator (step S252). In this way, even if the user ID of the operator who operated the multifunction device 20 that generated the read data, i.e., the login user to the multifunction device 20, does not match the user ID of the user set in the document data, if the user's usage authority information set in the document data indicates that the login user has the proxy operation authority, the approval request unit 136 in this embodiment makes an approval request for the proxy operation by the login user to the administrator of the document. Since the administrator uses the administrator terminal 30, when making an approval request using e-mail, for example, the approval request unit 136 refers to the administrator information (not shown), obtains an e-mail address that is the contact address of the administrator, and sends the e-mail. In this way, the approval request unit 136 requests approval for the proxy operation. In order to obtain approval from the administrator, the approval request is made by including at least information that can identify the legitimate user requesting the proxy operation and the login user who will perform the proxy operation, along with the request for approval of the proxy operation.
[0073] When an approval request is sent from the cloud 10, the approval processing unit 31 displays the contents of the e-mail on a display or the like in response to an operation by the administrator. Then, the approval processing unit 31 returns the result of the administrator's decision on whether or not approval is possible.
[0074] In this way, the cloud 10 receives a response to the approval request from the administrator terminal 30. If approval for the proxy operation is obtained from the administrator (Y in step S253), the save determination unit 133 transitions the process to step S253. The processes from step S253 onward may be the same as those in the first embodiment, and therefore will not be described here. On the other hand, if approval for the proxy operation is not obtained from the administrator (N in step S253), the save determination unit 133 ultimately determines that the read data cannot be saved, as in the first embodiment (step S168).
[0075] According to this embodiment, the proxy operation authority is included in the user authority information, and when determining whether the read data can be saved, the proxy operation authority is referred to to allow another user, that is, the logged-in user to the multifunction device 20 in the above description, to save the read data on behalf of the user. This makes it possible to save the read data as the user intends, even if the user is in a situation where he or she is unable to save the read data himself or herself. As is clear from the fact that the save determination process does not include a determination as to whether the user is in a situation where he or she is unable to save the read data, it is possible for the user to have another user save the read data on his or her behalf, even if the user is in a situation where he or she is able to save the read data.
[0076] In the above embodiments, the term "processor" refers to a processor in a broad sense, including general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).
[0077] In addition, the operations of the processor in the above embodiments may be performed not only by one processor, but also by multiple processors located at physically separate locations working together. The order of the operations of the processor is not limited to the order described in the above embodiments, and may be changed as appropriate.
[0078] (Additional Note) (((1))) A processor is provided. The processor, extracting document identification information that identifies the document and user identification information that identifies a user who can use the document, the document identification information being added to the printed document from scanned data of the printed document obtained by printing the document data of the document; extracting user identification information for identifying a user who can use the document and usage authority information for the document granted to the user, the user identification information being set in document data of the document identified by the extracted document identification information; determining how to handle the read data according to the extracted usage authority information; An information processing system comprising: (((2))) The information processing system described in (((1))) is characterized in that, when the user identification information of an operator who caused a reading means to read the printed document and generate the read data matches the user identification information set in the document data of the document identified by the document identification information, the processor determines the form in which the read data is to be saved based on the writing authority of the operator set in the usage authority information. (((3))) The information processing system according to (((2))) is characterized in that, if the operator does not have writing authority, the processor saves the read data as a separate document from the document. (((4))) The information processing system according to ((2))) or ((3))), wherein the processor updates the document data with the read data if the operator has write authority. (((5))) The information processing system described in (((1))) is characterized in that the processor does not allow the reading data to be saved if the user identification information of the operator generating the reading data does not match the user identification information set in the document data of the document identified by the document identification information. (((6))) The processor, Even if the user identification information of the operator does not match the user identification information set in the document data of the document specified by the document specification information, when referring to the usage authority information, if a proxy operation authority is set for a user who can use the document, a request for approval of the proxy operation by the operator is made to an administrator of the document; If approval is obtained from the administrator, storage of the read data is permitted. The information processing system according to (((5))) is characterized in that (((7))) On the computer, A function of extracting document identification information that identifies a document and user identification information that identifies a user who can use the document, which are added to the printed document from scanned data of the printed document obtained by printing the document data of the document; a function of extracting user identification information for identifying a user who can use the document and usage authority information of the document granted to the user, the user identification information being set in document data of the document specified by the extracted document specification information; A function of determining how to handle the read data according to the extracted usage authority information; A program to achieve this.
[0079] According to the invention described in (((1))), the scanned data of the document can be handled as intended by the user, as compared to a case where the user's usage authority for the document is not referred to. According to the invention described in (((2))), the read data can be saved in a format according to the writing authority of the operator. According to the invention described in (((3))), the read data can be treated as a document different from the original document. According to the invention described in (((4))), the read data can be treated as the original document. According to the invention described in (((5))), it is possible to prevent read data generated by an operation by a person who may be a fraudulent person and is not an authorized person from being stored. According to the invention described in (((6))), it is possible to have a person who is not an authorized user act as a proxy to store the read data. According to the invention described in (((7))), the scanned data of the document can be handled as intended by the user, as compared to a case where the user's usage authority for the document is not referred to. [Explanation of symbols]
[0080] 2 information processing system, 4 network, 10 cloud, 11 document management unit, 12 read data receiving unit, 13 read data processing unit, 14 document database (DB), 20 multifunction device, 21 print processing unit, 22 read processing unit, 23 read data transmission unit, 30 administrator terminal, 31 approval processing unit, 40 user terminal, 131 encryption processing unit, 132 document information acquisition unit, 133 storage determination unit, 134 read data storage unit, 135 processing control unit, 136 approval request unit.
Claims
1. A processor is provided. The processor, extracting document identification information that identifies the document and user identification information that identifies a user who can use the document, the document identification information being added to the printed document from scanned data of the printed document obtained by printing the document data of the document; extracting user identification information for identifying a user who can use the document and usage authority information for the document granted to the user, the user identification information being set in document data of the document identified by the extracted document identification information; determining how to handle the read data according to the extracted usage authority information; An information processing system comprising:
2. The information processing system according to claim 1, characterized in that, when the user identification information of an operator who caused the reading means to read the printed document and generate the read data matches the user identification information set in the document data of the document identified by the document identification information, the processor determines the form in which the read data is to be saved based on the writing authority of the operator set in the usage authority information.
3. 3. The information processing system according to claim 2, wherein the processor stores the read data as a separate document from the document when the operator does not have writing authority.
4. 3. The information processing system according to claim 2, wherein the processor updates the document data with the read data if the operator has write authority.
5. The information processing system according to claim 1, characterized in that the processor does not allow the saving of the read data if the user identification information of the operator generating the read data does not match the user identification information set in the document data of the document identified by the document identification information.
6. The processor, Even if the user identification information of the operator does not match the user identification information set in the document data of the document specified by the document specification information, when referring to the usage authority information, if a proxy operation authority is set for a user who can use the document, a request for approval of the proxy operation by the operator is made to an administrator of the document; If approval is obtained from the administrator, storage of the read data is permitted.
6. The information processing system according to claim 5.
7. On the computer, A function of extracting document identification information that identifies a document and user identification information that identifies a user who can use the document, which are added to the printed document from scanned data of the printed document obtained by printing the document data of the document; a function of extracting user identification information for identifying a user who can use the document and usage authority information of the document granted to the user, the user identification information being set in document data of the document specified by the extracted document specification information; A function of determining how to handle the read data according to the extracted usage authority information; A program to achieve this.
Citation Information
Patent Citations
Electronic document management system
JP2008306650A
