JP4992731B2 - Document management apparatus, document management system, and program - Google Patents

Description

  The present invention relates to a document management apparatus, a document management system, and a program.

  In a system for managing electronic documents, a generated electronic document may be stored in a predetermined server, or may be attached to an e-mail and transmitted to a predetermined destination. For example, there is a system that transfers an electronic document generated by reading a paper document with a scanner to an apparatus such as a server or a terminal connected to the scanner over a network. In such a system, as a conventional technique for automatically determining a transfer destination of an electronic document generated by scanning a paper document, for example, the techniques disclosed in Patent Documents 1-3 below are proposed.

  Patent Document 1 discloses a scanner that determines a transfer destination of scanned and read image data by referring to an address database that stores a transfer destination address for each document type. The scanner described in Patent Literature 1 extracts document type information from a scanned and read image, reads a transfer destination address associated with the document type represented by the extracted document type information from the address database, and reads the read transfer destination. The scanned image data is transferred to the address.

  Japanese Patent Application Laid-Open No. 2004-228561 performs character recognition processing on image data obtained by scanning a document, and stores the image data in a storage area of a storage device corresponding to a character string obtained as a result of character recognition processing. Is disclosed.

  In the document scanning system described in Patent Document 3, user identification information is input at the time of a scanning operation by a user, and electronic information generated by scanning reading using storage location access information previously associated with the user identification information. The document is stored in the storage location for the user.

