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

Description

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

  An electronic document (hereinafter simply referred to as a document) such as text document data, audio data, and multimedia data is registered in a server, and the document is provided in response to a user request. There is also known a system that provides a unique identifier to an electronic document and provides the electronic document corresponding to the identifier input by the user.

  In addition, there is a system that records information representing an operation history for a document and provides information related to the operation history. For example, in the system described in Patent Document 1, when a user performs an operation on a document to which an operation ID (identifier) is assigned, a new operation ID is assigned to the document as a result of the operation. A derivation relationship in which the operation ID of the document is a parent and a new operation ID assigned to the operation result document is a child is recorded. Further, attribute information relating to the operation performed on the document is recorded in association with the derivation relationship. In addition, when the system described in Patent Document 1 receives a request to browse a document with an operation ID specified from the user, the information of the document with the operation ID included on the route that traces the derivation relationship starting from the specified operation ID. To the user.

JP 2008-3846 A

  In a document management system that records the history of operations on a document, if a search result document is provided in response to a request to search for a document that satisfies a specific search condition, the search is executed using the search condition. However, the fact that the document is provided as a search result is not recorded with respect to the document provided as the search result.

  It is an object of the present invention to provide a document management apparatus, a document management system, and a document management program that record that a document provided as a search result in response to a search request records the document as a search result. And

According to the first aspect of the present invention, information on a derivation relationship whose parent is the first document and whose child is the second document generated as a result of the operation on the first document is received from the information processing apparatus and registered in the storage unit. A registration unit, and a tree structure represented by a derivation relation group registered in the storage unit in response to a use request specifying a designated document and a search condition, and among the documents included in the tree structure to which the designated document belongs A document that satisfies a search condition as an output target document, and an output unit that outputs information about the output target document. The registration unit further includes the output target document as a parent, and the output unit includes the output target document. It registers information of derivation relationship to the child an output result document is information document output the result in the storage unit regarding receives information indicating the type of the operation to the first document from the information processing apparatus, When the operation type is a predetermined type, and when the operation type is other than the predetermined type and the forced registration instruction attached to the second document is detected by the information processing apparatus, Derivation relationship information is registered in the storage unit, and when the operation type is other than the predetermined type and the forced registration instruction is not detected, the derivation relationship information is not registered in the storage unit. This is a featured document management apparatus.

The invention according to claim 2 is the invention according to claim 1 or 2, wherein the output unit includes a document having the output result document as a child, and other documents among the output target documents satisfying the search condition. Display information to be displayed on the display device in different manners.

According to a third aspect of the present invention, information on a derivation relationship having a first document as a parent and a second document generated as a result of an operation on the first document as a child is received from the information processing apparatus and registered in the storage unit. And the search among documents included in the tree structure to which the designated document belongs, which is a tree structure represented by the derivation relation group registered in the storage unit in response to a use request for specifying the designated document and the search condition A document that satisfies the conditions is set as an output target document, and the output result is a document that is output as a result of outputting information about the output target document, and the output unit outputs information about the output target document. It registers information of derivation relationship that a child document in the storage unit, the information indicating the type of the operation on the first document receiving from the information processing apparatus, the type of the operation is predetermined type In some cases, and when the operation type is other than the predetermined type and the forced registration instruction attached to the second document is detected by the information processing apparatus, the derivation relationship information is stored in the storage unit. Registering, and if the operation type is other than the predetermined type and the forced registration instruction is not detected , causing the computer to execute a step of not registering the information on the derivation relationship in the storage unit. Document management program.

The invention according to claim 4 includes an information processing apparatus and a document management apparatus, and the information processing apparatus uses a first document as a parent and a second document generated as a result of an operation on the first document as a child. A transmission unit that transmits derivation relationship information to the document management device, and a request unit that requests the document management device to specify a specified document and a search condition, and the document management device includes: A registration unit that receives information on the derivation relationship from the information processing apparatus and registers the information in a storage unit; and a tree structure represented by a derivation relationship group registered in the storage unit in response to the use request from the information processing device. An output unit that outputs a document that satisfies the search condition among documents included in the tree structure to which the designated document belongs, and that outputs information related to the output target document, and the registration unit further includes: Output pair The document a parent registers the information of the derivation relationship that the output unit is a child the output result document is a document of the result of outputting information on the output target document in the storage unit, the operation for the first document Information indicating the type of the operation is received from the information processing apparatus, and the operation type is a predetermined type, and the operation type is other than the predetermined type, and the information processing apparatus converts the information into the second document. If the attached forced registration instruction is detected, the derivation relationship information is registered in the storage unit, and if the operation type is other than the predetermined type and the forced registration instruction is not detected, the derivation relationship information is registered. It is a document management system characterized by not registering related information in the storage unit .

According to the invention according to claim 1, 3 , or 4 , with respect to a document to be output in response to a use request for the document, the fact that the document has been output is recorded , and all that is performed on the document Compared with the case of recording the derivation relationship of the document caused by this kind of operation, it is possible to record the derivation relationship of the document caused by the operation of the type that needs to be recorded for management purposes, using a small storage area .

