JP4101164B2 - DATA DISTRIBUTION DEVICE, DATA DISTRIBUTION METHOD, DATA DISTRIBUTION PROGRAM, AND RECORDING MEDIUM - Google Patents

Description

  The present invention relates to a data distribution apparatus, a data distribution method, a data distribution program, and a recording medium, and more particularly to a data distribution apparatus, a data distribution method, a data distribution program, and a data distribution apparatus that distribute information to a destination specified on a medium read together with a document. The present invention relates to a recording medium.

  2. Description of the Related Art Document distribution systems that distribute electronic data stored in a document database or the like to a mail address designated by a user, a folder on a file system, or another document database have been conventionally used.

  In recent years, multifunctional image forming apparatuses (hereinafter referred to as “fusion machines”) in which the functions of apparatuses such as a printer, a copy machine, a facsimile machine, and a scanner are housed in a single housing have been provided. Cooperation between the machine and the document distribution system is also planned. That is, the information scanned by the multifunction peripheral is transmitted to the distribution server as it is, and transmitted from the distribution server to the destination. According to such a form, a complicated operation of temporarily storing scanned information in a document database and instructing distribution again from a terminal such as a PC (Personal Computer) becomes unnecessary.

  When instructing distribution of scanned information from the multifunction peripheral, the user designates a distribution destination from the destination list displayed on the operation panel of the multifunction peripheral. The destinations displayed in the destination list are those registered in a predetermined database on the network or the database owned by the MFP itself, but all destinations registered in such a database are displayed in the destination list. May not be desirable from the viewpoint of security or the like. This is because it is conceivable that a malicious user distributes information to an unspecified destination, or even a malicious user distributes a confidential document to an incorrect destination due to an operation error.

  Therefore, it is necessary to limit the destinations that can be specified for each user and display only the destinations within the limitation range in the destination list.

  By the way, the operation panel generally has a smaller display area than a display such as a PC, and cannot display a large amount of information at a time. For example, even if the destination list is displayed, the entire list cannot be displayed on one screen, and complicated operations such as scrolling and screen switching are required in order to check a portion that is not displayed. Therefore, a document distribution system is provided in which a destination can be designated by a mark sheet provided with a mark area for each destination.

  That is, the user puts a mark on a destination to be designated as a delivery destination on the mark sheet, and sets the mark sheet on another document to be delivered on the multifunction peripheral. The multi-function apparatus scans originals including mark sheets one by one, and transmits the scanned information to the distribution server as image data. The distribution server determines the destination by performing mark recognition on the image data of the mark sheet by an OMR (Optical Mark Reader) function, and distributes image data other than the mark sheet to the destination.

  As described above, by using the mark sheet, the user can easily specify the destination.