JP 2001-45197 A JP-A-2005-234708 JP 2006-135671 A

  For example, in a system that transfers an operation result document to a transfer destination set in advance for each type of document to be operated and each user who performs the operation, an explicit transfer destination address for each of the document type or the user, etc. Must be set in advance. Therefore, for example, when the number of users who use the system increases or decreases, or when the types of documents are added or reduced, processing for updating the setting information of the corresponding transfer destination address is required, which is troublesome.

  An object of the present invention is to provide a technique that can more easily determine a transfer destination of a document of an operation result.

  The invention according to claim 1 is a registration unit that receives history information including the second document generated as a result of the operation on the first document and the type of the operation from the information processing apparatus and registers the history information in the storage unit. The registration unit further registers in the storage unit a derivation relationship indicating that the parent of the second document is the first document, and the registration unit stores the history information including a predetermined operation type. When received from the information processing apparatus, the transfer destination to which at least a part of the received history information is transferred is determined using the received history information and at least a part of the history information group stored in the storage unit. And the history information may further include transfer information that is information used for determining the transfer destination and includes information indicating a device designated as the transfer destination device. The decision Is the transfer history among the history information group corresponding to the document group corresponding to the ancestor of the document in the received history information in the tree structure represented by the received history information and the derivation relation group stored in the storage unit. When there is history information including information, the document management apparatus determines the transfer destination based on the transfer information included in any of the history information.

  According to a second aspect of the present invention, in the first aspect of the invention, the determination unit is a document included in a path traced back through the tree structure starting from the document in the received history information, and the corresponding history The transfer destination is determined based on the transfer information in the history information corresponding to the document in the received history information and the closest document on the path among the documents whose information includes the transfer information.

  The invention according to claim 3 is the invention according to claim 1, wherein the transfer information further includes information designating a type of operation to be included in the history information to be processed by the determination unit. Documents included in the received history information among the documents included on the path going back through the tree structure starting from the document in the received history information and including the transfer information in the corresponding history information And transfer of the received history information when the type of operation specified in the transfer information in the history information corresponding to the closest document on the path includes the type of operation in the received history information. Determine the destination.

  The invention according to claim 4 is the invention according to claim 1, wherein the transfer information further includes information specifying a type of operation to be included in the history information to be processed by the determination unit, and the determination unit includes: In the history information group corresponding to a document group corresponding to an ancestor of the document in the received history information in the received history information and the tree structure, there is history information including the transfer information. If the type of operation specified in the transfer information included in any of the history information includes the type of operation in the received history information, the transfer destination is determined for the received history information.

  The invention according to claim 5 is the invention according to claim 3 or 4, wherein the transfer information includes the type of operation that should be included in the history information to be processed by the determination unit, and the history information including the type of operation. And a rule used when determining the transfer destination with respect to the transfer information, and the determination unit associates the rule associated with the type of operation in the received history information in the transfer information To determine the transfer destination.

  The invention according to claim 6 is the invention according to claim 1 or 2, wherein the transfer information further includes information for determining a plurality of different transfer destinations for one history information, A plurality of different transfer destinations are determined for the received history information, and at least a part of the received history information is transferred to each of the plurality of different transfer destinations determined by the determination unit.

  The invention according to claim 7 is a step of receiving history information including the second document generated as a result of the operation on the first document and the type of the operation from the information processing apparatus and registering the history information in the storage unit. A registration step for further registering in the storage unit a derivation relationship indicating that the parent of the second document is the first document, and the history information including a predetermined operation type in the registration step. A decision to determine a transfer destination for transferring at least a part of the received history information using the received history information and at least a part of the history information group stored in the storage unit when received from the processing device; And the history information is information for transfer used to determine the transfer destination device, and represents the device designated as the transfer destination device. Transfer information may be included, and in the determination step, the received history information and a tree structure represented by the derivation relation group stored in the storage unit correspond to an ancestor of the document in the received history information. Determining the transfer destination based on the transfer information included in any of the history information when there is history information including the transfer information in the history information group corresponding to the document group; It is a featured program.

  The invention according to claim 8 includes an information processing device and a document management device, and the information processing device includes a second document generated as a result of an operation on the first document, and the type of the operation. A transmission unit for transmitting history information to the document management apparatus; and transfer information for determining a transfer destination for transferring information related to the second document from the document management apparatus. A receiving unit that receives a setting of transfer information including information representing a device designated as a device, and the transmission unit receives the transfer information received when the receiving unit receives the setting of the transfer information. The history information further including information is transmitted to the document management device, and the document management device is a registration unit that receives the history information from the information processing device and registers the history information in a storage unit. The document parent is A registration unit for further registering a derivation relationship indicating that the document is one document in the storage unit, and the history information including a predetermined operation type received from the information processing apparatus by the registration unit. A determination unit that determines a transfer destination to which at least a part of the received history information is transferred using at least a part of the history information and the history information group stored in the storage unit, the received history information and There is history information including the transfer information among history information groups corresponding to document groups corresponding to ancestors of documents in the received history information in the tree structure represented by the derivation relationship group stored in the storage unit. A determination unit that determines the transfer destination based on the transfer information included in any of the history information.

  According to the first, seventh, or eighth aspect of the invention, the operation result document is obtained by using the information acquired by tracing the derivation relationship between the documents without setting the transfer destination address for each operated document. Can determine the forwarding destination.

  According to the second aspect of the present invention, the operation result document is a derivation source document, which is a derivation relationship among documents associated with transfer information including information of a device designated as a transfer destination device. The transfer destination can be determined using the transfer information of the closest document in the tree structure.

  According to the third aspect of the invention, information specifying the type of operation to be executed for transfer processing can be set in association with the document, and the operation result document is designated as a derivation source document and a transfer destination device. Transfer processing in the case where the document is generated as a result of the type of operation specified by the setting associated with the closest document in the tree structure of the derivation relationship among the documents associated with the transfer information including the information of the specified device. Can be executed.

  According to the invention of claim 4, information specifying the type of operation for which transfer processing should be executed can be set in association with a document, and the type specified by this setting is selected from the document and a document derived from the document. A transfer process can be executed for a document generated as a result of the operation.

  According to the fifth aspect of the present invention, the transfer destination of the operation result document can be determined according to different rules according to the type of operation.

  According to the invention of claim 6, transfer processing to a plurality of different transfer destinations can be executed for a document generated as a result of one operation.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram showing a schematic configuration of a document management system. This system includes document management servers 10-1 and 10-2 (hereinafter collectively referred to as document management server 10) and client terminals 20-1 and 20 connected via a network 30 such as the Internet or a local area network. ... (Hereinafter collectively referred to as client terminal 20).

  The client terminal 20 will be described with reference to FIG. A client terminal is a terminal used by a user to operate a document, such as a personal computer or a digital copying machine. As illustrated in FIG. 2, the client terminal 20 includes a document operation unit 200, a registration processing unit 210, and a transfer information setting unit 220.

  The document operation unit 200 is means for executing an operation on a document. Examples of operations on a document include document display (“browsing” from the user's point of view), editing, printout, reading of a paper document, copying of a paper document, and the like. Although only one document operation unit 200 is shown in FIG. 2, each operation may be performed by a separate operation unit (for example, an editing application, a reading control application, or the like). For example, if the document operation unit 200 is software for creating and editing an electronic document such as a word processor, the document operation unit 200 displays the electronic document according to a user instruction or edits the electronic document. Or When an operation is performed on a document, the document operation unit 200 outputs an ID-added document 300 that represents the result of the operation.

  The ID-added document 300 is an electronic document including meta information 310 and document content 320 as shown in FIG. The document content 320 is document content data generated as a result of the operation of the document operation unit 200. If the document operation unit 200 is software for creating and editing an electronic document, the document content 320 is a document file generated as a result of editing by the software. If the document operation unit 200 is an apparatus that prints an electronic document, the document content 320 may be content data of the electronic document to be printed, for example. If the document operation unit 200 is a device that scans a paper document or a device that copies a paper document, the document content 320 may be, for example, image data obtained by reading the paper document.

  The meta information 310 is information for document management, and includes a management ID 312, a parent ID 314, and log information 316.

  The management ID 312 is unique identification information of the ID-added document 300 itself. The parent ID 314 is a management ID of the parent ID-added document of the ID-added document 300. That is, in this embodiment, a document with an ID and a new document with an ID obtained as a result of an operation performed on the document with the ID are handled as a relationship between a parent and a child. When the second ID-added document is obtained by operating the first ID-added document, the first ID-added document is the parent of the second ID-added document, and the second ID-added document is the first ID-added document. It is a child of an ID-added document. Therefore, for example, when a document with the management ID “A” is operated by the document operation unit 200 and the management ID of the new ID-added document obtained as a result is “B”, the latter meta information 310 The management ID 312 is “B”, and the parent ID 314 is “A”. Such a parent-child relationship is hereinafter referred to as a “(management ID) derivation relationship”.

  When an operation for newly registering an electronic document not registered in this system is performed, or when an operation for scanning or copying an unregistered paper document is performed (in this case, the image read from the paper document is used as the document content). In the ID-added document 300 that is generated), the parent ID 314 is empty (that is, the parent does not exist).

  The log information 316 is information of various log items regarding the operation when the ID-added document is generated. The log items include, for example, the date and time when the operation was performed, the type of the operation, and the user (operator) who instructed the operation, but are not limited thereto. The operation types include, for example, registration (registering a new document in this system), browsing, editing, updating (registering an updated version), printing, scanning, copying of a paper document, and the like. For example, when the user edits the first ID-added document using the document operation unit 200 and gives an instruction to complete editing, the log information 316 of the second ID-added document generated as a result is as follows. The date and time of editing completion, the identification information of the user who instructed the editing, and “edit” as the type of operation are included.

  Here, the type of operation incorporated in the log information 316 is a type according to the classification for the purpose of log recording, and may not be the type of operation executed by the document operation unit 200 itself. For example, a plurality of types of operations executed by the document operation unit 200 may be associated with the same single log recording purpose operation type. For example, even when editing an electronic document with an ID on a document editing application and instructing “Register as update” on the operation menu, a paper document with a management ID is read by the scanner on the operation menu of the reading control application. Even when “Register the read document as an approved version” is instructed, the value of the operation type incorporated in the log information 316 is “update”.

  The document operation unit 200 may encrypt the operated document. This encryption can be decrypted by the document operation unit 200 compliant with the present system. In this case, the document content 320 of the ID-added document 300 output from the document operation unit 200 is encrypted, and can be decrypted only by the document operation unit 200 conforming to the present system. Therefore, since the document operation unit 200 is used when the ID-added document 300 is operated, the document operation unit 200 detects the operation, and the content of the operation is notified from the document operation unit 200 to the document management server 10. The Note that encryption may be applied not only to the document content 320 but also to meta information 310 (or a part thereof) described later.

  Returning to the description of FIG. 2, the document operation unit 200 includes an ID assignment unit 202 and a derivation relationship incorporation unit 204 in order to create the ID-added document 300 as described above as an operation result. The ID assigning unit 202 is a unit that assigns a unique management ID to the operation result ID-added document 300. The management ID needs to be identification information unique at least in the present system. For example, the hash value of the ID-added document 300 (excluding the management ID 312) generated as a result of the operation may be obtained, and this hash value may be used as the ID-added document of the document 300. As the hash function, a cryptographic hash function having collision resistance such as SHA-256 (SHA-256 is a cryptographic hash function having a 256-bit hash value defined by NIST in FIPS180-2) is used. For example, it is possible to generate a management ID having sufficient uniqueness for practical use. Of course, the method for generating a unique management ID in the system at each client terminal 20 is not limited to this. If the management ID includes identification information unique to the client terminal 20, a management ID unique in the system can be generated at each client terminal 20.

  The derivation relationship incorporating unit 204 includes a new management ID 312 assigned by the ID assigning unit 202 to the operation result document, and a parent ID 314 that is the management ID of the parent document that is the source of the operation (in the case of new registration, And meta information 310 including log information 316 regarding the operation. Here, the derivation relationship incorporating unit 204 holds correspondence information indicating which of the operation types for log recording purposes each operation type executed by the document operation unit 200 corresponds to. By using this information, the value of the operation type incorporated in the log information 316 is obtained. Then, the derivation relationship incorporating unit 204 generates and outputs the post-operation ID-added document 300 by adding the meta information 310 to the operation result document content.

  When the document operation unit 200 is application software, the ID assignment unit 202 and the derivation relationship incorporation unit 204 may be realized as a so-called plug-in program added to the software. .

  The registration processing unit 210 executes processing for registering the ID-added document 300 output from the document operation unit 200 in the document management server 10. In this way, each client terminal 20 registers the ID-added document 300 that is the result of the operation performed by itself, in the document management server 10, so that the document management server 10 grasps the derivation relationship between the ID-added documents 300. Can do.

  In the present embodiment, when the client terminal 20 registers the ID-added document 300 in the document management server 10, the document management server 10 may perform a process of transferring the ID-added document 300 to another apparatus. For example, the document management server 10 may transfer the ID-added document 300 registered by the client terminal 20 to another document management server 10 connected via the network 30.

  The transfer information setting unit 220 executes processing related to setting of transfer information used for determining a transfer destination of the ID-added document 300 from the document management server 10. The transfer information includes information indicating a transfer destination candidate device, such as an address of another device connected to the document management server 10 (for example, URL (Uniform Resource Locator)). A specific example of the content of the transfer information will be described later. When the document operation unit 200 executes an operation on a document, the transfer information setting unit 220 accepts input of transfer information by the user for the ID-added document 300 as a result of the operation. For example, when the document operation unit 200 performs an operation on a document, the transfer information setting unit 220 displays information that prompts the user to set transfer information on a display device (not shown), thereby transferring the transfer information. Accepts input. The transfer information setting unit 220 passes the received transfer information to the document operation unit 200. The derivation relationship incorporation unit 204 of the document operation unit 200 incorporates the transfer information received from the transfer information setting unit 220 into the log information 316 of the ID-added document 300 as the operation result.

  When the transfer information setting unit 220 displays information prompting the user to input transfer information on the display device, when the user instructs not to set the transfer information, the transfer information setting unit 220 220 notifies the document operation unit 200 to that effect. Upon receiving this notification, the derivation relationship incorporation unit 204 of the document operation unit 200 does not incorporate the transfer information into the log information 316 of the ID-added document 300. In this case, the log information 316 includes log items (such as the operation type, the operator, and the operation date / time exemplified above) other than the transfer information.

  The transfer information incorporated in the log information 316 of the ID-added document 300 is used to determine the transfer destination for the ID-added document 300 or the ID-added document 300 derived from the ID-added document 300 in the document management server 10. Used.

  The transfer information setting unit 220 may execute the above-described transfer information setting process only when a specific type of operation is executed in the document operation unit 200. For example, the transfer information setting unit 220 performs the transfer information setting process when the “(new) registration” operation or the “update (update version registration)” operation is executed in the document operation unit 200. When a type operation (browsing, editing, printing, etc.) is executed, the transfer information setting process may not be performed. If the transfer information setting unit 220 does not perform transfer information setting processing even when an operation is performed on the document in the document operation unit 200, the log information 316 of the ID-added document 300 output by the document operation unit 200 as a result of the operation is displayed. , Transfer information is not included.

  The ID-added document 300 output as a result of the operation by the document operation unit 200 may be electronically copied or transmitted to another person by a method such as attaching to an e-mail, like a normal document file. it can. The e-mail transmission software is not compliant with this system in this example, so this transmission operation is not reflected in the ID-added document, and is therefore not recorded in the document management server 10. When a person who has received an ID-added document 300 from another person operates the ID-added document 300 using the document operation unit 200 of his / her client terminal 20, an ID assigned a new management ID according to the operation. An attached document is generated.

  When the document operation unit 200 prints an electronic document, a management ID may be generated, and the management ID may be embedded in the print result of the electronic document. The management ID can be embedded by, for example, a method of superimposing a code image indicating the management ID on the print image of the electronic document. Further, when the paper has an RFID (Radio Frequency Identifier) tag, a management ID may be written on the RFID tag. When printing is performed in this manner, the document operation unit 200 registers an ID-added document including meta information such as the management ID and the operation type “print” in the document management server 10. When an ID-added document is printed, an ID-added document including the management ID of the ID-added document as the parent ID 314 is generated. In the ID-added document corresponding to the print operation, print data such as page description language data indicating a printed image or bitmap image data, or a printed document file may be incorporated as the document content 320.

  When the document operation unit 200 reads a paper document in which the management ID is embedded, the document operation unit 200 assigns a new management ID to the reading operation, and includes an image of the reading result as the document content 320. The ID-added document is generated and registered in the document management server 10. The management ID read from the paper document is set in the parent ID 314 of the ID-added document. When copying a paper document in which a management ID is embedded, the above-described reading and printing processes are executed.

  Next, the document management server 10 will be described. The document management server 10 accumulates ID-added documents 300 sent from a plurality of client terminals 20 in the system, and provides various services to the user based on the accumulated information. As shown in FIG. 4, the document management server 10 includes a document DB (database) 100, a derivation relationship DB 110, a document registration unit 130, a request processing unit 140, and a transfer processing unit 150.

  The document DB 100 is a database that stores the document content 320 of the ID-added document 300 sent from the client terminal 20. Each document content 320 stored in the document DB 100 may be managed by a unique content ID. As the content ID, for example, a hash value by a cryptographic hash function of the document content may be used, but the content ID is not limited to this. The client terminal 20 may give the content ID. In this case, the content ID may be incorporated in the meta information 310. Further, instead of the content ID, the document content 320 may be stored in the document DB 100 in association with the management ID of the ID-added document 300 corresponding to the document content.

  The document registration unit 130 registers the document content 320 in the ID-added document 300 received from the client terminal 20 in the document DB 100 and the meta information 310 in the derivation relationship DB 110. Among them, the derivation relationship registration unit 132 is in charge of registration of the meta information 310. In addition, the document registration unit 130 passes the ID-added document 300 received from the client terminal 20 to the transfer processing unit 150.

  The derivation relationship DB 110 is a database that accumulates meta information mainly including derivation relationship information among such ID-added documents 300. FIG. 5 shows an example of data contents of the derivation relationship DB 110. One line of information in the table shown in FIG. 5 is a meta information record corresponding to one ID-added document 300. In this example, each item of parent ID, operation type, operator, and transfer information is registered in association with the management ID of each ID-added document 300. Of these, items other than the management ID, parent ID, and transfer information are not limited to those illustrated. Items that are necessary for management purposes may be recorded. In the example of FIG. 5, the address of the document management server 10 different from the document management server 10 having this derivation relationship DB 110 is used as the value of the transfer information item of the record corresponding to the ID-added document 300 with the management ID “Doc1”. Is registered.

  The meta information items illustrated in FIG. 5 are merely examples. For example, a path name indicating the storage location in the document DB 100 that stores the document content 320 in the ID-added document may be registered in the derivation relationship DB 110. If the document DB 100 has a function of searching the document content 320 by content ID, the content ID may be registered in the meta information record instead of the document storage path.

  Note that FIG. 5 is merely a representation of the data managed by the derivation relationship DB 110 from the viewpoint of contents, and does not define a specific representation format or database format. For example, the derivation relationship DB 110 can be constructed as a general relational database, or an XML (eXtensible Markup Language) document describing meta information excluding the management ID is constructed as a database in which the management ID is registered as a key. You can also.

  The data content of the derivation relationship DB 110 shown in FIG. 5 has a tree structure as shown in FIG. This is a tree structure in which a management ID is a node and a parent-child relationship between management IDs is an edge.

  Hereinafter, the document history shown in the examples of FIGS. 5 and 6 will be described in chronological order.

  In this example, first, a “registration” operation of a document (form) is executed on the client terminal 20 of userA. The “registration” operation is an operation for registering in the server 10 a document that is not registered in the document management server 10 (that is, a document that does not have a management ID). During this operation, the transfer information setting unit 220 of the client terminal 20 accepts input of transfer information “http://fs.fujixerox.co.jp” by userA. Then, the meta information having the management ID “Doc1”, the parent ID is empty, the operation type is “registration”, and the transfer information is “http://fs.fujixerox.co.jp”, the document contents of the document, , Including ID, “Doc1” is generated and sent to the document management server 10 from the client terminal of userA. In response to this, the document management server 10 registers the document contents in the ID-added document “Doc1” in the document DB 100 and meta information in the derivation relationship DB 110. In the following description, the registered document content is represented by “Content1” for identification. Thereafter, userA distributes the registered ID-added document to other users userB and userC. This distribution can be performed, for example, by attaching the ID-added document to an e-mail and transmitting it to each user.

  In this example, the transfer information setting unit 220 of each client terminal 20 stores the transfer information when the operation of “registration” or “update (registration as an updated version)” is performed in the document operation unit 200. The above-described transfer information setting process that accepts user input and passes it to the document operation unit 200 is performed. When an operation other than “registration” or “update” is performed, the transfer information setting process is not performed. .

  After that, when userB edits the ID-added document “Doc1” by the document operation unit 200 of his / her client terminal 20 and instructs “Register as update” on the operation menu, the client terminal 20 has the management ID 312. An ID-added document “Doc2” having a value “Doc2”, a parent ID 314 value “Doc1”, and an operation type value “update” is generated. At this time, it is assumed that userB has not input transfer information. Therefore, the meta information 310 of the ID-added document “Doc2” does not include transfer information. Then, the client terminal 20 registers the generated ID-added document “Doc2” in the document management server 10. The document content 320 is changed from “Content1” to “Content2” by the editing performed by userB. A record with the management ID “Doc2” is registered in the derivation relationship DB 110 of the document management server 10.

  Note that the ID-added document “Doc1” in the client terminal 20 of userB before this operation is replaced with the ID-added document “Doc2” by the document operation unit 200 in accordance with this operation. In this replacement process, the derivation relationship incorporating unit 204 changes the management ID 312 of the meta information 310 among the original ID-added document “Doc1” to the newly issued ID “Doc2” and the original document “Doc1”. Management ID "Doc1" is set to the value of the parent ID 314. Further, the derivation relationship incorporating unit 204 changes the value of the operation type in the log information 316 to “update” which is the type of the current operation, changes the value of the operation time to the date and time of the update, and Change the value to userB. Furthermore, since the transfer information is not set in this operation, the derivation relationship incorporating unit 204 deletes the transfer information in the log information 316 of the original ID-added document “Doc1”. Further, since the document content changes due to editing, the document operation unit 200 replaces the document content 320 of the original ID-added document “Doc1” from “Content1” to “Content2”.

  When the operation for the ID-added document “Doc1” is executed in this way, the operation is replaced with the post-operation ID-added document “Doc2”. Therefore, after the replacement, the ID-added document “Doc1” itself does not exist in the client terminal 20, but the ID-added document “Doc2” exists instead.

  Thereafter, userB distributes the ID-added document “Doc2” to userD by e-mail or the like.

  Next, the document operation unit 200 of the userC client terminal 20 performs an “update (registered as an updated version)” operation on the ID-added document “Doc1” distributed from userA. The client terminal 20 of userC generates a new ID-added document “Doc3” including the document content “Content3” of the update result, the parent ID is “Doc1”, and the operation type value is “update”. Register in the document management server 10. The ID-added document “Doc1” of the client terminal 20 of userC is replaced with this ID-added document “Doc3”. In this operation, it is assumed that the transfer information is not set by userC, and the log information 316 of the ID-added document “Doc3” does not include the transfer information.

  Next, userD performs an operation of printing two copies of the ID-added document “Doc2” distributed from userB by the document operation unit 200 of his / her client terminal 20. In response to this operation, two new ID-added documents “Doc4” and “Doc5” respectively corresponding to the two copies of the paper document as the print result are generated and registered in the document management server 10. In both the ID-added documents “Doc4” and “Doc5”, the parent ID is “Doc2”, and the operation type value is “print”. Note that when the “print” operation is performed, the processing by the transfer information setting unit 220 is not executed, and therefore neither the ID-added documents “Doc4” and “Doc5” include the transfer information in the log information 316. . Further, the ID-added document “Doc2” before printing is replaced with the ID-added documents “Doc4” and “Doc5” after printing in the client terminal 20. Since the document contents are not changed by the printing operation, the document contents of the ID-added documents “Doc4” and “Doc5” after printing remain “Content2” which is the same as the ID-added document “Doc2” before printing. In addition, information representing the management IDs “Doc4” and “Doc5” of the ID-added document generated by the printing operation is embedded in the two copies of the paper document as a result of the printing.

  Thereafter, the userE writes the paper document as a print result in which the information representing the management ID “Doc4” is embedded by handwriting, and the document operation unit 200 realized in the scanner device connected to the document management server 10 via the network. Is used to read the written paper document and instruct "Register the read document as an answer" on the operation menu. In response to this operation, the document operation unit 200 generates a new ID-added document “Doc6” with the management ID “Doc4” read from the paper document as the parent ID and the operation type value “answer”. Register with the management server 10. The document content 320 of the ID-added document “Doc6” is set to “Content4” which is information obtained by reading a paper document. When the “answer” operation is performed, the transfer information is not set.

  Further, userF writes the printed paper document in which the information representing the management ID “Doc5” is embedded, and the document operation unit 200 is used to scan the written paper document to read “read document”. Is registered as an answer ”, an ID-added document“ Doc7 ”having a parent ID“ Doc5 ”and an operation type value“ answer ”is generated and registered in the document management server 10. Thereafter, userG writes the printed paper document in which information representing the management ID “Doc5” is embedded, and executes the “answer” operation similar to the above for the written paper document to the document operation unit 200. Then, an ID-added document “Doc8” whose parent ID is “Doc5” and whose operation type value is “answer” is generated and registered in the document management server 10. The document contents 320 of the ID-added documents “Doc7” and “Doc8” are set to “Content5” and “Content6”, which are information obtained by reading the paper document after writing, respectively. The log information 316 of the ID-added documents “Doc7” and “Doc8” does not include transfer information.

  5 and 6 show the state of the document or operation derived from “Doc1” in the derivation relationship DB 110 at this point.

  In the above, taking the data content of the derivation relation DB 110 as an example, the state of registration of document operation information in this system has been described.

  Returning to the description of FIG. 4, the request processing unit 140 provides a service using the derivation relationship DB 110 in response to a service request including the management ID from the client terminal 20. As a service provided by the request processing unit 140, for example, there is a service for searching for the latest version of a document corresponding to the management ID in the service request. Another example is a service that provides log information about an ancestor (root) document corresponding to the management ID in the service request or the ancestor. As another example, there is a service that provides a history of the management ID, that is, a history of operations that the document has passed from the founder to the management ID (for example, a list of information indicating who performed what operation when). There is also a service that accepts specification of search conditions for attribute items registered in the derivation relationship DB 110 and provides a list of ID-added documents that satisfy the search conditions.

  The service request is issued based on the ID-added document held in the client terminal 20. For example, when the user opens an ID-added document using the document operation unit 200 of the client terminal 20, the document operation unit 200 provides a service menu using the derivation relationship, and the service desired by the user from the menu is provided. The specification of is accepted. Then, a service request including the management ID of the document with ID and a code indicating the designated service is transmitted to the request processing unit 140 of the document management server 10. At this time, a user interface screen for designating search conditions for attribute items such as user identification information and operation date / time may be provided, and the search conditions input via this screen may be transmitted to the request processing unit 140 together. . Further, in addition to the management ID, the code indicating the service, and the search condition, other information such as the identification information of the instructing user and the authentication information input by the user is transmitted from the client terminal 20 to the request processing unit 140. You may do it.

  As another example, it may be considered that the designation of a service by the user is regarded as one “operation” and a new management ID is assigned to the “operation”. In this case, an ID-added document including the code of the specified service as the operation type, the management ID of the original ID-added document used in the specification as a parent ID is generated, and this ID-added document is requested as a service request. May be sent to the document management server 10. In this case, the request processing unit 140 determines a service to be provided based on the operation type information in the received ID-added document, and similarly uses the parent ID in the ID-added document as a starting point for the process of tracing the derivation relationship.

  When the request processing unit 140 receives a service request from the client terminal 20, the derivation relationship between the management ID and the parent ID registered in the derivation relationship DB 110 is configured with the management ID specified in the service request as a starting point. The tree traverses the tree and uses the information obtained as a result of the scan to execute the service requested by the user.

  The transfer processing unit 150 performs processing for transferring the ID-added document 300 received from the client terminal 20 to another apparatus. When the document registration unit 130 receives the ID-added document 300 from the client terminal 20, the transfer processing unit 150 acquires the ID-added document 300 from the document registration unit 130 and sets it as a processing target. The transfer processing unit 150 includes a transfer destination determination unit 152 and a document information transfer unit 154. The transfer destination determination unit 152 determines whether or not to execute the transfer process for the ID-added document 300 acquired from the document registration unit 130 and the transfer destination when the transfer process is executed. For example, the transfer destination determining unit 152 first determines whether or not to execute the transfer process for the ID-added document 300 according to the operation type included in the log information 316 of the ID-added document 300. If it is determined to execute the transfer process, the transfer destination of the ID-added document 300 is determined with reference to the derivation relationship DB 110. The document information transfer unit 154 performs processing for transferring the ID-added document 300 to the transfer destination determined by the transfer destination determination unit 152.

  Hereinafter, the process performed by the transfer processing unit 150 will be described in detail.

  FIG. 7 is a flowchart illustrating an example of a processing procedure executed by the transfer processing unit 150. When the document registration unit 130 receives the ID-added document 300 from the client terminal 20 and performs the above-described registration processing in the document DB 100 and the derivation relationship DB 110 for the received ID-added document 300, the transfer processing unit 150 is notified of this. To do. Upon receiving this notification from the document registration unit 130, the transfer processing unit 150 starts processing of the procedure illustrated in FIG.

  Referring to FIG. 7, first, in step S10, the transfer processing unit 150 acquires the ID-added document 300 received by the document registration unit 130 from the document registration unit 130 as an ID-added document to be processed.

  Next, in step S20, the transfer destination determining unit 152 determines whether or not to execute the transfer process for the processing target ID-added document according to the operation type included in the log information of the processing target ID-added document. . For example, when the operation type of the ID-added document to be processed is a specific operation type set in advance, it is determined to execute the transfer process, and when it is another operation type, it is determined not to execute the transfer process. In the following, if the operation type is “answer (registers a document read by the scanner as an answer)”, the transfer process is executed. If the operation type is other than “answer”, the system administrator etc. An example in the case of being set in advance will be described.

  When the operation type of the ID-added document to be processed is “answer”, the transfer destination determining unit 152 determines to execute the transfer process on the ID-added document to be processed, and the process proceeds from step S20 to step S30. . If the operation type of the ID-added document to be processed is not “Answer”, the transfer destination determination unit 152 determines not to execute the transfer process, and the process ends without performing the processes in and after step S30.

  For example, in the document history described above with reference to FIG. 5 and FIG. 6, the document management server 10 stores the ID-added documents “Doc1” to “Doc5” (all of which the operation type is not “answer”) by each client. When received from the terminal 20, the transfer destination determining unit 152 determines not to execute the transfer process, and proceeds to NO as a result of the determination in step S20 of FIG. 5 and 6, when the document management server 10 receives the ID-added documents “Doc6”, “Doc7”, and “Doc8” (the operation type is “answer”) from each client terminal 20. The transfer destination determination unit 152 determines to execute the transfer process, and proceeds to YES as a result of the determination in step S20 of FIG.

  In step S30, the transfer destination determining unit 152 refers to the derivation relationship DB 110 and acquires transfer information for determining the transfer destination of the ID-added document to be processed. FIG. 8 shows an example of a detailed procedure of the transfer information acquisition process in step S30 of FIG.

  When step S30 in FIG. 7 is started, processing of the procedure illustrated in FIG. 8 is started.

  Referring to FIG. 8, in step S302, transfer destination determining unit 152 initializes a route list. In the path list, in the tree structure represented by the derivation relation group registered in the derivation relation DB 110, ID-added documents (nodes) included in the route traced back to the ancestor direction from the ID-added document to be processed (the corresponding node). It is a list to be recorded.

  Next, in step S304, the transfer destination determination unit 152 sets the management ID of the ID-added document to be processed acquired from the document registration unit 130 as the attention ID, and registers the attention ID in the route list in step S306.

  In step S308, the transfer destination determination unit 152 refers to the derivation relationship DB 110 and acquires a record corresponding to the attention ID.

  In step S310, the transfer destination determining unit 152 determines whether or not a value is set in the transfer information item of the record acquired in step S308. If a value is set in the transfer information item, the process advances to step S312 to acquire the value of the transfer information item set in the record. That is, the transfer information set for the attention ID is acquired. When the process of step S312 ends, the process illustrated in FIG. 8 ends.

  As a result of the determination in step S310, when it is determined that no value is set in the transfer information item of the record acquired in step S308, the process proceeds to step S314.

  In step S314, the transfer destination determining unit 152 determines whether the value of the parent ID item of the record acquired in step S308 is “Null”. The value of the parent ID item being “Null” means that in the tree structure represented by the derivation relationship group registered in the derivation relationship DB 110, the node corresponding to the attention ID is the root node. If the node corresponding to the attention ID is not the root node, the value of the parent ID item is not “Null”, and as a result of the determination in step S314, the process proceeds to step S316. In step S316, the value of the parent ID is set as a new attention ID. Thereafter, in step S306, this new attention ID is added to the end of the route list, and the processing in step S308 and subsequent steps is repeated.

  In step S314, when the node corresponding to the attention ID corresponds to the root node in the tree structure of the derivation relationship, the value of the parent ID item is “Null”, and as a result of the determination, the process proceeds to step S318.

  In step S318, the transfer destination determining unit 152 acquires initial transfer information that is set in advance by a system administrator or the like. The process of step S318 is executed in the tree structure of the derivation relationship, and the ID corresponding to any of the nodes included on the route traced from the ID-added document to be processed to the root node of the tree structure of the derivation relationship. This is also the case where transfer information is not set for attached documents. In this case, transfer information cannot be acquired from the derivation relationship DB 110. The default transfer information is so-called default transfer information that is set in advance by a user or a system administrator as transfer information used in such a case. The initial transfer information is set in common for ID-added documents whose log information does not include transfer information among ID-added documents corresponding to the root node of the tree structure of the derivation relation in the derivation relation DB 110. This information can be considered as transfer information. The default transfer information may be, for example, a specific server address. After step S318, the process in FIG. 8 ends.

  As a result of the process illustrated in FIG. 8, if the transfer information is included in the log information of the ID-added document to be processed, this transfer information is acquired. If the log information of the ID-added document to be processed does not include transfer information, one node from the ID-added document to be processed to the root node in the tree structure represented by the derivation relation group in the derivation relation DB 110 Going back one by one, when a node for which transfer information is set first appears, the transfer information of that node is acquired (loop processing including steps S306 to 310, S314, and S316). In other words, among the nodes that are included in the route that goes back from the document with ID to be processed toward the root node of the tree structure and for which transfer information is set, the ID that has the most processing target in the route Transfer information of a node close to the document is acquired. Further, when transfer information is not set for any of the nodes included in the route, initial transfer information is acquired.

  For example, in the example of the document history shown in FIGS. 5 and 6, when the ID-added document “Doc6” is a processing target of the transfer processing unit 150, the processing-target ID-added document “Doc6” has transfer information. Not set. Therefore, by the loop processing including steps S306 to 310, S314, and S316 in the processing of FIG. 8, processing that goes back one node at a time from the node of “Doc6” in the tree structure shown in FIG. In the tree structure shown in FIG. 6, the node of the ID-added document “Doc1” appears first as a node in which transfer information is set, one node after the “Doc6” node. Therefore, when the ID-added document “Doc6” is a processing target, the transfer information “http://fs.fujixerox.co.jp/” of the ID-added document “Doc1” is acquired as a result of the processing in the example of FIG. Is done.

  Further, as a result of the processing in the example of FIG. 8, the route list starts from the management ID of the ID-added document to be processed, and is the node set with the transfer information and closest to the ID-added document to be processed. This is a list in which the management IDs of the documents included in the path traced back through the tree structure of the derivation relationship are arranged in order from the ID-added document to be processed. In the above example where the ID-added document “Doc6” shown in FIG. 5 and FIG. 6 is the processing target, the contents of the route list are ““ Doc6 ”,“ Doc4 ”,“ Doc2 ”,“ Doc1 ””.

  When the transfer information acquisition process illustrated in FIG. 8 ends, the process proceeds to step S40 in FIG. Referring to FIG. 7 again, in step S40, the transfer destination determination unit 152 uses the transfer information acquired in the transfer information acquisition process (step S30, FIG. 8) to transfer the processing target ID-added document. Transfer destination information representing In the present embodiment, in the generation of transfer destination information, the transfer destination determination unit 152 further uses the route list generated in the transfer information acquisition process of FIG. For example, the record of the derivation relationship DB 110 is referred to for the management ID included in the route list, and the record whose operation type is “update” is searched. In the above example where the ID-added document “Doc6” in the table of FIG. 5 is processed, the derivation relationship among the management IDs included in the route list “Doc6”, “Doc4”, “Doc2”, “Doc1”. A record with the management ID “Doc2” whose operation type is “update” in the record of the DB 110 is obtained as a search result. Then, the value of the operator's item included in the search result record is acquired. If a plurality of records are obtained as a search result, the operator of the record corresponding to the management ID closest to the head of the route list is acquired. In this example, the operator “userB” of the record with the management ID “Doc2” is acquired.

  The transfer destination determination unit 152, for example, the transfer information acquired as a result of the processing of FIG. 8, the information indicating the operator of the “update” operation acquired by the above processing on the route list, and the ID-added document to be processed The destination information is generated by combining the information representing the operator included in the log information. In this example in which the ID-added document “Doc6” in FIG. 5 is a processing target, the transfer destination determination unit 152, for example, transfers information “http://fs.fujixerox.co.jp” acquired as a result of the processing in FIG. ”And the operator“ userB ”of the“ update ”operation node on the route list and the operator“ userE ”of the ID-added document“ Doc6 ”to be processed, and transfer destination information“ http: // fs.fujixerox.co.jp/userB/userE.xdw ”is generated. This transfer destination information is the user of the ID document operator corresponding to the “update” operation of the derivation source of the ID target document to be processed in the document management server 10 represented by the transfer information acquired as a result of the processing of FIG. The processing target ID is attached as a file having a file name obtained by adding the extension (.xdw) indicating the file format to the user name of the operator of the processing target ID-added document under the directory (folder) having the same name as the name. Represents storing a document.

  FIG. 9 illustrates an example of transfer destination information generated by the transfer destination determination unit 152 for each of the ID-added documents “Doc6”, “Doc7”, and “Doc8” in the document history examples illustrated in FIGS. 5 and 6. . The transfer destination information generated for the ID-added document “Doc6” is as described above. Regardless of whether the ID-added documents “Doc7” and “Doc8” are to be processed, as in the case of the ID-added document “Doc6”, the transfer information that appears first in the tree structure shown in FIG. 6 is set. Since the node is a “Doc1” node, the transfer information “http://fs.fujixerox.co.jp/” of “Doc1” is acquired as the transfer information. The route list for the ID-added document “Doc7” is “Doc7”, “Doc5”, “Doc2”, “Doc1”, and the route list for the ID-added document “Doc8” is “Doc8”, “Doc5”. "," Doc2 "," Doc1 "". Therefore, in both cases of the ID-added documents “Doc7” and “Doc8”, the “update” operation node in the route list is the ID-added document “Doc2”, and the operator is “userB”. From the above, in the transfer destination information generated for each of the ID-added documents “Doc7” and “Doc8”, the part of “http://fs.fujixerox.co.jp/userB/” is the ID-added document “Doc6”. It is common. The file name portions of the transfer destination information of the ID-added documents “Doc7” and “Doc8” are “userF.xdw” and “userG.xdw” based on the operator of each ID-added document.

  When the transfer destination information is generated by the transfer destination determination unit 152 (step S40), the document information transfer unit 154 transfers the ID-added document 300 to the transfer destination represented by the generated transfer destination information in step S50. To do. When step S50 ends, the process of FIG. 7 ends.

  The processing of the example of FIG. 7 described above is started by the transfer processing unit 150 of the document management server 10 every time an operation is performed on the document at the client terminal 20 and the ID-added document is registered in the document management server 10. The When the operation type of the ID-added document is a predetermined operation type, transfer destination determination and transfer processing (steps S30 to S50) are executed. Therefore, each time an operation of a predetermined operation type is performed in the document operation unit 200 of the client terminal 20, the ID-added document as the operation result is transferred from the document management server 10 to another apparatus. In the above-described example, each time a paper document written by the user is read by the scanner and “registers the read document as an answer”, the ID-added document including the read document content is transferred from the document management server 10 to the transfer destination. The data is transferred to the transfer destination determined by the determination unit 152.

  As described above, according to the processing of the example described with reference to FIGS. 7 and 8, the ID-added document whose operation type is “answer” is the derivation-source ID-added document in the transfer destination device, and the “update” Are stored in a directory having the same name as the user name of the operator of the ID-added document corresponding to the operation. The file name of the ID-added document to be stored includes the user name of the operator of the ID-added document. Therefore, the ID-added document corresponding to the “update” operation by any user can be confirmed by checking the storage location and file name of the ID-added document transferred from the document management server 10 and stored in the transfer destination apparatus. On the other hand, it is identified which user has “answered”.

  In the above example, among the management IDs included in the route list, when there are a plurality of records with the operation type “update” in the derivation relationship DB 110 record, the record corresponding to the management ID closest to the route list is displayed. An operator is acquired and used to generate transfer destination information. In another example, an operator may be acquired for each of a plurality of records whose operation type is “update” and used to generate transfer destination information. For example, transfer destination information including a directory name obtained by combining user names of a plurality of corresponding operators may be generated. For example, in the management ID included in the route list, two records with the operation type “update” in the derivation relation DB 110 are searched, and when the operators of the searched records are userX and userY, “< Transfer destination information having a structure of “transfer information acquired as a result of the processing of FIG. 8> / userX / userY / <file name including the user name of the operator of the ID-added document to be processed>” is generated.

  In the example of the transfer information acquisition process described above, when the transfer information is not acquired even if the tree structure in the derivation relationship DB 110 is traced back from the ID-added document to be processed to the root node, the transfer information of the initial setting is used. Instead of acquiring information (step S318 in FIG. 8) and proceeding to transfer destination information generation processing (step S40 in FIG. 7), the processing by the transfer processing unit 150 is terminated without performing the processing in steps S318 and S40 and subsequent steps. May be.

  In the processing example of the embodiment described above, an address representing a transfer destination device is set as the transfer information. The transfer information set for each ID-added document 300 is not limited to this example. For example, it is possible to set, as transfer information, information that specifies which operation type of operation is performed when the transfer process is executed. Also, for example, in the transfer information, it can be instructed to generate the transfer destination information according to different rules according to different operation types.

  FIG. 10 shows a case where the operation type to be transferred by the document management server 10 is specified, and transfer information that instructs generation of transfer destination information according to different rules according to different operation types is set. An example of the content of transfer information set for each ID-added document is shown. FIG. 10 is also an example of the data contents of the derivation relationship DB 110. FIG. 11 shows a tree structure represented by the data content derivation relationship of FIG.

  Referring to FIG. 10, the record corresponding to each management ID includes items of parent ID, operation type, operator, file name, transfer information 1 and transfer information 2. The parent ID, operation type, and operator items are the same as in the example of FIG. The file name is a name given to the electronic document file of the ID-added document. Each item of the transfer information 1 and the transfer information 2 represents two types of transfer information, and includes a transfer operation, a transfer address, and a rule ID as subordinate items. When the ID-added document 300 including the operation type set in the transfer operation item in the log information 316 is registered in the document management server 10, the transfer processing unit 150 transfers the transfer address and rule ID corresponding to the transfer operation. Is used to execute the transfer process for the ID-added document 300. In the transfer address field, the address of the transfer destination device is set. In the rule ID item, rule identification information that defines how to use transfer information to generate transfer destination information is set.

  The rule corresponding to each rule ID is preset by a system administrator or the like and registered in a storage device (not shown) of the document management server 10, for example. FIG. 12 shows an example of rule contents corresponding to the rule IDs “1” and “2”. In the example of FIG. 12, the rule corresponding to the rule ID “1” includes the transfer address included in the transfer information acquired with reference to the derivation relationship DB 110 and the file name of the ID-added document to be processed. It represents a rule for generating a combined address as transfer destination information. In FIG. 12, the rule corresponding to the rule ID “2” includes a transfer address included in the transfer information acquired by referring to the derivation relationship DB 110, a user name representing an operator of the ID-added document to be processed, Represents a rule for generating an address combining the above as transfer destination information.

  Hereinafter, the history of document operations illustrated in FIG. 10 and FIG. 11 will be described mainly in chronological order with respect to registration processing and transfer processing in the document management server 10. In the following description, the transfer information setting unit 220 of the client terminal 20 performs transfer information setting processing only when a “registration” operation or an “update” operation is performed in the document operation unit 200. To do.

  First, the “registration” operation of the document is performed at the client terminal 20 of userA. During this operation, the transfer information setting unit 220 of the client terminal 20 associates a preset transfer destination information generation rule with its rule ID together with information that prompts the user to set transfer information. Information to be represented (see FIG. 12) is acquired from the document management server 10 and displayed on the display device, and input of transfer information by the user is accepted. Here, it is assumed that userA has set two types of transfer information (transfer information 1 and transfer information 2). For transfer information 1, set the transfer operation to “Registration, Update”, the transfer address to “http://fs1.fujixerox.co.jp/questionnaire”, the rule ID to “1”, and transfer information 2 Suppose that the transfer operation is set to “answer”, the transfer address is set to “http://fs1.fujixerox.co.jp/answer”, and the rule ID is set to “2”. The document operation unit 200 of the client terminal 20 generates an ID-added document 300 having a management ID “Doc1”, a parent ID “Null”, and an operation type “registration”. In the log information 316 of the ID-added document “Doc1”, information representing the above-described contents set by the userA for the transfer information 1 and the transfer information 2 is incorporated. Further, the log information 316 incorporates the file name “lecture class 1_v1.doc” of the electronic document file corresponding to the ID-added document “Doc1”. The ID-added document “Doc1” is transmitted to the document management server 10 by the registration processing unit 210.

  In the document management server 10 that has received the ID-added document “Doc1” from the client terminal 20, the document registration unit 130 registers the document content in the document DB 100 and the meta information in the derivation relationship DB 110 for the ID-added document “Doc1”. Registration processing is performed. In addition, the document registration unit 130 notifies the transfer processing unit 150 that registration processing has been performed on the ID-added document “Doc1”. In this example in which the operation type for executing the transfer process is specified in the transfer information set for the ID-added document, the transfer processing unit 150 uses the procedure illustrated in FIG. 7 and FIG. The process according to the illustrated procedure is performed.

  Referring to FIG. 13, in step S100, the transfer processing unit 150 acquires the ID-added document “Doc1” received by the document registration unit 130 from the document registration unit 130 as an ID-added document to be processed. Next, in step S102, the transfer destination determining unit 152 of the transfer processing unit 150 sets the management ID “Doc1” of the ID-added document to be processed as the attention ID. Further, in step S104, the transfer destination determining unit 152 acquires a record corresponding to the attention ID from the derivation relationship DB 110. Here, the record of the management ID “Doc1” in the table of FIG. 10 is acquired. In step S106, it is determined whether or not the acquired record includes the transfer information. If included, the process proceeds to step S108. If not included, the process proceeds to step S116. Since the record with the management ID “Doc1” includes the transfer information, the process advances to step S108 here, and the transfer destination determination unit 152 acquires the transfer information in the record with “Doc1” as the attention ID. Next, in step S110, the transfer destination determining unit 152 determines whether or not the operation type in the log information 316 of the ID-added document to be processed is included in the “transfer operation” item of the transfer information acquired in step S110. Determine whether. If included, the process proceeds to step S112, and if not included, the process ends. This time, in the acquired transfer information (transfer information of the ID-added document “Doc1”), “registration / update” is set as the transfer operation of the transfer information 1, and “ “Answer” is set. Therefore, since the operation type “registration” of the ID-added document “Doc1” to be processed is included in the transfer operation in the transfer information acquired in step S108, the process proceeds to step S112.

  Next, in step S112, the transfer destination determination unit 152 generates transfer destination information for the ID-added document to be processed. In step S112, the transfer destination determination unit 152 uses the transfer address and rule ID associated with the operation type of the ID-added document to be processed in the transfer information acquired in step S108. Since the operation type of the current ID-added document “Doc1” to be processed is “registration”, the transfer address “http: //fs1/fujixerox.co” of the transfer information 1 including “registration” in the transfer operation item. .jp / questionnaire "and rule ID" 1 "are used. The transfer destination determination unit 152 generates transfer destination information of the document with the ID “Doc1” in accordance with the transfer destination information generation rule (see FIG. 12) corresponding to the rule ID “1”. That is, the transfer address “http: //fs1/fujixerox.co.jp/questionnaire” of the transfer information 1 is combined with the file name “Lecture 1_v1.doc” of the ID-added document “Doc1” to be processed. The address “http: //fs1/fujixerox.co.jp/questionnaire/lecture 1_v1.doc” is generated as transfer destination information. Thereafter, in the document information transfer process of step S114, the document information transfer unit 154 stores the ID-added document “Doc1” in the storage destination indicated by the address of the transfer destination information.

  After processing in the document management server 10 for the ID-added document “Doc1”, userA edits the ID-added document “Doc1” at his / her client terminal 20, and the file name is “Lecture 1_v2.doc”. Then, when “Register as update version” is designated on the operation menu, the document operation unit 200 has a parent ID “Doc1”, an operation type “update”, and a file name “Seminar 1_v2.doc”. An ID-added document “Doc2” is generated and registered in the document management server 10. At this time, it is assumed that userA selects not to set transfer information, and the log information 316 of the ID-added document “Doc2” does not include transfer information.

  When the document management server 10 receives the ID-added document “Doc2” from the client terminal 20, the document registration unit 130 performs registration processing in the document DB 100 and the derivation relationship DB 110. Upon receiving the notification that the registration processing has been performed from the document registration unit 130, the transfer processing unit 150 starts the processing of FIG. 13, and acquires the ID-added document “Doc2” as a processing target in step S100. Next, the transfer destination determination unit 152 sets the management ID “Doc2” of the ID-added document to be processed as the attention ID (step S102), and acquires a record corresponding to the attention ID “Doc2” from the derivation relationship DB 110 (step S104). ). Since the record with the attention ID “Doc2” does not include the transfer information, as a result of the determination in step S106, the process proceeds to step S116, and the value of the parent ID item included in the record with the attention ID “Doc2” is “Null”. It is determined whether or not. If it is determined in step S116 that the value of the parent ID item is “Null”, the transfer processing unit 150 ends the process, and if it is not “Null”, the process proceeds to step S118. Since the parent ID of the attention ID “Doc2” is “Doc1” and not “Null”, the process proceeds to step S118, and the parent ID “Doc1” is set as a new attention ID, and the processes in and after step S104 are repeated. In this case where “Doc1” is the attention ID, the transfer information set for “Doc1” is acquired by the processing of steps S106 and S108.

  As described above, in the process of the procedure illustrated in FIG. 13, when the transfer information is not set in the ID-added document to be processed, the loop process including steps S104, S106, S116, and S118 is performed in the derivation relation DB 110. The tree structure of the derivation relationship is traced back one node at a time from the ID-added document to be processed, and a node for which transfer information is set is searched. Then, the transfer information of the node in which the transfer information that appears first is set is acquired.

  After the transfer information set for “Doc1” is acquired, the operation type “update” included in the log information 316 of the ID-added document “Doc2” to be processed is acquired in the determination in step S110. Since it is included in the value of the transfer operation item in the use information (transfer information of “Doc1”), the process proceeds to the transfer destination information generation process in step S112. At this time, the transfer destination determination unit 152 uses the transfer information 1 (see FIG. 10) including “update”, which is the operation type of the ID-added document “Doc2” to be processed, in the transfer operation item. Generate. Therefore, using the transfer address “http: //fs1/fujixerox.co.jp/questionnaire” included in the transfer information 1, a rule corresponding to the rule ID “1” included in the transfer information 1 (FIG. 12). The transfer destination information “http: //fs1/fujixerox.co.jp/questionnaire/lecture class 1_v2.doc” is generated according to (see). The ID-added document “Doc2” is stored in the storage destination indicated by the transfer destination information (step S114).

  Next, when the ID-added document “Doc2” is printed by userD, the ID-added document “Doc3” corresponding to this print operation is generated and registered in the document management server 10. Information representing the management ID “Doc3” is embedded in the paper document of the print result. In the transfer processing unit 150 that processes the ID-added document “Doc3”, the tree structure of the derivation relationship (FIG. 11) in the derivation relationship DB 110 is changed to “Doc3” by the loop process including steps S104, S106, S116, and S118. Going back one node at a time, when “Doc1” in which transfer information is set becomes the attention ID, the process proceeds from step S106 to step S108, and the transfer information of “Doc1” is acquired. In the determination in step S110, since “print”, which is the operation type of the ID-added document “Doc3” to be processed, is not included in the transfer operation item of the acquired transfer information, the process proceeds to NO as a result of determination. The processing unit 150 ends the process without performing the transfer destination information generation process (step S112) and the document information transfer process (step S114) for the ID-added document “Doc3”.

  Further, when the userE writes in the paper document in which the information representing the management ID “Doc3” is embedded, and the written paper document is scanned by the scanner and “registers the read document as an answer”, the document operation unit 200 The ID-added document “Doc4” whose parent ID is “Doc3” and whose operation type is “Answer” is generated and registered in the document management server 10.

  In step S100 in FIG. 13, the transfer processing unit 150 of the document management server 10 acquires the ID-added document “Doc4” as a processing target. Then, through a loop process including steps S104, S106, S116, and S118, the tree structure of the derivation relationship (see FIG. 11) is traced back from “Doc4” to be processed to “Doc1” in which transfer information is set, Get transfer information for "Doc1". Since the operation type “answer” of the ID-added document “Doc4” to be processed is included in the item of transfer operation of the acquired transfer information, the process proceeds to step S112 as a result of the determination in step S110. In step S112, the transfer destination determination unit 152 uses the transfer information 2 (see FIG. 10) including “answer” that is the operation type of the ID-added document “Doc4” to be processed in the transfer operation item. Is generated. That is, according to the transfer destination information generation rule (see FIG. 12) corresponding to the rule ID “2” included in the transfer information 2, the transfer address “http: //fs1/fujixerox.co. "http / fs1 / fujixerox.co.jp / answer / userE.xdw", which is a combination of the "jp / answer" and the user name "userE" of the operator of the ID-added document "Doc4" to be processed Generated as transfer destination information. The document information transfer unit 154 stores the ID-added document “Doc4” in the storage position represented by the transfer destination information (step S114).

  As described above, according to the process of the example of FIG. 13 in the case where the type of operation to be transferred from the document management server 10 is specified in the transfer information incorporated in the log information of the ID-added document, the document management server 10 When the transfer information is set in the ID-added document to be processed, the transfer processing unit 150 acquires the transfer information (the process proceeds to YES in the first determination in step S106 after the process is started). If the transfer target information is not set in the processing target ID-added document, the tree structure of the derivation relationship in the derivation relationship DB 110 is traced one node at a time starting from the target ID-added document, and the transfer information is set. When a node (ID-added document) that has been identified is first discovered, transfer information for that node is acquired (loop processing including steps S104, S106, S116, and S118). In other words, among the nodes that are included in the route that goes back from the document with ID to be processed toward the root node of the tree structure and for which transfer information is set, the ID that has the most processing target in the route Get transfer information for nodes close to the document. After acquiring the transfer information, the transfer processing unit 150 performs transfer processing according to whether or not the operation type of the ID-added document to be processed is specified as the type of operation to be transferred in the acquired transfer information. Whether or not to execute is determined (step S110). If no transfer information is set for any ID-added document included in the path that goes back from the ID-added document to be processed to the root node of the tree structure in the derivation relation tree structure, the steps in FIG. 13 are performed. The process proceeds to NO in the determination of S116, and the process ends without performing the transfer destination information generation process (step S112) and the document information transfer process (step S114).

  In still another example of the transfer information set for the ID-added document, when the document management server 10 receives one ID-added document 300, the transfer information that instructs to execute a plurality of different modes of transfer processing Information may be set. FIG. 14 shows an example of the default transfer information when a plurality of different modes of transfer processing are executed for one ID-added document 300. The transfer information shown in FIG. 14 is an example of the initial transfer information acquired in step S318 in FIG. 8 when the transfer processing unit 150 executes the process illustrated in FIGS. 7 and 8, for example. It is.

  Referring to FIG. 14, two types of transfer information, transfer information 1 and transfer information 2, are set in association with each operation type. In the transfer information 1 and the transfer information 2, subordinate items of the transfer destination type, document delivery, and transfer address are set, respectively. The transfer destination type represents the type of the transfer destination device. Examples of the types of transfer destination apparatuses include the document management server 10, an e-mail server, and a FAX (fax, facsimile) server according to the present embodiment. In the example of FIG. 14, the transfer destination type of the transfer information 1 is set to “document management server”, which represents, for example, the same type of server as the document management server 10 of the present embodiment. . In addition, the transfer destination type of the transfer information 2 is set to “SMTP”, which represents an e-mail server using SMTP (Simple Mail Transfer Protocol). The item of document delivery indicates whether or not the document content 320 of the ID-added document 300 is transmitted to the transfer destination in the transfer process. If “yes” is set in the document sending item, the ID-added document 300 including the document content 320 is transmitted to the transfer destination. If “no” is set, the document content 320 of the ID-added document 300 is displayed. Do not send to the forwarding destination. When the document content 320 is not transmitted, for example, information including only the meta information 310 of the ID-added document 300 and not including the document content 320 is transmitted to the transfer destination apparatus. In the item of transfer address, the address (URL or e-mail address, etc.) of the transfer destination device is set. When “Null” is set in the transfer address field, the transfer process is not executed. In the example of FIG. 14, in which operation type the transfer process is executed (determination condition in step S20 in FIG. 7) is set, and a plurality of different modes for executing the transfer process are set. .

  According to the setting of the transfer information illustrated in FIG. 14, when the document management server 10 receives the ID-added document 300 whose operation type is “registration” or “update”, the ID-added document 300 is transferred to another document management server 10. A transfer process (transfer process by transfer information 1), a transfer process (transfer process by transfer information 2) for transmitting an email including the meta information 310 of the received ID-added document 300 to the SMTP email server, and Two types of transfer processing are performed. In the transfer process using the transfer information 1, the ID-added document 300 including the document content 320 is transmitted to the transfer destination. In the transfer process using the transfer information 2, the document content 320 of the ID-added document 300 is not transmitted to the transfer destination. For the ID-added document 300 whose operation type is “print” or “browse”, the transfer process using either the transfer information 1 or the transfer information 2 is not executed.

  FIG. 15 shows an example of transfer information set for each ID-added document when the transfer information is initialized as exemplified in FIG. FIG. 15 is also an example of data contents registered in the derivation relationship DB 110. FIG. 16 shows a tree structure formed by the data contents of the derivation relation DB 110 shown in FIG.

  Referring to FIG. 15, the record corresponding to each management ID includes items of parent ID, operation type, operator, file name, transfer information 1 and transfer information 2. The parent ID, operation type, operator, and file name items are the same as in the example of FIG. The transfer information 1 and the transfer information 2 in the table of FIG. 15 correspond to the default transfer information 1 and the transfer information 2 in the example of FIG. 14, respectively. In the table of FIG. 15, the transfer information 1 and the transfer information 2 include transfer destination control and transfer address as subordinate items, respectively. In the transfer destination control item, an operator indicating how to generate transfer destination information using the value of the transfer address item and the transfer address value of the corresponding initial transfer information Is registered.

  For example, referring to the record of the management ID “Doc4” in the table of FIG. 15, the value of the transfer destination control item of the transfer information 1 is “new”, and the value of the transfer address item is “Null”. The transfer destination control operator “new” uses only the transfer address included in the transfer information set for the ID-added document without using the transfer address of the corresponding initial transfer information. Represents generating information. Therefore, the transfer information 1 of the management ID “Doc4” is not used for the transfer ID “http://fs1.fujixerox.co.jp/text” of the default transfer information 1 and the management ID “Doc4”. This means that the transfer destination information is generated using the transfer address “Null” included in the transfer information 1. Here, the transfer address “Null” indicates that the transfer process is not executed. Therefore, the transfer information 1 with the management ID “Doc4” is set so as not to execute the transfer process based on the transfer information 1, that is, the transfer process to the other document management server 10 is executed for the ID-added document “Doc4”. Represents the setting to avoid. Further, in the record of the management ID “Doc4” in the table of FIG. 15, the value of the transfer destination control item of the transfer information 2 is “new”, and the value of the transfer address is “foo@fujixerox.co.jp”. It is. Therefore, the transfer information 2 of the management ID “Doc4” is changed to the transfer information 2 of the management ID “Doc4” without using the transfer address “editors@fujixerox.co.jp” of the default transfer information 2. This means that the transfer destination information is generated using only the included transfer address “foo@fujixerox.co.jp”. That is, for the ID-added document “Doc4”, in the transfer process using the transfer information 2, an e-mail is transmitted to “foo@fujixerox.co.jp”.

  Further, for example, referring to the record of the management ID “Doc5” in the table of FIG. 15, “add” is used for the transfer destination control item of the transfer information 2 and “bar@fujixerox.co.jp” is used for the transfer address item. "Is registered. The transfer destination control value “add” generates transfer destination information using the transfer address included in the transfer information set for the ID-added document in addition to the transfer address of the corresponding initial transfer information. Represents what to do. Therefore, the transfer information 2 with the management ID “Doc5” is included in the transfer information 2 with the management ID “Doc5” in addition to the transfer address “editors@fujixerox.co.jp” of the default transfer information 2. This means that transfer destination information is generated using the transfer address “bar@fujixerox.co.jp”. For example, “editors@fujixerox.co.jp, bar@fujixerox.co.jp” including both the above-mentioned transfer addresses is used as transfer destination information.

  The transfer destination control values described above are merely examples, and operators representing other control contents may be set as necessary. For example, an operator for deleting a part of the transfer address of the initial transfer information (for example, deleting some of a plurality of mail addresses) can be set.

  Hereinafter, when the default transfer information is set as shown in FIG. 14, the document management server 10 receives each ID-added document from the client terminal 20 in the example of the document history shown in FIGS. 15 and 16. A specific example of the processing performed by the transfer processing unit 150 will be described. In this example, the transfer processing unit 150 performs the same process as the process described above with reference to FIGS. 7 and 8 for each ID-added document. However, in the process of this example, in step S312 in the transfer information acquisition process of FIG. 8, the transfer destination determination unit 152 acquires the transfer information of the attention ID, and also acquires the initial transfer information. In the process of this example described below, route list information is not used in the generation of transfer destination information. Therefore, steps S302 and S306 relating to the generation of the route list may be omitted in the process of FIG.

  Further, in the process of this example, the transfer destination determination unit 152 determines whether the transfer destination information generation process (step S50 in FIG. 7) uses the acquired transfer address (in this case, the transfer process using the transfer information 1). Of the document management server 10) and the file name of the ID-added document to be processed are generated as transfer destination information. As for the transfer process using the transfer information 2, the acquired transfer address (here, the mail address) is used as transfer destination information as it is.

  FIG. 17 shows an example of transfer destination information generated by the transfer destination determination unit 152 for each ID-added document in the table of FIG.

  In the following description, the processing of the client terminal 20 that generates each ID-added document, and the document registration unit 130 of the document management server 10 registers the ID-added document received from the client terminal 20 in the document DB and the derivation relationship DB. Description of the processing to be performed is omitted. These processes for each ID-added document are the same as those described with reference to the document history shown in FIGS. 5 and 6 or the document history shown in FIGS. 10 and 11.

  Referring to FIG. 15, first, for the ID-added documents “Doc1” and “Doc2”, the operation types are “registration” and “update”, respectively, so that the transfer processing by the transfer processing unit 150 is executed (FIG. 15). 7 YES in step S20). Since no transfer information is set for the ID-added documents “Doc1” and “Doc2”, the process advances from step S314 to step S318 in FIG. 8 to obtain the default transfer information (see FIG. 14). Using this, transfer destination information is generated (step S40 in FIG. 7). In the case of the ID-added document “Doc1”, the transfer address “http://fs1.fujixerox.co.jp/text” of the default transfer information 1 and the ID-added document “Doc1” are related to the transfer process using the transfer information 1. The transfer destination information “http://fs1.fujixerox.co.jp/text/class1_v1.doc” is generated by combining with the file name “class1_v1.doc” (see FIG. 17). The ID-added document “Doc1” including the document content is transferred to the address represented by the transfer destination information. Regarding the transfer processing by the transfer information 2, the transfer address “editors@fujixerox.co.jp” of the transfer information 2 of the initial setting is set as transfer destination information (see FIG. 17), and the ID-added document “Doc1” is addressed to this address. An email containing "meta information" is sent. The user who receives this e-mail performs, for example, the fact that the ID-added document “Doc1” is registered in the document management server 10 by referring to the meta information included in the e-mail, the registration date and time, and the registration operation. Information about the operation of the ID-added document “Doc1” such as the operator and the file name can be obtained.

  In the case of ID-added document "Doc2" as well as "Doc1", transfer processing using transfer information 1 (transfer destination information is "http://fs1.fujixerox.co.jp/text/class1_v2.doc )) And transfer processing by the transfer information 2 (transfer destination information is “editors@fujixerox.co.jp”).

  When the document management server 10 receives the ID-added document “Doc3”, since the operation type is “print”, the process proceeds to NO in step S20 of FIG. 7 and the transfer process is not executed. Therefore, transfer destination information is not generated (see FIG. 17).

  Since all the ID-added documents “Doc4” to “Doc7” have the operation type “update”, when the document management server 10 receives the respective ID-added documents “Doc4” to “Doc7”, the transfer processing unit 150 transfers them. The process is executed (YES in step S20 in FIG. 7).

  Referring to FIG. 15, the ID-added document “Doc4” includes transfer information in its log information 316. For the transfer information 1, the transfer destination control is set to "new" and the transfer address is set to "Null". For the transfer information 2, the transfer destination control is "new", and the transfer address is "foo@fujixerox.co. jp ". Therefore, in the transfer information acquisition process of the transfer destination determination unit 152 for processing the ID-added document “Doc4”, the transfer information set in the ID-added document “Doc4” and the initial setting in step S312 of FIG. The transfer information is acquired. Then, in the transfer destination information generation process (step S40 in FIG. 7), as described above, the transfer information 1 is transferred according to the transfer destination control value “new” of the transfer information 1 and 2 of the ID-added document “Doc4”. For the transfer address “Null” and the transfer information 2, transfer destination information is generated as the transfer address “foo@fujixerox.co.jp”. The document information transfer unit 154 does not perform the transfer process using the transfer information 1 but performs the transfer process using the transfer information 2 as the meta information 310 of the ID-added document “Doc4” addressed to the address “foo@fujixerox.co.jp”. Is sent (step S50 in FIG. 7).

  Next, when the document management server 10 receives the ID-added document “Doc5”, the transfer destination control is set to “add” for the transfer information 2 in the log information 316 of the ID-added document “Doc5”. Contains transfer information with the address set to “bar@fujixerox.co.jp”. Therefore, as a result of the transfer information acquisition process (FIG. 8) of the transfer destination determination unit 152 that processes the ID-added document “Doc5”, transfer information and initial transfer information of the ID-added document “Doc5” are acquired. Is done. Since the transfer information 1 is not set in the transfer information of the ID-added document “Doc5”, in the transfer destination information generation process (step S40 in FIG. 7), the transfer process using the transfer information 1 is initialized. Transfer destination information is generated using the transfer address of the transfer information 1 and the file name of the ID-added document “Doc5” (see FIG. 17). Further, regarding the transfer processing by the transfer information 2, as described above, the transfer address of the initial transfer information 2 and the ID-added document "according to the setting contents of the transfer information 2 of the ID-added document" Doc5 " Transfer destination information “editors@fujixerox.co.jp, bar@fujixerox.co.jp” including both the transfer address of the transfer information 2 of Doc5 ”is generated (see FIG. 17). As a transfer process based on the transfer information 1, the document information transfer unit 154 transfers the ID-added document “Doc5” to the address indicated by the transfer destination information “http://fs1.fujixerox.co.jp/text/class1_v3.doc”. As a transfer process based on the transfer information 2, the meta-data of the document “Doc5” with ID addressed to the two e-mail addresses indicated by the transfer destination information “editors@fujixerox.co.jp, bar@fujixerox.co.jp” An e-mail containing information 310 is sent.

  Since the transfer information is not set for the ID-added document “Doc6” (see FIG. 15), as a result of the transfer information acquisition process (FIG. 8) in the transfer processing unit 150, the ID-added document “Doc6” is the parent. Transfer information set for an ID-added document “Doc4” and initial transfer information are acquired. In the transfer destination information generation process (step S40 in FIG. 7) and the document information transfer process (step S50 in FIG. 7), transfer destination information similar to the transfer destination information for the ID-added document “Doc4” is generated and generated. Transfer processing is performed according to the transferred destination information. That is, the transfer process by the transfer information 1 is not executed, and as the transfer process by the transfer information 2, the address of the transfer destination information “foo@fujixerox.co.jp” (the transfer information 2 of the ID-added document “Doc4” is stored). An e-mail including the meta information 310 of the ID-added document “Doc6” is transmitted to the transfer address.

  Since the transfer information is not set for the ID-added document “Doc7” (see FIG. 15), the result of the transfer information acquisition process (FIG. 8) of the transfer processing unit 150 is the parent of the ID-added document “Doc7”. The transfer information set for the ID-added document “Doc5” and the default transfer information are acquired. In the transfer destination information generation process (step S40 in FIG. 7) and the document information transfer process (step S50 in FIG. 7), the same process as the process for the ID-added document “Doc5” is performed. In other words, in the transfer process using the transfer information 1, the transfer destination information “http://fs1.fujixerox” is a combination of the transfer address of the default transfer information 1 and the file name of the ID-added document “Doc7” to be processed. ID-added document “Doc7” is sent to the address of “.co.jp / text / class 1_v4.doc”. In the transfer process using the transfer information 2, the transfer destination information “editors@fujixerox.co.jp” including the transfer address of the transfer information 2 of the initial setting and the transfer address of the transfer information 2 of the ID-added document “Doc5” is used. , bar@fujixerox.co.jp ", an e-mail including meta information 310 of the ID-added document" Doc7 "is transmitted to two e-mail addresses.

  For the ID-added document “Doc8”, since the operation type is “browse”, the process proceeds to NO in step S20 in FIG. 7, the transfer process is not executed, and transfer destination information is not generated (see FIG. 17). .

  In the above description with reference to FIGS. 14 to 17, two types of the document management server 10 and the electronic mail server have been described as examples of transfer destination types. As another example of the transfer destination type, transfer to a FAX server that manages FAX transmission / reception may be set. In this case, for example, the FAX server address and the FAX transmission destination FAX number are set in the corresponding transfer information item. At this time, if the value of the document sending item is set to “yes”, a document including the document content of the ID-added document 300 is faxed by the fax server, and if the value of the document sending item is set to “no”. A document including only the meta information of the ID-added document 300 and not including the document content is transmitted by FAX. In addition, an item for setting the mode of FAX transmission may be further provided in the subordinate items of the transfer information. For example, items for setting the presence / absence of a cover sheet and the type of cover sheet in FAX transmission can be provided.

  In the above-described example, two modes of transfer processing are executed for one ID-added document, but the initial setting is performed so that three or more modes of transfer processing are executed for one ID-added document as necessary. Transfer information and transfer information for each ID-added document may be set. For example, it can be set to execute transfer processing for three types of transfer destinations, that is, the document management server 10, the e-mail server, and the FAX server.

  Further, for example, even if the transfer destination type is the same, it may be set to execute a plurality of modes of transfer processing in which at least one of the values of the document sending item and the transfer address item is different.

  In the example illustrated above, the management ID is issued at each client terminal 20, but the document management server 10 may issue the management ID instead. In this case, when an operation is performed on the ID-added document, the client terminal 20 includes the management ID in the ID-added document before the operation as the parent ID 314, and further includes log information 316 about the operation and the document content after the operation. 320, the management ID 312 generates blank document data and sends it to the document management server 10. The document management server 10 assigns a new management ID to the received document data, and registers information included in the management ID and the document data in the document DB 100 and the derivation relationship DB 110. In addition, the document management server 10 generates an ID-added document by setting the assigned management ID in the document data, and returns it to the client terminal 20. The client terminal 20 replaces the ID-added document before the operation with the received ID-added document. As described above, even in the configuration in which the document management server 10 assigns the management ID, the processing of each example described above can be executed in the same manner.

  In the above example, the ID-added document 300 including the management ID 312, the parent ID 314, the log information 316, and the document content 320 is stored in the client terminal 20. Instead, the client terminal 20 has only the management ID. Other information may be stored in the document management server 10. In this case, when a document is operated on the client terminal 20, a management ID corresponding to the document is sent to the document management server 10, and the document is acquired from the document management server 10. As another example, the ID-added document 300 held by the client terminal 20 may include the management ID 312 and the document content 320, and may not include the parent ID 314 and the log information 316. In this case, the server may have a parent ID 314 and log information 316 in association with the management ID 312.

  When the document management server 10 assigns a management ID, the document management server 10 generates a management ID corresponding to the acquisition operation, and provides the management ID and the document to the client terminal 20 in association with each other. At the same time, log information (operation time, operator, etc.) about the acquisition operation, the original management ID (ie, parent ID), and the assigned management ID are recorded in the derivation relationship DB 110. The client terminal 20 replaces the management ID transmitted to the document management server 10 with the received management ID and opens the received document. The user performs operations such as browsing and editing on the opened document. When the operation on the document is completed, the client terminal 20 sends the document after the operation to the document management server 10 together with the management ID and log information about the operation. The document management server 10 assigns a new management ID to the received document and registers it in the derivation relationship DB 110, and registers the received management ID as a parent ID in the derivation relationship DB 110. Also, the received log information and the document after the operation are registered in the derivation relationship DB 110 and the document DB 100. Then, the document management server 10 returns the newly assigned management ID to the client terminal 20. The client terminal 20 replaces the original management ID with the received management ID. Through the processing as described above, the derivation relationship between operations is accumulated in the document management server 10.

  On the other hand, when the client terminal 20 is configured to give a management ID, the document management server 10 may return a document corresponding to the management ID received from the client terminal 20 to the client. The client terminal 20 opens the received document, and the user operates the document. After the operation is completed, the client terminal 20 assigns a new management ID to the operation result document, and sends the same information as the above-mentioned ID-added document including the management ID to the document management server 10. And the client terminal 20 preserve | saves only management ID among the documents with the ID, and deletes other information.

  The document management server 10 in the system exemplified above is typically realized by executing a program describing functions or processing contents of each unit of the document management server described above on a general-purpose computer. As shown in FIG. 18, for example, the computer has a CPU (central processing unit) 40, a memory (primary storage) 42, various I / O (input / output) interfaces 44, and the like connected via a bus 46. Circuit configuration. Also, a disk drive 50 for reading various types of portable non-volatile recording media such as a hard disk drive (HDD) 48, a CD, a DVD, a flash memory, etc. via the I / O interface 44, for example. Connected. Such a drive 48 or 50 functions as an external storage device for the memory. A program in which the processing contents of the embodiment are described is stored in a fixed storage device such as the hard disk drive 48 via a recording medium such as a CD or DVD or via a network, and is installed in a computer. The program stored in the fixed storage device is read into the memory and executed by the CPU, whereby the processing of the embodiment is realized. The same applies to the client terminal 20.

It is a block diagram which shows the example of schematic structure of a document utilization management system. It is a block diagram which shows the example of an internal structure of a client terminal. It is a figure which shows typically the example of the data structure of a document with ID. It is a block diagram which shows the example of an internal structure of a document management server. It is a figure which shows the example of the data content of derivation relation DB. FIG. 6 is a diagram schematically illustrating a tree structure formed by a management ID group in the data content illustrated in FIG. 5. It is a flowchart which shows an example of the process sequence of a transfer process part. It is a flowchart which shows an example of the partial process sequence of a transfer process part. It is a figure which shows the example of the transfer destination information which a transfer destination determination part produces | generates. It is a figure which shows the example of the data content of derivation relation DB in a modification. FIG. 11 is a diagram schematically illustrating a tree structure formed by a management ID group in the data content illustrated in FIG. 10. It is a figure which shows the example of the transfer destination information generation rule which a transfer process part uses. It is a flowchart which shows another example of the process sequence of a transfer process part. It is a figure which shows the example of the information for transfer set corresponding to each operation classification. It is a figure which shows the example of the data content of derivation relation DB in a modification. FIG. 16 is a diagram schematically illustrating a tree structure formed by a management ID group in the data content illustrated in FIG. 15. It is a figure which shows the other example of the transfer destination information which a transfer destination determination part produces | generates. It is a figure which shows an example of the hardware constitutions of a computer.

Explanation of symbols

  10 document management server, 20 client terminal, 30 network, 44 interface, 46 bus, 48 HDD, 50 disk drive, 100 document DB, 110 derivation relationship DB, 130 document registration unit, 132 derivation relationship registration unit, 140 request processing unit, 150 transfer processing unit, 152 transfer destination determination unit, 154 document information transfer unit, 200 document operation unit, 202 ID allocation unit, 204 derivative relation incorporation unit, 210 registration processing unit, 220 transfer information setting unit, 300 ID-added document 310 Meta information, 320 Document content.

Claims (8)

A registration unit that receives history information including a second document generated as a result of an operation on the first document and the type of the operation from the information processing apparatus and registers the history information in a storage unit, wherein the second document A registration unit for further registering in the storage unit a derivation relationship indicating that the parent of the first document is the first document;
When the registration unit receives the history information including a predetermined operation type from the information processing apparatus, the reception unit uses the received history information and at least a part of the history information group stored in the storage unit. A determination unit that determines a transfer destination to which at least a part of the recorded history information is transferred;
With
The history information may further include transfer information that is information used for determining the transfer destination and includes information indicating a device designated as the transfer destination device.
The determination unit includes a history information group corresponding to a document group corresponding to an ancestor of a document in the received history information in a tree structure represented by the received history information and a derivation relationship group stored in the storage unit, A document management apparatus, wherein when there is history information including the transfer information, the transfer destination is determined based on the transfer information included in any of the history information.   The determination unit includes the received history among documents included in a path that goes back the tree structure starting from the document in the received history information and includes the transfer information in the corresponding history information. The document management apparatus according to claim 1, wherein the transfer destination is determined based on the transfer information in history information corresponding to a document in the information and the closest document on the path. The transfer information further includes information specifying the type of operation that should be included in the history information to be processed by the determination unit,
The determination unit includes the received history among documents included in a path that goes back the tree structure starting from the document in the received history information and includes the transfer information in the corresponding history information. The received history when the type of operation specified in the transfer information in the history information corresponding to the document in the information and the closest document on the route includes the type of operation in the received history information The document management apparatus according to claim 1, wherein the transfer destination is determined for information. The transfer information further includes information specifying the type of operation that should be included in the history information to be processed by the determination unit,
In the history information group corresponding to the document group corresponding to the ancestor of the document in the received history information in the received history information and the received history information in the tree structure, there is history information including the transfer information. If the type of operation specified in the transfer information included in any of the history information includes the type of operation in the received history information, the transfer destination for the received history information The document management apparatus according to claim 1, wherein: The transfer information is information that associates the type of operation that should be included in the history information to be processed by the determination unit and the rules used when determining the transfer destination for the history information that includes the type of operation. Further including
5. The document according to claim 3, wherein the determination unit determines the transfer destination according to the rule associated with the type of operation in the received history information in the transfer information. Management device. The transfer information further includes information for determining a plurality of different transfer destinations for one history information,
The determination unit determines a plurality of different transfer destinations for the received history information,
The document management apparatus according to claim 1, wherein at least a part of the received history information is transferred to each of the plurality of different transfer destinations determined by the determination unit. A step of receiving history information including a second document generated as a result of an operation on the first document and the type of the operation from the information processing apparatus and registering the history information in a storage unit; A registration step of further registering in the storage unit a derivation relationship indicating that the parent is the first document;
When the history information including a predetermined operation type is received from the information processing apparatus in the registration step, the received history information and at least a part of the history information group stored in the storage unit are used to receive the history information. A determination step for determining a transfer destination to which at least a part of the recorded history information is transferred;
To the computer,
The history information may further include transfer information that is information used for determining the transfer destination device and includes information indicating a device designated as the transfer destination device.
In the determination step, among the history information group corresponding to the document group corresponding to the ancestor of the document in the received history information in the tree structure represented by the received history information and the derivation relation group stored in the storage unit, When there is history information including the transfer information, the transfer destination is determined based on the transfer information included in any of the history information;
A program characterized by that. An information processing device and a document management device;
The information processing apparatus includes:
A transmission unit configured to transmit history information including a second document generated as a result of an operation on the first document and the type of the operation to the document management device;
Setting of transfer information including transfer information for determining a transfer destination to which information related to the second document is transferred from the document management apparatus, and representing information indicating the apparatus designated as the transfer destination apparatus A reception part for receiving,
With
The transmission unit transmits the history information further including the received transfer information to the document management apparatus when the reception unit receives the setting of the transfer information,
The document management apparatus includes:
A registration unit that receives the history information from the information processing apparatus and registers the history information in the storage unit, and further registers a derivation relationship indicating that a parent of the second document is the first document in the storage unit. A registration department;
When the registration unit receives the history information including a predetermined operation type from the information processing apparatus, the received history information and at least a part of the history information group stored in the storage unit are used. A determination unit for determining a transfer destination to which at least a part of the received history information is transferred, wherein the received history information and a tree structure represented by a derivation relation group stored in the storage unit When there is history information including the transfer information among history information groups corresponding to a document group corresponding to an ancestor of the document, the transfer destination is based on the transfer information included in any of the history information. A determination unit for determining
Comprising
A document management system characterized by that.

Images