According to the invention according to claim 2 , with respect to a document that is an output target in response to a use request for the document, a document that has been an output target before and other documents can be presented to the user in different modes. it can.

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

  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 shown in FIG. 2, the client terminal 20 includes a document operation unit 200, a registration processing unit 210, and a forced registration instruction receiving 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 the figure, each of these operations may be handled 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.

  The forced registration instruction receiving unit 220 receives an instruction to force the document management server 10 to register the specific ID-added document 300 (hereinafter also referred to as “forced registration instruction”). As will be described later, the document management server 10 may restrict registration in the document management server 10 according to the operation type included in the log information 316 of the ID-added document 300. When the forced registration instruction receiving unit 220 receives the forced registration instruction, the forced registration instruction receiving unit 220 transmits the instruction to the document management server 10 via the registration processing unit 210. Upon receiving this instruction, the document management server 10 registers the instructed ID-added document 300 regardless of the restriction on the operation type to be registered.

  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 an operation type limitation 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 contents in the ID-added document received from the client terminal 20 in the document DB 100 and the meta information in the derivation relationship DB 110. Among them, the derivation relationship registration unit 132 is in charge of registration of meta information.

  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, the items of parent ID, operation type, operator, operation date and time are registered in association with the management ID of each ID-added document 300. Of these, items other than the management ID and parent ID pair are not limited to those illustrated. Items that are necessary for management purposes may be recorded. The operation type, the operator, and the operation date / time have already been described.

  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.

  The document history shown in the examples of FIGS. 5 to 6 will be described below in chronological order. 5 to 6 show a document in which a certain user registers a form document of a specific format (for example, a questionnaire form, various application forms, etc.), and other users fill in the form document. An example of a document history when registering a document is shown.

  First, a “new registration” operation of a document (form document) is executed on the client terminal of userA. The “new registration” operation is an operation for registering a document not registered in the document management server 10 (that is, a document having no management ID) in the server 10. In response to this operation, the ID-added document “Doc1” including the meta information having the management ID “Doc1”, the parent ID is empty, and the operation type is “new registration” and the document content of the document is received from the client terminal of userA. It is sent to the document management server 10. 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, userC, and userD. This distribution can be performed, for example, by attaching the ID-added document to an e-mail and transmitting it to each user.

  Thereafter, another user userB edits (adds to the form) the ID-added document “Doc1” in the document operation unit 200 of his / her client terminal, and displays “response (registered as completed document)” on the operation menu. Instruct. The client terminal 20 generates an ID-added document “Doc2” as a result of the “response” operation, and the ID-added document “Doc2” is registered in the document management server 10. The management ID in the meta information of the ID-added document is “Doc2” and the parent ID is “Doc1”. The operator is userB and the operation type is “response”. Further, by editing the ID-added document “Doc1”, the document content 320 is changed from “Content1” to “Content2”. The document management server 10 recognizes that the document “Doc2” is a child of the document “Doc1” from the value of the parent ID of the received ID-added document.

  It should be noted that the ID-added document “Doc1” that was in the client terminal 20 of userB before this operation is replaced with the ID-added document “Doc2” by the derivation relationship incorporating unit 204 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 “response” which is the type of the current operation, changes the value of the operation time to the date and time of the response, and Change the value to userB. Further, the document content 320 is changed to “Content2”.

  When the operation for the ID-added document “Doc1” is executed in this way, the ID-added document “Doc1” 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, when userC edits the ID-added document “Doc1” by the document operation unit 200 of his / her client terminal 20 and instructs “response” on the operation menu, the client terminal 20 indicates that the value of the management ID 312 is “ An ID-added document “Doc3” having a value “Doc3”, a parent ID 314 value “Doc1”, and an operation type value “response” is generated. The client terminal 20 replaces the generated ID-added document “Doc3” with the ID-added document “Doc1” before the “response” operation, and registers the ID-added document “Doc3” in the document management server 10. As a result of the editing, the document content has changed from “Content1” to “Content3”. A record with the management ID “Doc3” is registered in the derivation relationship DB 110 of the document management server 10.

  After that, userA designates the ID-added document “Doc1” and makes a use request for presenting the ID-added document registered as a result of the “response” operation for the designated document “Doc1” to the document management server 10. . Through the processing in response to this request, the document management server 10 returns the ID-added documents “Doc2” and “Doc3” generated by the “response” operation to the ID-added document “Doc1” to the client terminal 20 of userA. That is, the ID-added documents “Doc2” and “Doc3” are downloaded to the client terminal 20. Details of a series of processing performed by the document management server 10 in response to the use request specifying the designated document will be described later. The document operation unit 200 of the client terminal 20 generates a new ID-added document corresponding to the result of the download operation for the ID-added documents “Doc2” and “Doc3”. For example, new management IDs “Doc4” and “Doc5” are assigned to the documents obtained as a result of downloading “Doc2” and “Doc3” with IDs. Then, the management ID values in the meta information of the ID-added documents “Doc2” and “Doc3” downloaded to the client terminal 20 are replaced with “Doc4” and “Doc5”, respectively, and the parent ID values are changed. Replace with "Doc2" and "Doc3". Also, the value of the operation type is replaced with “collected”, and the value of the operator is replaced with “userA”. In addition, the value of the operation date is replaced with the time when each of the ID-added documents “Doc2” and “Doc3” is downloaded. The document contents 320 of the ID-added documents “Doc4” and “Doc5” are not changed from the document contents “Content2” and “Content3” of the downloaded ID-added documents “Doc2” and “Doc3”. The registration processing unit 210 of the client terminal 20 transmits the ID-added documents “Doc4” and “Doc5” generated by the document operation unit 200 to the document management server 10. At this time, since the document contents of the ID-added documents “Doc4” and “Doc5” are the same as the parent documents “Doc2” and “Doc3”, the client terminal 20 has the ID-added document “Doc4” with the document contents omitted. , “Doc5” may be transmitted to the document management server 10. Records of management IDs “Doc4” and “Doc5” are registered in the derivation relationship DB 110 of the document management server 10.

  Furthermore, userD performs a “response” operation on the ID-added document “Doc1”, an ID whose management ID value is “Doc6”, the parent ID 314 value is “Doc1”, and the operation type value is “response”. A record corresponding to the attached document “Doc6” is registered in the derivation relationship DB 110 of the document management server 10. In the client terminal 20 of userD, the ID-added document “Doc1” before the “response” operation is replaced with the ID-added document “Doc6”. Further, the document content is changed from “Content1” to “Content4” by the editing accompanying the “response” operation.

  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. Accompanying this service, the request processing unit 140 may accept selection of an ID-added document desired by the user from the list, and provide the selected ID-added document. The service for searching for the latest version described above can also be regarded as a service for providing a search result for a search condition “the operation date is the latest”. In addition, the service that provides information on the original document described above can be regarded as a service that provides a search result for the condition “document corresponding to the root of the tree structure”. As another example, a display screen having a tree structure representing a derivation relationship of an ID-added document group based on the derivation relationship DB 110 is provided, and selection of a document with an ID desired by the user is accepted and selected on the display screen. Some services provide ID-added documents.

  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.

  In the example of the document history described with reference to FIGS. 5 and 6, the use request for designating the ID-added document “Doc1” and presenting the ID-added document as a result of the “response” operation for the designated document is as follows: It is an example of a service request. As described above, records with management IDs “Doc4” and “Doc5” respectively corresponding to operations in which the documents “Doc2” and “Doc3” with IDs are downloaded from the document management server 10 to the client terminal 20 as a result of the use request. Is registered in the derivation relationship DB 110.

  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 operation type restriction unit 150 restricts the operation type of the document that the document registration unit 130 registers in the derivation relationship DB 110. The operation type limiting unit 150 notifies the document registration unit 130 of information specifying the operation type of the document to be registered in the derivation relationship DB 110. When the document registration unit 130 receives an ID-added document from the client terminal 20 and the operation type of the ID-added document is included in the operation type notified from the operation type restriction unit 150 as a registration target, the document registration unit 130 Records corresponding to attached documents are registered in the derivation relationship DB 110. If the operation type of the ID-added document received from the client terminal 20 is not included in the operation type notified as the registration target from the operation type limiting unit 150, the document registration unit 130 derives a record corresponding to the ID-added document. It is not registered in the relation DB 110. The operation type limiting unit 150 may notify the document registration unit 130 that the operation type to be registered is not limited. When the operation type is not limited, the document registration unit 130 registers corresponding records in the derivation relationship DB 110 for all the ID-added documents received from the client terminal 20 without confirming the operation type. The example of the process of the document registration unit 130 described above with reference to FIGS. 5 and 6 is an example of the process when the operation type is not limited.

  Hereinafter, an example of the processing procedure of the request processing unit 140 when a service request including the management ID of the designated document is received from the client terminal 20 will be described with reference to FIGS. In the following, an example will be described in which a service request for requesting to provide a document obtained as a result of searching using “a document whose operation type is“ response ”among the documents corresponding to the descendants of the specified document” as a search condition is described. To do. In the service request for specifying the search condition, for example, a specific ID-added document is specified in the client terminal 20, and the user instructs execution of the “display response document list” command on the operation menu of the document operation unit 200. In this case, the data is transmitted from the client terminal 20 to the document management server 10.

  Referring to FIG. 7, first, the request processing unit 140 extracts the management ID of the designated document from the service request (search request) received from the client terminal 20, and sets the management ID to the attention ID (step S1). Next, the request processing unit 140 refers to the derivation relationship DB 110 and searches for a child ID of the attention ID (step S2). “Management ID” of a record having the attention ID as the value of “parent ID” in the derivation relationship DB 110 is a child ID of the attention ID. Then, it is determined whether or not there is a child ID of the attention ID (step S3). When the child ID of the attention ID does not exist (NO in step S3), the request processing unit 140 returns information indicating “no search result” to the client terminal 20 as a result of the service execution (step S7). If there is a child ID of the attention ID (YES in step S3), the request processing unit 140 executes a descendant search process illustrated in FIG. 8 for each child ID.

  When the descendant search process in step S4 is started, the process of the procedure in the example of FIG. 8 is started. First, the request processing unit 140 sets the child ID as the attention ID (step S11). Next, the request processing unit 140 acquires a record corresponding to the attention ID from the derivation relationship DB 110 (step S12), and puts the acquired record in the intermediate result list (step S13). The intermediate result list is a list constructed in order to accumulate information as material for obtaining a processing result of a requested process.

  Thereafter, the request processing unit 140 searches for the child ID of the attention ID (step S14), and determines whether the child ID has been searched (step S15). If there is a child ID (YES in step S15), the request processing unit 140 recursively executes a descendant search process (step S4) for each of the child IDs. When the descendant search process for all the child IDs ends, the process for the attention ID ends. Even when it is determined in step S15 that there is no child ID, the process for the attention ID is ended.

  Referring to FIG. 7 again, when the descendant search process in step S4 is completed for all child IDs of the target ID, records corresponding to documents derived from the document corresponding to the target ID are accumulated in the intermediate result list. It will be. For example, referring to FIG. 5, when records of management IDs “Doc1”, “Doc2”, and “Doc3” are registered in the derivation relationship DB 110 and the attention ID is “Doc1”, the intermediate result list includes Records of management IDs “Doc2” and “Doc3” are accumulated. Next, the request processing unit 140 determines whether there is a record that satisfies the search condition from the intermediate result list (step S5). For example, when the condition that “the operation type is“ response ”” is set as the search condition, the records with the management IDs “Doc2” and “Doc3” (all the operation types are “response”) in the intermediate result list. If accumulated, it is determined that a record satisfying the search condition exists in the intermediate result list. If there is a record that satisfies the search condition in the intermediate result list (YES in step S5), the request processing unit 140 provides information about the document corresponding to the record that satisfies the search condition as a search result (step S6). Here, the request processing unit 140 may provide the content of the corresponding document, or may provide the content of a specific item in the record of the corresponding document. All the contents of the corresponding document record may be sent to the client terminal 20. If no record satisfying the search condition exists in the intermediate result list (NO in step S5), information indicating that no document satisfying the search condition is found is sent to the client terminal 20 (step S7).

  FIG. 9 shows a result of the request processing unit 140 of the document management server 10 performing the processing of the procedure of the example of FIGS. 7 and 8 in response to the search request from the client terminal 20, and as a result of step S6 of FIG. It is an example of the display screen displayed on a display apparatus. FIG. 9 shows that the ID-added document “Doc1” is searched as a designated document at the time when records with management IDs “Doc1” to “Doc3” are registered in the operation history described with reference to FIGS. 5 and 6. It is an example of a display screen when a request (search condition: a document whose operation type is “response” among documents corresponding to descendants of a specified document) is made. Referring to FIG. 9, for each of ID-added documents “Doc2” and “Doc3” that are children of ID-added document “Doc1” and whose operation type is “response”, the response date and time (operation date and time) and responder (operation Displayed). In FIG. 9, the management ID of each document is not shown, but the rows 60a and 60b in the table in the display screen of FIG. 9 correspond to ID-added documents “Doc2” and “Doc3”, respectively. On this display screen, userA uses an input device such as a mouse to check the check box (select a document) and press the “Download Checked Document” button (for example, “click” operation with the mouse, or The request processing unit 140 of the document management server 10 that has received the information indicating that the “return key” input operation of the keyboard after selecting the button) transmits the selected ID-added document to userA's It transmits to the client terminal 20. That is, the selected ID-added document is downloaded to the client terminal 20 of userA. The document operation unit 200 of the client terminal 20 generates a new ID-added document 300 as a result of the download operation, and the new ID-added document 300 is registered in the document management server 10.

  For example, on the display screen in the example of FIG. 9, when both the ID-added documents “Doc2” and “Doc3” are selected (check box is checked) and the “Download Checked Document” button is pressed, the ID-added document is displayed. “Doc2” and “Doc3” are downloaded from the document management server 10 to the client terminal 20. The document operation unit 200 of the client terminal 20 assigns new management IDs “Doc4” and “Doc5” to the document resulting from the download operation. Then, ID-added documents “Doc4” and “Doc5” whose parent IDs are “Doc2” and “Doc3” and whose operation type is “collection” are generated and registered in the document management server 10 by the registration processing unit 210. The Details of the processing in the client terminal 20 at this time have been described above with reference to FIGS. 5 and 6.

  FIG. 10 shows another example of the display screen displayed on the display device of the client terminal 20 in step S6 of FIG. FIG. 10 shows the ID-added document “Doc1” when the records of the ID-added documents “Doc1” to “Doc6” are registered in the derivation relation DB 110 in the document history described with reference to FIGS. 5 and 6. The request processing unit 140 receives the search request from the client terminal 20 as a designated document (search condition: a document whose operation type is “response” among the documents corresponding to the descendants of the designated document), and the request processing unit 140 is an example shown in FIGS. It is an example of a display screen displayed as a result of performing the process. In the table in the display screen of the example of FIG. 10, rows 70a, 70b, and 70c correspond to ID-added documents “Doc2”, “Doc3”, and “Doc6” that satisfy the search conditions, respectively. In FIG. 10, among ID-added documents “Doc2”, “Doc3”, and “Doc6”, ID-added documents “Doc2” and “Doc3” that have a document whose operation type is “collection” as children, and the operation type is “ An ID-added document “Doc6” that does not have a document “collected” as a child is displayed in a different manner. Specifically, for ID-added documents “Doc2” and “Doc3” for which a “collection” operation has already been performed, a checkbox for selecting download is not displayed, and a “collection” operation is performed for each document. The “collection date” that is the date and time when the “recovery” is performed and the “collector” that is the operator are displayed. For an ID-added document “Doc6” for which “collection” operation has not yet been executed, a check box for selecting download is displayed, and “collection date” and “collector” are not displayed.

  When the display screen as in the example of FIG. 10 is displayed on the client terminal 20, the request processing unit 140 performs, for example, the following procedure in step S6 of FIG. First, it is determined whether or not each search result document satisfying the search condition has a document whose operation type is “collection” as a child. This determination is performed by confirming the operation type of the record having the management ID of each document satisfying the search condition as the parent ID in the derivation relationship DB 110. Then, for a search result document having a document whose operation type is “collection” as a child, the operation date and time of the record corresponding to the child “collection” operation and the value of the operator are respectively displayed on the display screen of the client terminal 20. The “collection date” and “collector” values to be displayed are displayed. Thereafter, the request processing unit 140 hides the check box for selecting a download for a search result document having a document whose operation type is “collection” as a child, and sets “collection date” and “collector”. Display a search result document that does not have a document whose operation type is "collection" as a child, display a check box for selecting download, and indicate that "collection date" and "collector" are not displayed Display information to be transmitted is transmitted to the client terminal 20. According to the processing of the above example, when none of the search result documents has a child document whose operation type is “collection”, a display screen like the example of FIG. 9 is displayed on the display device of the client terminal 20 and the search is performed. When any of the result documents has a child document whose operation type is “collection”, a display screen as in the example of FIG. 10 is displayed on the display device of the client terminal 20.

  In the above, an example in which the search condition specified in the service request is “a document corresponding to a descendant of the designated document whose operation type is“ response ”” has been described. In another example, the search condition may be “a document that does not have a child document whose operation type is“ response ”and whose operation type is“ collection ”among documents corresponding to descendants of the designated document” ”. For example, in the document operation unit 200 of the client terminal 20, when the user selects the option “Do not display collected documents” on the operation menu instructing execution of the “display response document list” command, A service request designating the search condition in this example is transmitted to the document management server 10. When the search condition of this example is used, the request processing unit 140 of the document management server 10 has an operation type “response” in the record of the ID-added document in the intermediate result list in step S5 of FIG. In addition, a record in which the operation type is “collected” does not exist among records having the management ID of the record as a parent ID is determined as a record that satisfies the search condition. If the derivation relationship DB 110 has the data of the example of FIG. 5 and the request processing unit 140 performs the process of the example of FIGS. 7 and 8 according to the search condition of this example as the designated document “Doc1”, the ID Search results for information on the attached document "Doc6" (a document that corresponds to a descendant of the specified document "Doc1", has an operation type of "response", and has no child document with an operation type of "collection") Offered as.

  In the example described above, in response to a search request, first, a list of documents satisfying the search result is displayed, and a “collection” operation is performed on the document selected in the list. In another example, instead of accepting selection of a document that is a target of a “collection” operation from a list of documents that satisfy a search result, the document management server 10 includes document contents for all the documents that satisfy the search result. An ID-added document may be transmitted to the client terminal 20. In this example, when the client terminal 20 receives an ID-added document that satisfies the search result, the client terminal 20 generates a new ID-added document with the management ID of the received ID-added document as the parent ID and the operation type “collected”. The generated new ID-added document is registered in the document management server 10.

  In the example of the processing described above, the newly registered form document is entered, but the form document itself is not updated. In another example, the form document itself may be updated and registered in the document management server 10 (registration of a revised version of the form document). When the revised version of the form document is registered, the document management server 10 may manage the version of the form document.

  FIG. 11 shows an example of data contents of the derivation relationship DB 110 when the document management server 10 performs version management of ID-added documents. Referring to FIG. 11, in addition to the items illustrated in FIG. 5 (parent ID, operation type, operator, operation date / time) in association with each management ID, an item “document version” is registered. In the example of FIG. 11, the history of operations from the ID-added documents “Doc1” to “Doc6” is the same as the history described with reference to FIGS. When the derivation relationship registration unit 132 of the document management server 10 receives the ID-added document from the client terminal 20, the derivation relationship registration unit 132 confirms the operation type, and if it is “new registration”, the “document version” of the corresponding record in the derivation relationship DB 110. The value of the item “” is set to information indicating the first version (“ver1” in the example of FIG. 11). If the operation type of the ID-added document received from the client terminal 20 is “revision”, information indicating that the version is the next version of the version of the parent ID of the ID-added document is set as the document version. When the operation type is neither “new registration” nor “revision”, the same value as the document version value of the parent ID record is set as the document version.

  For example, referring to FIG. 11, after the record with the management ID “Doc6” is registered in the derivation relationship DB 110, the userA has his / her own client terminal 20 for the ID-added document “Doc1” which is a newly registered form document. When the document is edited using the document operation unit 200 and "Revision (registered as a revised version of the form document)" is instructed on the operation menu, a new ID-added document "Doc7" is generated and the document management server 10 is derived. Registered in the relationship DB 110. The ID-added document “Doc7” has a parent ID “Doc1”, an operation type “revision”, and an operator userA. In the document management server 10 that has received the ID-added document “Doc7”, the derivation relationship registration unit 132 determines that the operation type of the ID-added document “Doc7” is “revision”. A record with management ID “Doc1” is searched from the derivation relationship DB 110. Then, “ver2”, which is information indicating that the version of the record with the management ID “Doc1” is the one after the document version “ver1”, is used as the document of the record of the derivation relation DB 110 corresponding to the ID-added document “Doc7”. Register as version value. After the record of the ID-added document “Doc7” is registered in the derivation relationship DB 110, when userE performs a “response” operation on the ID-added document “Doc7” which is a revised form document, the ID-added document “Doc7” The record of the ID-added document “Doc8” is registered in the derivation relationship DB 110 as a child of. When the ID-added document “Doc8” is received from the client terminal 20, the derivation relationship registration unit 132 of the document management server 10 has the operation type of the ID-added document “Doc8” as “response”, and “new registration” and “ Therefore, the same document version “ver2” as the parent document “Doc7” of the ID-added document “Doc8” is registered as the document version of the ID-added document “Doc8”.

  FIG. 12 shows a tree structure formed by the derivation relationship in the derivation relationship DB 110 in the example of FIG. 11 at the time when “Doc8” is registered.

  FIG. 13 shows a case where the document management server 10 uses the client terminal 20 to designate the ID-added document “Doc1” as a designated document when the derivation relation DB 110 has the data contents illustrated in FIG. 7 is displayed on the display device of the client terminal 20 as a result of the processing of the procedure in the example of FIG. 7 by the request processing unit 140 when a document corresponding to the above is received (the document whose operation type is “response”). It is an example. In the display screen of the example of FIG. 13, for each of the documents “Doc2”, “Doc3”, “Doc6”, and “Doc8” that satisfy the search conditions, in addition to the items displayed on the display screen of the example of FIG. The version is displayed. Rows 80a, 80b, 80c, and 80d in the table in the display screen of the example of FIG. 13 correspond to the documents “Doc2”, “Doc3”, “Doc6”, and “Doc8”, respectively. With the display screen in the example of FIG. 13, the execution status of the “collection” operation for the document corresponding to the “response” operation is presented to the user together with the document version of the form document.

  In the example of the processing of the embodiment described above, the operation type limiting unit 150 notifies the document registration unit 130 that the operation type of the ID-added document 300 to be registered in the derivation relationship DB 110 is not limited, and the document registration unit 130 registers the ID-added document 300 received from the client terminal 20 in the derivation relationship DB 110 regardless of the operation type. Hereinafter, an example of processing of the document registration unit 130 when the operation type limitation unit 150 limits the operation type of the ID-added document 300 to be registered in the derivation relationship DB 110 will be described. As an example, a process in the case where the operation type limiting unit 150 instructs the document registration unit 130 to register in the derivation relationship DB 110 as a registration target only an ID-added document whose operation type is “new registration” or “response”. explain. Upon receiving the ID-added document 300 from the client terminal 20, the document registration unit 130 of the document management server 10 extracts the operation type from the log information 316, and whether the extracted operation type is “new registration” or “response”. Determine whether or not. If the operation type of the ID-added document 300 is “new registration” or “response”, the document registration unit 130 registers the document content 320 in the document DB 100, and the derivation relationship registration unit 132 stores the meta information 310. Register in the derivation relationship DB 110. When the operation type of the ID-added document 300 does not correspond to either “new registration” or “response”, the document registration unit 130 determines the document content 320 of the ID-added document 300 and the document DB 100 of the meta information 310 and the derivation relationship. Registration to the DB 110 is not performed. In this case, a process of returning the ID of the ID-added document 300 held in the client terminal 20 to the ID before the operation is performed.

  In the example of the embodiment described above, the document management server 10 derives the parent ID and log information (operation type, operator, operation date / time, etc.) in association with the management ID of each ID-added document. Register in the relationship DB 110. In an example of another embodiment, not only the parent ID and log information but also information extracted from the document content 320 of the ID-added document 300 is registered in the derivation relationship DB 110 in association with the management ID of the ID-added document 300. May be. For example, text information included in the document content 320 is extracted by performing text extraction processing, OCR (Optical Character Reader) processing, etc. on the document content 320 of the ID-added document 300, and the extracted text information is attributed as management ID. It may be registered in the derivation relationship DB 110 in association with.

  FIG. 14 shows an example of data content of the derivation relationship DB 110 when information extracted from the document content 320 of the ID-added document 300 is registered in the derivation relationship DB 110 together with the meta information 310. FIG. 14 shows an example of an operation history of a document derived from an ID-added document “Doc11” (operation type is “new registration”) which is an article purchase application form. In the derivation relationship DB 110 in the example of FIG. 14, in addition to the same items (parent ID, operation type, and operation date and time) as in the example of FIG. 5 in association with each management ID, “amount”, “quantity”, And each item of “item” is registered. Referring to FIG. 14, each userB, userC, and userD fills in an ID-added document “Doc11” and performs a “response” operation, whereby an ID-added document as a result of each “response” operation ” Records corresponding to Doc12 "," Doc13 ", and" Doc14 "are registered in the derivation relationship DB 110. When the document registration unit 130 of the document management server 10 receives the ID-added document 300 whose operation type is “response” from the client terminal 20, the text extraction process or the OCR process is performed on the document content 320 of the ID-added document 300. To extract information corresponding to the value of each item of “amount”, “quantity”, and “item”. The items to be extracted here are set in advance according to the format of the form document, for example, by the administrator of the document management server 10 or the like. In the example of FIG. 14, it is assumed that information is extracted from the document content 320 only for a document whose operation type is “response”.

  14 is an example of data contents of the derivation relationship DB 110 when the operation type limiting unit 150 of the document management server 10 limits the operation types of ID-added documents to be registered to “new registration” and “response”. But there is.

  In the table of the example of FIG. 14, when records with management IDs “Doc11” to “Doc14” are registered in the derivation relationship DB 110, a search request (search for the management ID “Doc11” from the client terminal 20 of userA as a designated document) When a condition: a document corresponding to a descendant of the designated document is selected, the request processing unit 140 of the document management server 10 performs the processing of the procedures in the examples of FIGS. Then, the display screen illustrated in FIG. 15 is displayed on the display screen of the client terminal 20. Referring to FIG. 15, for each of the ID-added documents “Doc12”, “Doc13”, and “Doc14” corresponding to the “response” operation for the ID-added document “Doc11”, the response date / time (operation date / time) and responder (operator) ), Contents of each item of amount, quantity, and item are displayed. In the table in the display screen of the example of FIG. 15, rows 90a, 90b, and 90c correspond to ID-added documents “Doc12”, “Doc13”, and “Doc14”, respectively. With the display screen in the example of FIG. 15, part of the document contents of the ID-added documents “Doc12”, “Doc13”, and “Doc14” are presented to userA.

  Inputs to the check box associated with each ID-added document and the “Set checked document to be collected” button on the display screen in the example of FIG. 15 are received as a forced registration instruction by the forced registration instruction receiving unit 220 of the client terminal 20. It is done. For example, userA checks the check boxes corresponding to the ID-added documents “Doc12” and “Doc13” on the display screen in the example of FIG. And click operation. In this case, the compulsory registration instruction accepting unit 220 accepts the above-described input by userA as a compulsory registration instruction for the ID-added document as a result of the “collection” operation for the ID-added documents “Doc12” and “Doc13”. Then, the forced registration instruction receiving unit 220 requests the document operation unit 200 to generate the ID-added document 300 as a result of the “collection” operation for the ID-added documents “Doc12” and “Doc13”. In response to a request from the forced registration instruction receiving unit 220, the document operation unit 200 generates an ID-added document 300 that includes information indicating that a forced registration instruction has been included in the log information 316 of the meta information 310. For example, the ID assignment unit 202 assigns new management IDs “Doc15” and “Doc16” to the documents resulting from the “collection” operation on the ID-added documents “Doc12” and “Doc13”. The derivation relationship incorporating unit 204 generates two pieces of meta information 310 corresponding to the new management IDs “Doc15” and “Doc16” assigned by the ID assigning unit 202, respectively. The derivation relationship incorporating unit 204 sets the parent ID in the meta information 310 of the management ID “Doc15” as “Doc12” and sets the parent ID in the meta information 310 of the management ID “Doc16” as “Doc13”. In the log information 316 in the meta information 310 of the management IDs “Doc15” and “Doc16”, the operation type is set to “collected”. Furthermore, the derivation relationship incorporating unit 204 sets information indicating that a forced registration instruction has been issued in the log information 316.

  FIG. 16 shows an example of the contents of the meta information 310 generated by the derivation relationship incorporating unit 204 for each of the management IDs “Doc15” and “Doc16”. The contents of one row of the table in the example of FIG. 16 indicate the contents of the meta information of each management ID. The meta information of the management IDs “Doc15” and “Doc16” illustrated in FIG. 16 includes an item of “forced registration” in addition to the items of the parent ID, operation type, operator, and operation date and time already described. . Referring to FIG. 16, the value of the forced registration item is set to “yes”. This indicates that there has been a forced registration instruction from the user for the ID-added documents “Doc15” and “Doc16”. The document operation unit 200 generates ID-added documents “Doc15” and “Doc16” including meta information having the contents illustrated in FIG. 16 and outputs the generated documents to the registration processing unit 210. The registration processing unit 210 transmits these ID-added documents “Doc15” and “Doc16” to the document management server 10. The document contents 320 of the ID-added documents “Doc15” and “Doc16” are empty.

  When the log information 316 of the ID-added document 300 received from the client terminal 20 includes information indicating that there has been a forced registration instruction, the document registration unit 130 of the document management server 10 registers the operation type limitation unit 150. Regardless of whether the operation type of the ID-added document 300 is included in the operation type specified as the target, the record corresponding to the ID-added document 300 is registered in the derivation relationship DB 110. Therefore, for example, when the operation type limiting unit 150 instructs the document registration unit 130 to register only records corresponding to ID-added documents whose operation type is “new registration” or “response” in the derivation relation DB 110. Even in the case of ID-added documents “Doc15” and “Doc16” (operation type is “collection”) whose “forced registration” item value is “yes”, the document registration unit 130 corresponds to each document. Records are registered in the derivation relationship DB 110. In the data content of the derivation relationship DB 110 in the example of FIG. 14, the records with management IDs “Doc15” and “Doc16” are registered by ignoring the content of the instruction by the operation type restriction unit 150 according to the above processing example regarding the forced registration command. Record.

  Referring to FIG. 15 again, the “content confirmation” button is a button for instructing to download the corresponding ID-added document to the client terminal 20. When the “confirm content” button is pressed on the display screen of the client terminal 20, a corresponding ID-added document is downloaded from the document management server 10 to the client terminal 20. The document operation unit 200 of the client terminal 20 generates an ID-added document corresponding to the download operation (operation type is “download”). The ID-added document generated at this time does not include information indicating that there is a forced registration instruction in the log information. For example, the value of the “force registration” item in the log information is set to a value different from “yes” (for example, “no” or “null”). Alternatively, the log information may not include the “forced registration” item itself. The client terminal 20 transmits to the document management server 10 an ID-added document generated as a result of the download operation by pressing the “content confirmation” button in the example of FIG. In the document management server 10, when the operation type to be registered is limited to “new registration” or “response” by the operation type limiting unit 150, the document management server 10 that has received the ID-added document as a result of the download operation described above Since the operation type is “download” and the information indicating that the forced registration instruction has been issued is not included in the log information, the document with the ID is not registered in the derivation relationship DB 110. In this case, processing for returning the ID of the ID-added document held in the client terminal 20 to the ID before the operation is performed.

  In the foregoing, an example of processing related to the operation type limiting unit 150 of the document management server 10 and the forced registration instruction receiving unit 220 of the client terminal 20 has been described. In the above-described example, the client terminal 20 determines the operation result regardless of whether the operation type of the operation performed on the ID-added document is set as the registration target by the operation type limiting unit 150 of the document management server 10. The ID-added document is transmitted to the document management server 10. In another example, when the client terminal 20 stores information representing the setting contents of the operation type limiting unit 150 of the document management server 10 in a storage device (not shown), and an operation of the operation type to be registered is executed. Only the ID-added document may be transmitted to the document management server 10. In the example of determining whether to send an ID-added document to the document management server 10 according to the setting contents of the operation type limiting unit 150 in the client terminal 20, the forced registration instruction receiving unit 220 issues a forced registration instruction for a specific ID-added document. Is received, regardless of the setting content of the operation type limiting unit 150, the ID-added document is registered in the document management server 10 by sending the ID-added document to the document management server 10. The

  In the various processing examples described above, providing an ID-added document to the client terminal 20 as a result of a search request to the document management server 10 is regarded as one “operation”. The ID-added document corresponding to the operation (in the above example, the operation type is “answer”) is registered in the document management server 10 as a child document of the ID-added document provided to the client terminal 20 as a search result. .

  In the example illustrated above, the management ID is issued mainly at each client terminal 20, but instead, the document management server 10 may issue all the management IDs. 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. In the computer, for example, as shown in FIG. 17, a CPU (central processing unit) 40, a memory (primary storage) 42, various I / O (input / output) interfaces 44, and the like are connected via a bus 46 as hardware. Circuit configuration. Also, a disk drive 50 for reading portable non-volatile recording media of various standards such as an HDD (Hard Disk Drive) 48, a CD, a DVD, and a flash memory via the I / O interface 44, for example, to the bus 46. 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 HDD 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 figure which shows the example of schematic structure of a document 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 the example of the process sequence of a request | requirement process part. It is a flowchart which shows the example of the partial process sequence of a request | requirement process part. It is a figure which shows the example of the display screen displayed on the display apparatus of a client terminal. It is a figure which shows the other example of the display screen displayed on the display apparatus of a client terminal. It is a figure which shows the other example of the data content of derivation relation DB. FIG. 12 is a diagram schematically illustrating a tree structure formed by a management ID group in the data content illustrated in FIG. 11. It is a figure which shows the other example of the display screen displayed on the display apparatus of a client terminal. It is a figure which shows the other example of the data content of derivation relation DB. It is a figure which shows the other example of the display screen displayed on the display apparatus of a client terminal. It is a figure which shows the example of the content of the meta information of a document with ID. 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, 40 CPU, 42 memory, 44 I / O interface, 46 bus, 48 HDD, 50 disk drive, 100 document DB, 110 derivation relation DB, 130 document registration unit, 132 derivation Relationship registration unit, 140 Request processing unit, 150 Operation type limiting unit, 200 Document operation unit, 202 ID allocation unit, 204 Derived relationship incorporation unit, 210 Registration processing unit, 220 Forced registration instruction reception unit, 300 Document, 310 Meta information 320 Document content.