As a related technique, Patent Document 1 discloses an invention of a document management system that transmits a document sent from a terminal by FAX.
JP 2001-86285 A

  However, since the display on the mark sheet is static, there is a problem that it is not possible to limit the destinations that can be specified for each user, unlike the operation panel. Since it is inefficient to prepare a mark sheet that displays different destinations for each user, it is necessary to use a mark sheet that describes all destinations that can be used as delivery destinations so that all users can use them. Because.

  Then, even though the destinations that can be specified on the operation panel are limited, all destinations can be specified on the mark sheet, and the specification of destinations on the mark sheet can be abused as a security hole. Sex is conceivable.

  The present invention has been made in view of the above points, and in the case of specifying a destination on a medium that is read together with a document, a data distribution apparatus, a data distribution method, and a data distribution capable of restricting a destination that can be distributed The purpose is to provide a program and a recording medium.

  Accordingly, in order to solve the above-described problem, the present invention provides a data distribution apparatus for distributing the image data to a predetermined destination in response to a distribution request for the read image data, as described in claim 1, Recognizing the first destination based on the image data, and determining the presence or absence of the user's distribution authority related to the distribution request for the first destination, and the distribution authority by the user by the destination recognition means Distribution means for distributing the image data to a destination determined to have the image data.

  In this way, the data distribution apparatus determines whether the user has the distribution authority for the destination recognized based on the image data, and executes the distribution to the destination having the distribution authority. It is possible to prevent unconditionally delivering to a marked destination.

  In order to solve the above problems, the present invention provides a data distribution method in the data distribution apparatus, a data distribution program for causing the data distribution apparatus to execute the data distribution method, or a recording medium on which the data distribution program is recorded. It is good.

  According to the present invention, it is possible to provide a data distribution device, a data distribution method, a data distribution program, and a recording medium that can restrict a distributable destination when a destination is specified in a medium that is read together with a document.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of a document distribution system according to an embodiment of the present invention. As shown in FIG. 1, the document distribution system 1 according to the present embodiment includes a distribution server 10, a multi-function apparatus 20, a distribution information management server 30, an authentication server 40, a user management server 50, a terminal 60, and the like. Each component is connected via a network such as the Internet or a LAN.

  The distribution server 10 is a computer on which an electronic data distribution function is implemented. In the present embodiment, the distribution server 10 distributes the information read (scanned) by the multifunction machine 20 to a predetermined destination (e-mail address, folder on the file system, document management database, or the like).

  The compound machine 20 is a multifunctional image forming apparatus in which the functions of each device such as a printer, a copy machine, a facsimile machine, and a scanner are housed in a single casing. In this embodiment, the multi-function device 20 requests the distribution server 10 to distribute information read by the scanner function in accordance with an instruction from the user.

  The distribution information management server 30 is information regarding the distribution authority of the user who has instructed distribution, information regarding destinations that can be designated as distribution destinations, etc. (hereinafter referred to as “distribution information” when the information managed by the distribution information management server 30 is generically referred to) It is a computer with the management function of The distribution information management server 30 provides distribution information in response to a request from the distribution server 10. The distribution authority means a distribution authority for each destination of the user. That is, each user is not permitted to distribute information to all destinations, and whether or not distribution is possible for each destination is managed by the distribution information management server 30 as information relating to distribution authority.

  The user management server 50 is a computer on which a user information management function, a user authentication function, and the like are installed. Specifically, in a Windows (registered trademark) environment, a domain controller, an LDAP (Lightweight Directory Access Protocol) server, or the like is applicable.

  The authentication server 40 is a computer on which a function for providing the function in the user management server 50 by a SOAP (Simple Object Access Protocol) interface is implemented. Only the client authenticated through the authentication server 40 can use the functions of the distribution server 10 and the distribution information management server 30.

  The terminal 60 is a PC (Personal Computer) in which a function for the user to confirm whether or not the destination specified in the mark sheet is correctly recognized by the distribution server (or called “destination confirmation function”). And so on. That is, in the present embodiment, the user can designate a destination using a mark sheet (hereinafter referred to as “destination designation sheet”).

  FIG. 2 is a diagram illustrating an example of a destination designation sheet. As shown in FIG. 2, the destination designation sheet 70 is provided with a mark area 71 for each destination. The user can cause the distribution server 10 to recognize the destination by marking the mark area of the destination as the distribution destination and causing the multi-function peripheral 20 to read the destination designation sheet 70 together with the document to be distributed.

  However, generally, when a mark sheet is used, a mark may not be accurately recognized in OMR (Optical Mark Reader) processing. Therefore, the user uses the destination confirmation function of the terminal 60 in order to confirm whether or not the mark recognition for the destination designation sheet 70 is correctly performed.

  FIG. 3 is a diagram showing a functional configuration example of the document distribution system in the embodiment of the present invention. As shown in FIG. 3, the distribution server 10 includes a distribution server unit 11, an input support server unit 12, a destination confirmation spooler 13, a destination confirmation server unit 14, and the like.

  The distribution server means 11 is a program in which a function for distributing information (image data or the like) requested for distribution from the multi-function device 20 to a destination designated by the destination designation sheet 70 or the like is installed.

  The input support server unit 12 is a program in which a function for executing OMR processing on the destination designation sheet 70 and notifying the distribution server unit 11 of the marked destination is installed.

  The destination confirmation spooler 13 is for temporarily storing information such as a destination recognized by the input support server means 12 by the OMR processing. In this embodiment, the destination confirmation spooler 13 uses a folder and a file in the file system. It is configured.

  The destination confirmation server means 14 provides the information stored in the destination confirmation spooler 13 to the destination confirmation client means 61 described later, and changes the delivery destination in response to a delivery destination change request from the destination confirmation client 61. It is a program that implements the function.

  The terminal 60 has destination confirmation client means 61. The destination confirmation client means 61 is a program in which a destination confirmation function is installed.

  The distribution information management server 30 includes a directory service 31 and a distribution information DB (Data Base) 32. The directory service 31 is a program for providing access means for the distribution information DB 32 through a SOAP interface. The distribution information DB 32 is a database in which distribution information is registered.

  The authentication server 40 has an authentication service 41. The authentication service 41 is a program for providing the function in the user management means 51 through the SOAP interface.

  The user management server 50 has user management means 51. The user management means 51 is a program in which a user information management function, a user authentication function, and the like are installed.

  Next, details of the distribution server 10 will be described. FIG. 4 is a diagram illustrating a hardware configuration example of the distribution server according to the embodiment of the present invention. The distribution server 10 of FIG. 4 is configured to include a drive device 100, an auxiliary storage device 102, a memory device 103, an arithmetic processing device 104, and an interface device 105 that are mutually connected by a bus B. The

  A program for realizing processing in the distribution server 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100.

  The auxiliary storage device 102 stores the installed program and also stores necessary files and data.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The arithmetic processing unit 104 executes functions related to the distribution server 10 in accordance with a program stored in the memory device 103. The interface device 105 includes, for example, a modem, a router, etc., and is used for connecting to a network.

  The distribution information management server 30, the authentication server 40, the user management server 50, and the like can also be realized with the same hardware configuration.

  Hereinafter, the processing procedure of the document distribution system 1 in FIG. 3 will be described. FIG. 5 is a sequence diagram for explaining processing relating to a distribution request from the multi-function peripheral to the distribution server. When the user sets the destination designation sheet 70 marked as the delivery destination on the original to be delivered and sets it on the multi-function peripheral 20, the multi-function peripheral 20 reads the destination designation sheet 70 and the original one by one. Start processing. The fusion machine 20 generates a file of image data (image file) for each page based on the read information.

  In step S101, the MFP 20 calls the authentication method of the authentication service 41 using the RPC of the SOAP with the user name and password (authentication information) input by the user via the operation panel as arguments, and thereby sends the authentication service 41 to the authentication service 41. User authentication request.

  In step S102 following step S101, when the authentication service 41 requests the user management unit 51 to authenticate the user with the authentication information, the user management unit 51 authenticates the user based on the authentication information. The result (authentication result) is transmitted to the authentication service 41 (S103).

  Progressing to step S104 following step S103, the authentication service 41 transmits a SOAP message including the authentication result to the multi-function device 20 as return information of the authentication method. When the authentication is successful, the authentication service 41 stores information indicating that the user is an authenticated user (hereinafter referred to as “authenticated user”).

  If the authentication is successful, the multi-function device 20 requests the authentication service 41 to issue an authentication ticket by calling an authentication ticket issuing method of the authentication service 41 based on the successful authentication. Here, the authentication ticket is electronic data for proving that the user has been authenticated, and when using a service provided by the distribution server means 11 in the distribution server 10 or the directory service 31 in the distribution information management server 30. The presentation is required.

  Proceeding to step S106 following step S105, the authentication service 41 confirms whether or not the user is an authenticated user. If the user is confirmed to be an authenticated user, the authentication service 41 generates an authentication ticket. The ticket is transmitted to the fusion machine 20.

  Progressing to step S107 following step S106, the multi-function device 20 transmits a request for providing a list of destinations that can be designated by the user (hereinafter referred to as “destination list”) to the distribution server means 11 with an authentication ticket. To do.

  Progressing to step S108 following step S107, when the distribution server means 11 transmits the destination list to the multi-function device 20, the destination list is displayed on the operation panel of the multi-function device 20. The distribution server means 11 obtains distribution information from the directory service 31 and provides a destination list based on the distribution information when providing the destination list, but this is omitted in the figure for convenience.

  Here, the displayed destination list includes not only individual users but also destinations for a group of a plurality of users, a predetermined folder, a predetermined document management database, and the like. Also, an abstract destination “OMR designation” is included as a destination for designating that the destination is designated by the destination designation sheet 70. Here, since the destination is designated by the destination designation sheet 70, the user selects “OMR designation” from the destination list. Note that a plurality of destinations can be selected simultaneously on the destination list, and “OMR designation” and other destinations can be selected together.

  Proceeding to step S110 following step S109, based on the selection of the destination by the user, the MFP 20 is selected by the image data, bibliographic information (file name, number of files, etc.) of the image data, the authentication ticket, and the user. An image data distribution request is transmitted to the distribution server means 11 with the destination ID of the destination.

  Here, the destination ID is a number uniquely assigned to each destination in order to identify each destination. It should be noted that the destination ID transmitted along with the distribution request is for the destination selected in the destination list. That is, when the destination designation sheet 70 is used, the destination ID corresponding to “OMR designation” is applicable instead of the destination marked on the destination designation sheet 70. In order to avoid confusion between the two, hereinafter, the destination ID designated with the distribution request is referred to as “destination ID-1”. When a plurality of destinations are selected on the destination list, a list of destination ID-1 (destination ID-1 list) is transmitted.

  Next, processing executed by the distribution server unit 11 and the like based on a distribution request from the multifunction machine 20 will be described. FIG. 6 is a sequence diagram for explaining a distribution process for “OMR designation”.

  In step S201, the distribution server means 11 requests the directory service 31 to log in by calling the login method of the directory service 31 using the RPC of SOAP with the authentication ticket as an argument. As will be described later, this is preparation processing for the distribution server means 11 to acquire distribution information from the directory service 31.

  Progressing to step S202 following step S201, the directory service 31 requests the authentication service 41 to confirm the validity of the authentication ticket by calling the ticket confirmation method of the authentication service 41 using the authentication ticket as an argument.

  Progressing to step S203 following step S202, the authentication service 41 confirms the validity of the authentication ticket, and transmits the result (confirmation result) to the directory service 31. Confirmation of the validity of the authentication ticket includes confirmation of whether or not the authentication ticket is indeed issued by the authentication service 41, confirmation of the expiration date of the authentication ticket, and the like.

  If the validity of the authentication ticket is confirmed, the process proceeds to step S204 following step S203, and the directory service 31 calls the user ID acquisition method of the authentication service 41 with the authentication ticket as an argument to the authentication service 41. It inquires about the user ID of the owner of the authentication ticket (that is, the user who instructed the distribution request in the multi-function device 20).

  Progressing to step S205 following step S204, the authentication service 41 inquires of the user management means 51 about the user ID (S205), and transmits the user ID returned from the user management means 51 to the directory service 31 (S206, S207). Note that the directory service 31 holds the received user ID for later processing.

  Proceeding to step S208 following step S207, the directory service 31 transmits to the distribution server means 11 that login is permitted.

  Proceeding to step S209 following step S208, the distribution server means 11 calls the distribution authority confirmation method of the directory service 31 with one destination ID-1 as an argument, so that the user can identify the destination (specified by the destination ID-1) ( Hereinafter, the directory service 31 is inquired as to whether or not the distribution authority for “current destination” is given.

  Proceeding to step S210 following step S209, the directory service 31 acquires the distribution authority for the current destination of the user specified by the user ID held in step S207 from the distribution authority table of the distribution information DB 32 (S211). ).

  FIG. 7 is a diagram illustrating a configuration example of a distribution authority table constituting the distribution information DB. As shown in FIG. 7, the distribution authority table 321 is a table that manages the presence / absence of distribution authority and the presence / absence of confirmation authority for each combination of destination ID and user ID. For example, in FIG. 7, a user with a user ID “1” is permitted to distribute information to destinations with destination IDs “1” and “2”, but the user ID is “2”. It is indicated that the distribution of information is permitted only to a destination whose destination ID is “1”. The confirmation authority will be described later.

  Here, what is confirmed is the destination for destination ID-1, that is, the distribution authority for “OMR designation” in this embodiment (not the distribution authority for each destination marked in destination designation sheet 70). .)

  Proceeding to step S212 following step S211, the directory service 31 transmits information indicating the presence or absence of the distribution authority to the distribution server means 11 as return information of the distribution authority confirmation method.

  If it is confirmed that the user has the distribution authority, the process proceeds to step S213 following step S212, and the distribution server means 11 calls the processing content inquiry method of the directory service 31 with the destination ID-1 as an argument, thereby The service 31 is inquired about the processing contents of the distribution processing for the current destination. Here, the processing content is information indicating what should be specifically executed as the distribution processing.

  Proceeding to step S214 following step S213, the directory service 31 acquires the processing content for the current destination from the destination / processing content correspondence table and the processing content detail table of the distribution information DB 32 (S215).

  FIG. 8 is a diagram illustrating a configuration example of a destination / processing content correspondence table constituting the distribution information DB. As shown in FIG. 8, the destination / processing content correspondence table 322 is a correspondence table between destination IDs and processing IDs. Here, the process ID is information for uniquely identifying each process content.

  FIG. 9 is a diagram illustrating a configuration example of a processing content detail table constituting the distribution information DB. As shown in FIG. 9, the processing content detail table 323 defines the processing content and the destination of the distribution processing for each processing ID.

  Therefore, first, the processing ID for the destination ID-1 is specified based on the destination / destination processing content correspondence table 322, and the processing content is specified based on the processing ID and the processing content detail table 323. .

  Here, it is assumed that the value of the destination ID-1 is “1”. Then, the processing ID “1” is identified from the destination / processing content correspondence table 322, and the processing content with the processing ID “1” is identified as the OMR processing from the processing content detail table 323. Is done. That is, it is specified that the delivery process when the destination is “OMR designation” should execute the OMR process.

  Proceeding to step S216 following step S215, the directory service 31 transmits processing contents indicating that the OMR processing is to be executed to the distribution server means 11 as return information of the processing contents inquiry method.

  Proceeding to step S217 following step S216, the distribution server means 11 executes the processing indicated in the processing content. Here, since it is necessary to execute the OMR process, the distribution server unit 11 performs the OMR process on the input support server unit 12 with the image data, the bibliographic information, the authentication ticket, and the destination ID-1 of the current destination. Request.

  If destinations other than “OMR designation” are designated, the distribution server means 11 repeats the processing from step S209 to S217 for each destination (S218), and then logs off from the directory service 31 ( S219).

  Incidentally, in FIG. 6, when the directory service 31 receives a login request from the distribution server means 11 (S201), the user ID is acquired and held in advance (S204 to S207). Since the ID only needs to be acquired by the timing (S210) for confirming the distribution authority, the user ID acquisition process may be executed at the timing when the distribution authority confirmation method is called from the distribution server means 11. .

  FIG. 10 is a diagram illustrating an example in which the timing for executing the user ID acquisition process is changed. In FIG. 10, the same parts as those in FIG.

  In FIG. 10, the user ID acquisition process (S204 to S207) is executed after the distribution authority confirmation method is called (S209). With such a processing procedure, the processing to be executed in response to the login request (S201) can be simplified. However, when a plurality of destinations are designated, it is necessary to repeat the process of acquiring the same user ID for each destination. Note that the content of the processing in each step is the same as that described with reference to FIG.

  Next, processing by the input support server unit 12 requested to perform OMR processing from the distribution server unit 11 will be described. FIG. 11 is a sequence diagram for explaining processing by the input support server means.

  In step S301, the input support server means 12 performs OMR processing on the image data from which the destination designation sheet 70 has been read, and identifies the destination ID of the marked destination. The destination ID specified here is “destination ID-2”. When a plurality of destinations are marked, a list of destination IDs-2 is specified.

  In step S302 following step S301, the input support server unit 12 requests the directory service 31 to log in by calling the login method of the directory service 31 with the authentication ticket as an argument.

  The login method called here is the same as that called by the distribution server means 11 in step S201 (FIG. 6). Therefore, from step S303 to step S309, as in steps S202 to S208, confirmation of the validity of the authentication ticket and acquisition processing of the user ID are executed by the directory service 31, and the input support server means 12 indicates that login is permitted. (S309).

  In step S310 following step S309, the input support server unit 12 determines the distribution authority method in the same manner as the distribution server unit 11 calls the distribution authority confirmation method of the directory service 31 in step S209 (FIG. 6). call. However, here, the destination ID-2, that is, the destination ID for the destination marked on the destination designation sheet 70 is designated as an argument.

  Proceeding to step S311 following step S310, the directory service 31 acquires the distribution authority of the user for the destination specified by the destination ID-2 (hereinafter referred to as “current destination”) from the distribution authority table 321 (FIG. 7). (S312).

  Progressing to step S313 following step S312, the directory service 31 transmits information indicating the presence / absence of distribution authority to the input support server unit 12.

  Progressing to step S314 following step S313, if the information received from the directory service 31 indicates that the distribution support for the current destination is indicated in the information received from the directory service 31, the input support server means 12 indicates a flag indicating whether distribution is possible for the current destination. Set (Distribution flag) to ON.

  Thereafter, the processing from step S310 to step S314 is executed for all the destinations marked on the destination designation sheet 70 (S315). Therefore, the availability of distribution is specified for each destination, and the availability of distribution is reflected in the distribution availability flag for each destination.

  Subsequent processing branches depending on the setting. That is, when it is set to execute distribution immediately (this case is hereinafter referred to as “immediate distribution mode”), the input support server unit 12 determines whether the image data, the bibliographic information, the authentication ticket, and the distribution availability. The distribution server means 11 is requested to distribute the image data together with a list of destination IDs-2 whose destinations are ON (S316).

  On the other hand, if the setting is made so that the delivery job is spooled in order to confirm the destination by the destination confirmation function (this case is hereinafter referred to as “destination confirmation mode”), the input support server means 12 receives the image data. The bibliographic information, the authentication ticket, and the list of destination IDs-2 whose delivery flag is ON are stored (spooled) in the destination confirmation spooler 13 (S317).

  It should be noted that the list of destination IDs 2 specified in steps S316 and S317 includes only the destination ID-2 whose destination is the distribution availability flag. Therefore, destinations for which the user has no distribution authority are excluded from the distribution destinations at this stage.

  Next, processing executed by the distribution server unit that receives a distribution request from the input support server unit 12 in the case of the immediate distribution mode will be described. FIG. 12 is a sequence diagram for explaining a distribution process for a marked destination.

  The process in FIG. 12 is basically the same as the process (FIG. 6) that is executed when a delivery request is first made for “OMR designation” as the destination.

  That is, when the distribution server means 11 calls the login method of the directory service 31 using the authentication ticket as an argument (S401), the directory service 31 confirms the validity of the authentication ticket and acquires the user ID (S402 to S407). ), To the effect that login is permitted is transmitted to the distribution server means 11 (S408).

  Proceeding to step S409 following step S408, the distribution server means 11 calls the distribution authority confirmation method of the directory service 31 with one destination ID-2 as an argument, whereby the user makes a destination ID- 2 is inquired as to whether or not the user has distribution authority for the destination specified by 2 (hereinafter referred to as “current destination”).

  It should be noted that the destination ID-2 that is crossed here is one that has already been confirmed by the input support server means 12 (see steps S310 to S313 in FIG. 11). Therefore, the confirmation processing of the distribution authority here is confirming in consideration of a time lag from the processing by the input support server means 12.

  Progressing to step S410 following step S409, the directory service 31 acquires the distribution authority from the distribution authority table 321 (S411), and transmits information indicating the presence or absence of the distribution authority to the distribution server means 11 (S412).

  Progressing to step S413 following step S412, the distribution server means 11 calls the processing content inquiry method of the directory service 31 with the destination ID-2 as an argument, whereby the processing content of the distribution processing for the current destination is made to the directory service 31. Inquire.

  Proceeding to step S414 following step S413, the directory service 31 acquires the processing content for the current destination from the destination / processing content correspondence table 322 (FIG. 8) and the processing content detail table 323 (FIG. 9) of the distribution information DB 32 (see FIG. 9). S415).

  Here, it is assumed that the value of the destination ID-2 is “2”. Then, the processing ID is specified as “2” from the destination / processing content correspondence table 322, and further, it is specified from the processing content details table 323 that the processing content should be transmitted to “xxx@yyy.jp” by mail. Is done.

  Proceeding to step S416 following step S415, the directory service 31 transmits the processing content indicating that the mail should be transmitted to the distribution server means 11 as return information of the processing content inquiry method.

  Following step S416, the process proceeds to step S417, and the process indicated in the process content is executed. Here, the distribution server means 11 transmits image data to “xxx@yyy.jp” by mail.

  Thereafter, when the distribution server means 11 executes the processing from step S409 to S417 for all destination IDs-2 (S418), it logs off from the directory service 31 and ends the processing (S419).

  Next, a description will be given of the case of the destination confirmation mode, that is, the case where information about the destination is stored in the destination confirmation spooler 13 in step S317 (FIG. 11). Information is stored in the destination confirmation spooler 13 with the following configuration.

  FIG. 13 is a diagram illustrating a configuration example of a destination confirmation spooler. As shown in FIG. 13, the destination confirmation spooler 13 generates a destination folder 132 (destination folder 132 a and destination folder 132 b) for each destination under the Root folder 131 of the destination confirmation spooler 13. Manage information about each destination. The destination corresponding to the destination folder 132 corresponds to the destination corresponding to the destination ID-1. That is, each time the process of step S317 is executed, one destination folder 132 is generated. Further, the folder name of each destination folder 132 is represented by the respective destination ID.

  Under each destination folder 132, a document folder 133 (a document folder 133a, a document folder 133b, etc.) is further generated for each “document”. The “document” here is not a one-to-one correspondence with the specific existence of a file or the like, but is a concept for information composed of one or more image data and one bibliographic information for them.

  Therefore, one or more image data 134 and bibliographic information 135 constituting the document are stored in the document folder as files. In the bibliographic information 135, for each destination ID that is marked on the destination designation sheet 70 recognized by the OMR process, that is, the destination corresponding to the destination ID-2, the presence / absence of the distribution authority for the destination is indicated. It is included as list information 136.

  Note that the folder name of each document folder 133 is represented by a document ID that uniquely identifies each document.

  Hereinafter, a process for the user to confirm information stored in the destination confirmation spooler 13 using the destination confirmation client means 61 of the terminal 20 will be described. In the following, the act of the user confirming information registered in one destination folder 132 is referred to as “destination confirmation”, and the process related to destination confirmation is referred to as “destination confirmation process”.

  FIG. 14 is a sequence diagram for explaining the destination confirmation processing.

  In step S501, when the user instructs activation of the destination confirmation client unit 61 in order to confirm whether or not the mark recognition on the destination designation sheet 70 is correctly performed, the destination confirmation client unit 61 sets the preset and stored settings. Execute startup processing such as reading information. The setting information includes the server name of the destination confirmation destination (here, the name of the destination confirmation server means 14), the destination ID of the destination to be confirmed (here, the destination ID corresponding to the destination ID-1, that is, “OMR”). Destination address for “designation”), the user name and password of the user, and the like.

  Subsequent to step S501, the destination confirmation client means 61 executes processing for acquiring an authentication ticket as in the case of the multi-function device 20 from steps S101 to S106 in FIG. 5, and acquires an authentication ticket from the authentication service 41. (S502 to S507).

  When the authentication ticket is acquired, the destination confirmation client means 61 requests the login to the destination confirmation server means 14 by calling the login method of the destination confirmation server means 14 with the authentication ticket as an argument (S508).

  Proceeding to step S509 following step S508, the destination confirmation server means 14 calls the login method of the directory service 31. Since the login process for the directory service 31 has already been described, detailed description thereof will be omitted.

  When the login to the directory service 31 is successful (S510), the destination confirmation server means 14 transmits a message indicating that the login is permitted to the destination confirmation client means 61 (S511).

  In step S512 following step S511, the destination confirmation client unit 61 sends a destination to the destination confirmation server unit 14 with the destination ID (destination ID-1) set as the confirmation target. An inquiry is made as to whether or not the user has the confirmation authority for the destination specified by ID-1 (hereinafter referred to as “current destination”). Here, “confirmation authority” refers to authority for confirming the destination. In other words, the user cannot confirm the destination for the destination without confirmation authority.

  Progressing to step S513 following step S512, the destination confirmation server means 14 inquires of the directory service 31 about the confirmation authority for the current destination by calling the confirmation authority confirmation method of the directory service 31 with the destination ID-1 as an argument. Then, the directory service 31 transmits information indicating the presence / absence of the confirmation authority to the destination confirmation server means 14 (S514).

  As shown in FIG. 7, the distribution authority table 321 manages whether or not there is a confirmation authority as well as the distribution authority. Therefore, the directory service 31 acquires confirmation authority for the destination specified by the user's destination ID-1 from the distribution authority table 321. In the distribution authority table 321 according to the present embodiment, the distribution authority and the confirmation authority are separately managed, but it is not meaningful to make a difference between the distributable destination and the confirmable destination. May manage only the distribution authority, and determine the confirmation authority based on the distribution authority.

  Proceeding to step S515 following step S514, the destination confirmation server means 14 transmits information indicating the presence / absence of confirmation authority to the destination confirmation client means 61.

  If the user has the confirmation authority, the process proceeds to step S516 following step S515, and the destination confirmation client unit 61 calls the confirmation waiting document acquisition method of the destination confirmation server unit 14 using the destination ID-1 as an argument, thereby confirming the destination confirmation server unit. 14 is inquired about a list of document IDs of documents registered in the current destination (hereinafter referred to as “awaiting confirmation document”).

  Progressing to step S517 following step S516, the destination confirmation server means 14 refers to the destination confirmation spooler 13 to obtain a list of document IDs (document ID list) of documents waiting for confirmation (S518). Specifically, the destination confirmation server means 14 specifies the destination folder 132 corresponding to the current destination based on the destination ID-1, and obtains a list of folder names of the document folder 133 immediately below the destination folder 132. .

  Progressing to step S519 following step S518, the destination confirmation server means 14 transmits a document ID list to the destination client means 61.

  Proceeding to step S520 following step S519, the destination confirmation client means 61 calls the destination list acquisition method of the destination confirmation server means 14 with one document ID included in the document ID list as an argument, so that the destination confirmation server For the means 14, a list of destination IDs-2 (that is, a list of destinations marked on the destination designation sheet 70) designated in the document specified by the document ID (hereinafter referred to as "current document"). Inquire.

  Proceeding to step S521 following step S520, the destination confirmation server means 14 refers to the destination confirmation spooler 13 to acquire destination list information 136 (S522) of the current document. Specifically, the destination confirmation server means 14 specifies the document folder 133 corresponding to the current document based on the document ID, and acquires the destination list information 136 stored in the document folder 133.

  Proceeding to step S 523 following step S 522, the destination confirmation server means 14 transmits the destination list information 136 to the destination confirmation client means 61.

  Note that the processing from step S520 to S523 is executed for all document IDs included in the document ID list (S524). Accordingly, the destination confirmation client means 61 acquires the destination list information 136 for each document registered as the current destination.

  In step S525, the destination confirmation client unit 61 displays a destination confirmation screen based on the destination list information 136 and the like.

  FIG. 15 is a diagram illustrating a display example of the destination confirmation screen. As illustrated in FIG. 15, the destination confirmation screen 62 includes a designated destination list display area 621, a destination designation sheet display area 622, operation target document change buttons 623 and 624, a document deletion button 625, a distribution button 626, and a destination addition button 627. And a destination deletion button 628 and the like.

  The designated destination list display area 621 is a list of destinations based on the destination list information 136 acquired in step S523, that is, destinations that are marked on the destination designation sheet 70 and recognized as being marked in the OMR processing. Is a region in which a list (hereinafter referred to as “designated destination list”) is displayed. In the designated destination list display area 621, for each destination, a destination ID, a comment, and whether delivery is possible (distribution availability) are displayed. The distribution availability is an item indicating whether or not there is a distribution authority for the destination, and is displayed based on information indicating whether or not distribution is included in the destination list information 136.

  By referring to the designated destination list display area 621, the user can mark a destination that has been marked but is not recognized in the OMR process, a destination to which the user does not have distribution authority, or a destination that has not been marked. It is possible to confirm a destination or the like recognized as marked by, for example.

  The destination designation sheet display area 622 is an area where the image data of the destination designation sheet 70 is displayed as it is. The user can confirm the destination marked by referring to the destination designation sheet display area 622.

  The operation target document change buttons 623 and 624 are buttons for changing a document to be operated on the destination confirmation screen 62. That is, when the operation target document change button 623 is selected, the previous document is set as the operation target, and the next document for which the operation target document change button 624 is selected is set as the operation target.

  The document deletion button 625 is a button for removing a document that is an operation target from a distribution target. The distribution button 626 is a button for instructing execution of distribution.

  The add destination button 627 is a button for adding a destination to the designated destination list. That is, when the add destination button 627 is selected, a dialog for selecting a destination is displayed, and the destination selected on the dialog is added to the designated destination list. Therefore, the user can use the add destination button 627 to add a destination or the like that was marked but not recognized in the OMR process.

  The destination deletion button 628 is a button for deleting the destination selected in the designated destination list display area 621 from the designated destination list. Therefore, the user can use the delete destination button 628 to delete a destination that has been marked by dust or the like even though it has not been marked.

  Progressing to step S526 following step S525, the user confirms the destination on the destination confirmation screen 62, and changes the destination by adding or deleting the destination.

  When the user clicks the distribution button 626, the process proceeds to step S 527, where the destination confirmation client unit 61 calls the distribution request method of the destination confirmation server unit 14 using the list of destination IDs of destinations specified on the destination confirmation screen 62 as an argument. Thus, the destination confirmation server means 14 is requested to execute distribution. Here, the destination ID designated as an argument is assumed to be destination ID-3.

  Progressing to step S528 following step S527, the destination confirmation server unit 14 provides a list of image data, bibliographic information, authentication ticket, and destination ID-3 acquired from the destination confirmation spooler 13 to the input support server unit 12. When requesting execution of distribution, the input server means 13 requests the distribution server means 11 to execute distribution (S529).

  Thereafter, as described with reference to FIG. 12, the distribution of the image data is executed to the destination specified by the destination ID-3.

  As described above, according to the distribution server 10 in the present embodiment, the input support server means 12 confirms the user's distribution authority for each destination recognized by executing the OMR process, and sets the destination with the distribution authority. Since the distribution is executed only for the destination, it is possible to prevent inconvenience due to the unconditional distribution to the destination marked on the destination designation sheet 70.

  In addition, the distribution server 10 can store information about the recognized destination in the destination confirmation spooler 13 and can provide the information to the terminal 60, and can also request the terminal 60 from the request. The destination can be changed according to the situation. Therefore, the user can confirm whether or not the designation on the destination designation sheet 70 is correctly recognized via the network. If the designation is not correctly recognized, the user changes the destination so as to be delivered to the originally scheduled destination. can do. As a result, it is possible to prevent the occurrence of a situation in which the intention of delivering to a certain destination has not been delivered.

  Further, since the information regarding the recognized destination includes information indicating the presence / absence of the distribution authority for each destination (distribution availability), the user can distribute to each destination designated on the destination designation sheet 70 in the terminal 60. You can check the authority. As a result, the user can confirm that a destination without distribution authority has been designated on the destination designation sheet 70, and take measures such that information is transmitted to the destination by another means. You can also.

  In the present embodiment, the example in which the multifunction machine 20 and the distribution server 10 are configured by separate hardware has been shown. However, by installing the function of the distribution server 10 in the multifunction machine 20, These functions may be realized by a single device.

  Further, the function for managing the distribution information DB 32 is not necessarily realized in an apparatus (distribution information management server 30) connected to the distribution server 10 via the network, and the distribution information DB 32 is arranged in the distribution server 10. You may make it do. However, when a plurality of distribution servers 10 are arranged on the network for the purpose of distributing the load of the distribution servers 10, the distribution information DB 32 is arranged on one computer rather than arranged on each distribution server 10. Can be managed more efficiently.

  In this embodiment, a mark sheet is described as a specific example of a medium that is read together with a document. However, the medium is not limited to a mark sheet. For example, if an OCR (Optical Character Recognition) function is implemented in the input support server means 12 in place of the OMR function, distribution can be realized to a destination described in characters on a document. Obviously, the invention is applicable.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

It is a figure which shows the structural example of the document delivery system in embodiment of this invention. It is a figure which shows the example of a destination designation | designated sheet. It is a figure which shows the function structural example of the document delivery system in embodiment of this invention. It is a figure which shows the hardware structural example of the delivery server in embodiment of this invention. It is a sequence diagram for demonstrating the process which concerns on the delivery request | requirement from a multifunction peripheral to a delivery server. FIG. 10 is a sequence diagram for explaining a distribution process for “OMR designation”. It is a figure which shows the structural example of the distribution authority table which comprises distribution information DB. It is a figure which shows the structural example of the address | destination and process content corresponding | compatible table which comprises distribution information DB. It is a figure which shows the structural example of the processing content detailed table which comprises distribution information DB. It is a figure which shows the example which changed the timing which performs the acquisition process of user ID. It is a sequence diagram for demonstrating the process by an input assistance server means. It is a sequence diagram for demonstrating the delivery process with respect to the marked destination. It is a figure which shows the structural example of a destination confirmation spooler. It is a sequence diagram for demonstrating a destination confirmation process. It is a figure which shows the example of a display of a destination confirmation screen.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Document distribution system 10 Distribution server 11 Distribution server means 12 Input support server means 13 Destination confirmation spooler 14 Destination confirmation server means 20 Multifunction machine 30 Distribution information management server 31 Directory service 32 Distribution information DB
40 Authentication Server 41 Authentication Service 50 User Management Server 51 User Management Unit 60 Terminal 61 Destination Confirmation Client Unit 100 Drive Device 101 Recording Medium 102 Auxiliary Storage Device 103 Memory Device 104 Arithmetic Processing Device 105 Interface Device B Bus