Claims (4)

A registration unit that receives from the information processing apparatus information about a derivation relationship having a first document as a parent and a second document generated as a result of an operation on the first document as a child;
Documents satisfying the search condition among the trees included in the tree structure to which the designated document belongs, which are the tree structure represented by the derivation relation group registered in the storage unit in response to a use request specifying the designated document and the search condition An output target document, and an output unit that outputs information on the output target document;
With
The registration unit further registers, in the storage unit, information on a derivation relationship in which the output target document is a parent, and the output unit outputs a document that is a result of outputting information related to the output target document. And receiving information indicating the type of operation for the first document from the information processing apparatus, and when the type of operation is a predetermined type, and when the type of operation is other than the predetermined type, When the forced registration instruction attached to the second document is detected by the information processing apparatus, the derivation relationship information is registered in the storage unit, and the type of operation is other than the predetermined type, and the forced type is registered. If the registration instruction is not detected, the information on the derivation relationship is not registered in the storage unit .
A document management apparatus characterized by that. The output unit outputs display information that causes a display device to display a document having the output result document as a child and other documents among the output target documents satisfying the search condition, in a manner different from each other.
The document management apparatus according to claim 1 . Receiving, from the information processing apparatus, derivation relationship information having a first document as a parent and a second document generated as a result of an operation on the first document as a child, and registering the information in a storage unit;
Documents satisfying the search condition among the trees included in the tree structure to which the designated document belongs, which are the tree structure represented by the derivation relation group registered in the storage unit in response to a use request specifying the designated document and the search condition Output the information on the output target document, and
Derivation relation information having the output target document as a parent and the output unit as a result of outputting information related to the output target document as a child is registered in the storage unit, and the first document Information indicating the type of the operation for the information processing device is received from the information processing device, and when the operation type is a predetermined type, and when the operation type is other than the predetermined type, the information processing device When the forced registration instruction attached to the document is detected, the derivation relationship information is registered in the storage unit, and the operation type is other than the predetermined type and the forced registration instruction is not detected. Not registering the derivation relationship information in the storage unit ;
A document management program for causing a computer to execute. An information processing device and a document management device;
The information processing apparatus includes:
A transmission unit configured to transmit, to the document management apparatus, information on a derivation relationship having a first document as a parent and a second document generated as a result of an operation on the first document as a child;
A request unit for making a use request for specifying a designated document and a search condition to the document management device;
With
The document management apparatus includes:
A registration unit that receives the derivation relationship information from the information processing apparatus and registers the information in the storage unit;
In response to the use request from the information processing apparatus, a document that satisfies the search condition among documents included in the tree structure represented by the derivation relation group registered in the storage unit and to which the designated document belongs. An output target document, and an output unit that outputs information about the output target document,
The registration unit further registers, in the storage unit, information on a derivation relationship in which the output target document is a parent, and the output unit outputs a document that is a result of outputting information related to the output target document. And receiving information indicating the type of operation for the first document from the information processing apparatus, and when the type of operation is a predetermined type, and when the type of operation is other than the predetermined type, When the forced registration instruction attached to the second document is detected by the information processing apparatus, the derivation relationship information is registered in the storage unit, and the type of operation is other than the predetermined type, and the forced type is registered. If the registration instruction is not detected, the information on the derivation relationship is not registered in the storage unit .
A document management system characterized by that.

Images