Claims (17)

A data distribution device for distributing the image data to a predetermined destination in response to a distribution request for the read image data,
Destination recognition means for recognizing a first destination based on the image data and determining whether or not the user has authority to distribute the distribution request for the first destination;
Possess and distribution unit for distributing the image data to destination determining that the user has the authority of delivery by the destination recognizing section,
The distribution unit determines a process to be executed for the second destination specified in the distribution request based on a processing information management unit that manages information on a process to be executed for the destination for each destination. And instructing the destination recognition unit to recognize the first destination based on the determination result . The image data includes image data obtained by reading a medium for designating the first destination,
2. The data distribution apparatus according to claim 1, wherein the destination recognition unit recognizes the first destination marked on the medium by performing OMR processing on the image data read from the medium. . 2. The destination recognizing unit determines whether or not a user has a distribution authority based on the distribution request based on a distribution authority management unit that manages the distribution authority for each destination for each user. Or the data delivery apparatus of 2. The distribution authority management means has an information management apparatus connected via a network,
4. The data distribution apparatus according to claim 3, wherein the destination recognizing unit inquires of the information management apparatus whether or not the distribution authority of the user related to the distribution request exists. The delivering device according to claim 1 to 4 any one characterized by determining based on the processing to be performed on recognized the first destination by the destination recognizing means to said processing information management unit The data distribution apparatus described. The processing information management means has an information management apparatus connected via a network,
The distribution means, the data distribution apparatus of claims 1 to 5 any one claim, characterized in that query the processing to be performed on the destination to the information management apparatus. The destination recognizing means stores distribution availability information indicating whether distribution is possible for each first destination recognized based on the image data,
The distribution availability information providing means for transmitting the delivery availability information stored by the destination recognition means to the client device in response to a request from a client device connected via a network. The data distribution apparatus as described in any one of thru | or 6 . The distribution availability information providing means requests the distribution means to distribute the image data to the third destination in response to a distribution request to the third destination transmitted from the client device based on the distribution availability information. 8. The data distribution apparatus according to claim 7, wherein The data according to any one of claims 1 to 8 , wherein the distribution request is transmitted from a reading device connected via a network and requests distribution of image data read by the reading device. Distribution device. A data distribution method in a data distribution apparatus that distributes the image data to a predetermined destination in response to a distribution request for read image data,
A destination recognition procedure for recognizing a first destination based on the image data;
A distribution authority determination procedure for determining whether a user has authority to distribute the distribution request for the first destination recognized in the destination recognition procedure;
A first distribution procedure for distributing the image data to a destination determined that the user is authorized to distribute in the distribution authority determination procedure ;
First process determination for determining a process to be executed for the second destination specified in the distribution request based on process information management information indicating information on a process to be executed for the destination for each destination Procedures
The data distribution method , wherein the destination recognition procedure is executed based on a determination result in the first process determination procedure . The image data includes image data obtained by reading a medium for designating the first destination,
11. The data distribution method according to claim 10 , wherein the destination recognition procedure recognizes the first destination marked on the medium by executing an OMR process on the image data read from the medium. . The distribution authority determination procedure, according to claim 10, characterized in that to determine whether the rights of distribution of users according to the distribution request based on the distribution rights management information indicating the presence or absence of the permission of delivery to each destination of each user Or the data delivery method of 11 . 13. The method according to claim 12 , further comprising a second process determination procedure for determining a process to be executed for the first destination recognized in the destination recognition procedure based on the process information management information. Data delivery method. Based on the determination result in the distribution authority determination procedure, a distribution permission / inhibition information storage procedure for storing distribution permission / inhibition information indicating whether distribution is possible for each of the first destinations recognized in the destination recognition procedure;
A distribution availability information providing procedure for transmitting the distribution availability information stored in the delivery availability information storage procedure to the client device in response to a request from a client device connected via a network; The data distribution method according to any one of claims 10 to 13 . In response to a distribution request for the third destination transmitted from the client device based on the distribution permission information transmitted to the client device in the distribution availability information providing procedure, the image data is sent to the third destination. 15. The data distribution method according to claim 14 , further comprising a second distribution request procedure for distributing the data. A data distribution apparatus that distributes the image data to a predetermined destination in response to a distribution request for the read image data.
A destination recognition procedure for recognizing a first destination based on the image data;
A distribution authority determination procedure for determining whether a user has authority to distribute the distribution request for the first destination recognized in the destination recognition procedure;
A first distribution procedure for distributing the image data to a destination determined that the user is authorized to distribute in the distribution authority determination procedure ;
First process determination for determining a process to be executed for the second destination specified in the distribution request based on process information management information indicating information on a process to be executed for the destination for each destination Steps and
The data distribution program , wherein the destination recognition procedure is executed based on a determination result in the first process determination procedure . The computer-readable recording medium which recorded the data delivery program of Claim 16 .

Images