JP5407209B2 - 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.

  There are cases where a plurality of users give additional information such as comments about the contents of an electronic document. For example, when a plurality of different users edit a document together, it is conceivable that each user who is involved in editing gives a comment or the like regarding his / her editing portion to the document as additional information. The additional information given to the electronic document is used to create a revised version of the electronic document, for example.

  A system for registering an electronic document in a server and managing additional information given to the registered document in association with the document has been developed. For example, Patent Document 1 discloses a document management system that manages additional data attached to an arbitrary area of a registered document in association with the information of the document and the creator of the additional data. The database server of this document management system performs processing such as document reference, additional data reference, registration, and deletion in response to a request from a user using a client computer. If a reference request for additional data is made when a plurality of additional data is registered in one area of the document, each registered additional data and its creator are displayed in a list in association with each other.

  Further, for example, Patent Document 2 discloses a document management apparatus that manages a document circulated by a plurality of users and additional information added to the document, and adds a document to each preset group of circulators. A document management apparatus for managing information is disclosed.

  On the other hand, 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 3, 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 the operation result. 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 3 receives a request to browse a document with an operation ID specified, the information about the document with the operation ID obtained by tracing the derivation relationship starting from the specified operation ID is sent to the user. provide.

JP 2001-175650 A JP 2007-58622 A JP 2008-3846 A

  By the way, the user may download the electronic document registered in the server to his / her client terminal, and may edit the electronic document or give additional information to the client terminal. In this case, the user registers (uploads) the electronic document after editing, addition of additional information, and the like. When each user edits an electronic document on his / her client terminal, for example, after the revised electronic document is registered in the server, the old version of the electronic document (the electronic document before the revision) is edited or commented May be added. The contents such as editing performed on the old version of the electronic document may be contents to be considered when the revised version of the electronic document is further revised.

  An object of the present invention is to facilitate retrieval of information related to operations performed on an old version of an electronic document after a revised version of the electronic document is registered.

According to the first aspect of the present invention, information on a derivation relationship having the first document as a parent and the second document as a child 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 that further receives an operation type and time for the first document from the information processing apparatus, and registers the operation type and time in association with the second document in the storage unit; In a tree structure represented by a registration unit and a derivation relationship group registered in the storage unit, to which the first document in the derivation relationship information received by the registration unit from the information processing apparatus belongs, A determination unit that determines whether one document corresponds to an ancestor of the latest document that is a document associated with the latest revision operation among documents included in the tree structure; and the determination unit Said first sentence in A processing unit that performs processing for associating information related to the operation on the first document with the latest document in the tree structure when it is determined that the document corresponds to an ancestor in the tree structure with respect to the latest document. , And the processing unit determines that the determination unit determines that the first document corresponds to an ancestor in the tree structure with respect to the latest version document, and the registration unit receives from the information processing apparatus. In the document management apparatus, the association processing is performed when the type of operation received together with the derivation relationship information corresponds to a response operation .

The invention according to claim 2 is the invention according to claim 1 , wherein the processing for associating includes the operation of the type of operation received by the registration unit together with the information of the derivation relationship from the information processing apparatus. Is a process of outputting information prompting the user to perform to the information processing apparatus.

According to a third aspect of the present invention, in the first aspect of the invention, the associating process is a derivation relationship indicating that the second document in the received derivation relationship information is a child of the latest document. Is registered in the storage unit.

According to a fourth aspect of the present invention, in the first aspect of the invention, the associating process generates reference information for the second document in the received derivation relation information and registers the reference information in the storage unit. In addition, it is a process of registering in the storage unit derivation relationship information having the latest document as a parent and the reference information as a child.

The invention according to claim 5 receives information of a derivation relationship having the first document as a parent and the second document as a child as a result of the operation on the first document from the information processing apparatus, and registers the information in the storage unit. In the registration step, the operation type and time for the first document are received from the information processing apparatus, and the operation type and time are associated with the second document and registered in the storage unit. In the registration step and the tree structure represented by the derivation relation group registered in the storage unit, the tree part to which the first document in the derivation relation information received by the registration unit from the information processing apparatus belongs, 1 of the document, and the determination step to determine whether or not to correspond to the ancestral respect latest document is a document associated with the latest revision operation of the document included in the tree structure, the determination stearate If the first document determines that the first document corresponds to an ancestor in the tree structure with respect to the latest document, the information related to the operation on the first document is associated with the latest document in the tree structure. And the processing step is a case where it is determined in the determination step that the first document corresponds to an ancestor in the tree structure with respect to the latest version document. In the registration step, when the type of operation received together with the derivation relationship information from the information processing apparatus corresponds to a response operation, the association management process is performed .

An invention according to claim 6 includes an information processing device and a document management device, wherein the information processing device has the first document as a parent and a second document as a result of an operation on the first document as a child. A derivation relationship information, and a transmission unit that transmits to the document management device the operation type and time for the first document, and the document management device includes the derivation relationship from the information processing device. Is registered in the storage unit, and further receives the operation type and time for the first document from the information processing apparatus, and stores the operation type and time for the second document. A registration unit registered in the storage unit in association with the storage unit, and a tree structure represented by a derivation relationship group registered in the storage unit, wherein the registration unit receives the first information in the derivation relationship information received from the information processing apparatus. The document belongs to In the tree structure, a determination to determine whether or not the first document corresponds to an ancestor of the latest document that is a document associated with the latest revision operation among the documents included in the tree structure. And the determination unit determine that the first document corresponds to an ancestor in the tree structure with respect to the latest document, information about an operation on the first document is stored in the tree structure. e Bei a processing unit that performs processing for associating the plate document, wherein the processing unit, the determination in the above section first document is determined to correspond to an ancestor in the tree structure to the latest document when the registering unit even if the type of the operations received together with information on the derivation relationship from the information processing apparatus corresponds to response operation performs processing for associating the, the It is a document management system for the butterflies.

According to the invention according to claim 1, 5 or 6 , an operation on an electronic document whose version is older than the latest electronic document can be detected , and the operation is performed on an electronic document whose version is older than the latest electronic document. Information related to operations can be managed in association with the latest version of the electronic document, and information related to operations of a preset type that have been performed on versions of the electronic document older than the latest version of the electronic document Ru can be managed in association with the electronic document.

According to the second aspect of the present invention, it is possible to prompt a user who has performed an operation on an electronic document whose version is older than the latest version of the electronic document to perform the operation on the latest version of the electronic document.

According to the third aspect of the present invention, it is possible to manage a document as a result of an operation on an electronic document whose version is older than the latest version of an electronic document as an operation result document for the latest version of an electronic document.

According to the fourth aspect of the present invention, a document as a result of an operation on an electronic document whose version is older than the latest electronic document can be acquired from reference information registered as an operation result on the latest electronic document.

  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. The client terminal 20 is a terminal used by a user to operate a document, and examples thereof include a personal computer and a digital copying machine. As shown in FIG. 2, the client terminal 20 includes a document operation unit 200 and a registration processing unit 210.

  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 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, and a request processing unit 140.

  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 document registration unit 130 further includes a registration restriction determination unit 134 and a registration restriction processing unit 136. When the document management server 10 receives an ID-added document from the client terminal 20, the registration restriction determination unit 134 determines whether the ID-added document is subject to registration restriction. In the example of the present embodiment, after a new version (revised version) document is registered in the document management server 10, an operation of a specific operation type is performed on a document with an ID (old version) older than the revised version. When the ID-added document is received from the client terminal 20, the ID-added document is determined to be subject to registration restriction. The registration restriction processing unit 136 includes a determination condition used for the determination of the registration restriction determination unit 134 and information indicating the content of the restriction process executed for the ID-added document determined to be subject to registration restriction. The restriction information is registered in the derivation relation DB 110. Further, the registration restriction processing unit 136 performs a restriction process according to the set registration restriction information on the ID-added document that is determined to be subject to registration restriction by the registration restriction determination unit 134. Examples of processing contents of the registration restriction determination unit 134 and the registration restriction processing unit 136 will be described in detail later.

  The derivation relation DB 110 is a database that accumulates meta information mainly including derivation relation information in the ID-added document 300 received by the document management server 10 from the client terminal 20. 5A and 5B show an example of data contents of the derivation relationship DB 110. FIG. FIG. 5B shows an example of the data content of the derivation relationship DB 110 when a certain time has elapsed since the derivation relationship DB 110 had the data of the example of FIG. 5A. One row of information in each table shown in FIGS. 5A and 5B is a meta information record corresponding to one ID-added document 300. In this example, items of parent ID, operation type, operator, operation date and time, and registration restriction 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. In the registration restriction item, registration restriction information set by the registration restriction processing unit 136 is stored. The registration restriction information is a record restriction information for a record corresponding to an old version of an ID-added document when an operation for registering a revised ID-added document with respect to a certain ID-added document ("revision registration" operation) is performed. Set to the item.

  For example, at the time when the derivation relationship DB 110 has the data of the example of FIG. 5A, the ID-added document whose operation type is “revision registration” is not registered in the derivation relationship DB 110, and the derivation relationship DB 110 No value is set in the registration restriction item of any record. Referring to FIG. 5B showing a state after a lapse of a certain time from the state illustrated in FIG. 5A, “child: response, revision registration: prohibited” is set in the registration restriction item of the record of management ID “Doc1”. ing. This registration restriction information represents that registration of an ID-added document that is a child of the ID-added document “Doc1” and whose operation type is “response” or “revision registration” to the document management server 10 is prohibited. Here, the operation type “response” represents an operation for adding additional information such as a comment to the ID-added document. In addition, the registration restriction information includes the ID-added document “Doc5” as a result of the “revision registration” operation for the ID-added document “Doc1” from the client terminal 20, and the record of the management ID “Doc5” is registered in the derivation relation DB 110. Registered by the registration restriction processing unit 136 of the document registration unit 130.

  The meta information items illustrated in FIGS. 5A and 5B 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.

  5A and 5B are merely representations of data managed by the derivation relationship DB 110 from the viewpoint of contents, and do 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. 5B 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 request processing unit 140 provides a service using the derivation relationship DB 110 in response to a service request including a 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.

  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.

  Hereinafter, various processes in the document management system will be described in detail.

  First, an example of processing of the document registration unit 130 when the document management server 10 receives the ID-added document 300 from the client terminal 20 will be described.

  FIG. 7 is a flowchart illustrating an example of a processing procedure of the document registration unit 130.

  Upon receiving an ID-added document from the client terminal 20, the document registration unit 130 first determines whether the operation type of the received ID-added document (hereinafter also referred to as “processed ID-added document”) is new registration. Determine (step S10). If the operation type is new registration (YES in step S10), the meta information of the ID-added document to be processed is registered in the derivation relation DB 110, and the document content is registered in the document DB 100 (step S60). If the operation type is not new registration (NO in step S10), the registration restriction determination unit 134 of the document registration unit 130 performs registration restriction information search processing (step S20).

  When the registration restriction information search process (step S20) is started, the registration restriction determination unit 134 starts the process illustrated in FIG. Referring to FIG. 8, first, the parent ID in the meta information of the ID-added document to be processed is set as the attention ID (step S200), and then the record corresponding to the attention ID is acquired from the derivation relationship DB 110 (step S202). . Then, it is determined whether registration restriction information is set in the registration restriction item of the acquired record (step S204). If the determination result is YES, the set registration restriction information is acquired and used as a search result (step S206). Thereafter, it is determined whether or not the operation type of the ID-added document to be processed is a restriction target in the acquired registration restriction information (step S208). If the operation type of the ID-added document to be processed is a restriction target (YES in step S208), the processing of the procedure in the example of FIG. 8 is terminated as it is, and the operation type of the ID-added document to be processed is not the restriction target. (NO in step S208), the search result of the registration restriction information is set to NULL (no search result) (step S212), and the process of the procedure in the example of FIG.

  If registration restriction information is not set in the registration restriction item of the record of the attention ID (NO in step S204), it is determined whether or not the operation type of this record is new registration or revision registration (step S210). If this determination result is YES, the search result of registration restriction information is set to NULL (step S212), and the process of the procedure in the example of FIG. On the other hand, when the operation type of the record of the attention ID is neither new registration nor revision registration (NO in step S210), the value of the parent ID of the record of the attention ID is set as the new attention ID (step S214), and the process is step. Return to S202.

  In the procedure of the example of FIG. 8, a loop structure including steps S202, S204, S210, and S214 is used to create a tree structure of derivation relationships (see the example of FIG. 6) starting from the parent document of the ID-added document to be processed. "Registration restriction information set in the nodes included in the route traced back to the ancestor direction is searched until a node for" operation "(root node) or a node for" revision registration "operation appears.

  When the process of the procedure in the example of FIG. 8 ends, the process returns to step S20 in FIG. Referring to FIG. 7 again, the registration restriction determination unit 134 determines whether the search result of the registration restriction information search process is NULL (step S30). If the search result is NULL (YES in step S30), it is determined that the ID-added document to be processed is not a registration restriction target, and the process proceeds to step S40. If the search result is not NULL (NO in step S30), it is determined that the ID-added document to be processed is a registration restriction target, and the registration restriction processing unit 136 performs restriction according to the content of the registration restriction information in the search result. Processing is performed (step S70). For example, if the registration restriction information “child: response, revision registration: prohibited” in the record of the management ID “Doc1” in the table of the example of FIG. 5B is a search result, this registration restriction information is a document that is subject to registration restriction. Represents that registration to the document management server 10 is prohibited. Therefore, in this example, the restriction process is that the ID-added document to be processed is not registered in the document DB 100 and the derivation relationship DB 110.

  In step S40, the document registration unit 130 determines whether or not the operation type of the ID-added document to be processed is revision registration. If it is not revision registration (NO in step S40), the document registration unit 130 registers meta information and document contents of the ID-added document to be processed in the derivation relation DB 110 and the document DB 100, respectively (step S60). If it is revision registration (YES in step S40), the registration restriction processing unit 136 of the document registration unit 130 performs registration restriction information setting processing (step S50). In the registration restriction information setting process, in the tree structure of document derivation relationships, the “new registration” operation or “ Registration restriction information is set for the node of the “revision registration” operation.

  FIG. 9 shows an example of the procedure of the registration restriction information setting process (step S50 in FIG. 7). Referring to FIG. 9, when the registration restriction information setting process is started, first, the registration restriction processing unit 136 sets the parent ID of the ID-added document to be processed as the attention ID (step S500). Next, a record corresponding to the attention ID is acquired from the derivation relationship DB 110 (step S502). Then, it is determined whether or not the operation type of the acquired record is new registration or revision registration (step S504). When the operation type of the record of attention ID is new registration or revision registration (YES in step S504), the registration restriction processing unit 136 sets registration restriction information in the record of attention ID in the derivation relation DB 110 (step S506). The process of the procedure in the example of FIG. The contents of this registration restriction information are preset by, for example, a system administrator. In the example of FIG. 5B, information indicating that registration of an ID-added document whose operation type is “response” or “revision registration” is prohibited as registration restriction information as a child of the ID-added document corresponding to the corresponding record. Is done.

  In step S504 in FIG. 9, when the operation type of the record of attention ID is neither new registration nor revision registration, the registration restriction processing unit 136 sets the value of the parent ID in the record of attention ID as a new attention ID. Then (step S508), the process returns to step S502.

  In the procedure of the example of FIG. 9, the loop process including steps S502, S504, and S508 first appears on the path that goes from the parent document of the ID-added document to be processed to the root of the derivation relation tree structure in the direction of the root node. Registration restriction information is set in the record of the derivation relationship DB 110 corresponding to the node of the “revision registration” operation. If there is no “revision registration” operation node on the route going back to the root node, registration restriction information is set in the record of the derivation relationship DB 110 corresponding to the root node (operation type is “new registration”).

  When the registration restriction information setting process in the example of FIG. 9 is completed, in step S60 of FIG. 7, the document registration unit 130 registers the meta information and document content of the ID-added document to be processed in the derivation relationship DB 110 and the document DB 100, respectively. .

  As described above, according to the processing example of the document registration unit 130 described with reference to FIGS. 7 to 9, a revised document (operation type is “revision registration”) of a certain ID-added document is registered in the document management server 10. In the tree structure of the document derivation relationship, registration restriction information is set for the document of the “new registration” operation or the document of the “revision registration” operation corresponding to the ancestor of the revised document. When a document for “revision registration” operation is registered in the document management server 10, the document is the latest version in the tree structure of the derivation relationship to which the document belongs. Therefore, it can be said that the registration restriction information is set for a document corresponding to an ancestor of the latest version of the document. When the document registration unit 130 receives an ID-added document from the client terminal 20, the registration restriction information is searched by tracing the tree structure of the derivation relationship starting from the parent document of the document toward the root node. At this time, if there is a “revision registration” operation node for which registration restriction information is not set on the route going back to the root node, this node corresponds to the latest version of the document, so the document received from the client terminal 20 is the latest. Corresponds to the descendants of the version document and is not subject to registration restrictions. On the other hand, if there is a node for which registration restriction information is set on the route going back to the root node, the document received from the client terminal 20 is a document derived from the document corresponding to the ancestor of the latest version of the document, and the registration restriction It becomes the object of.

  As described above, according to the processing example of the document registration unit 130 described with reference to FIGS. 7 to 9, the latest version of the documents included in the tree structure having one “new registration” operation document as a root node. Registration of a document as a result of executing an operation of a specific operation type for a document corresponding to an ancestor of the document is limited. In other words, after the revised document is registered, the operation type restricted in the registration restriction information for the ID-added document version older than the revised version (in the example of FIG. 5B, “response” or “revision”). The ID-added document generated as a result of the operation of “registration”) is subject to registration restriction.

  The example of the processing procedure of the document registration unit 130 of the document management server 10 has been described above. A specific example of how document operation information is registered in the document management system will be described below with reference to FIGS. 5A, 5B, and 6. FIG.

  Referring to FIG. 5A, first, a “new registration” operation of a document is executed at 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 registration unit 130 of the document management server 10 starts processing of the procedure in the example of FIG. Since the operation type of the ID-added document “Doc1” is new registration, the process proceeds from step S10 in FIG. 7 to step S60, and the document registration unit 130 transfers the document contents in the ID-added document “Doc1” to the document DB 100 and meta information. Are registered in the derivation relationship DB 110, respectively. 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 adds a comment to the ID-added document “Doc1” using the document operation unit 200 of his / her client terminal, and instructs “response (register comment-added document)” on the operation menu. The client terminal 20 generates an ID-added document “Doc2” as a result of the “response” operation, and the ID-added document “Doc2” is transmitted to 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 adding a comment to the ID-added document “Doc1”, the document content 320 is changed from the document content of the ID-added document “Doc1”. 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. In the document registration unit 130 of the document management server 10, the processing of the procedure in the example of FIG. 7 for processing the ID-added document “Doc2” proceeds from step S10 to step S20 because the operation type is not “new registration”. Since the registration restriction information is not set in the document “Doc1” which is the parent of the document “Doc2” to be processed, the search result of the registration restriction information search process (FIG. 8) is NULL, and steps S30 to S40 in FIG. Proceed to Further, since the operation type is not “revision registration”, the registration restriction information setting process (step S50) is not performed, and the meta information of the ID-added document “Doc2” is stored in the derivation relation DB 110 and the document content is stored in the document DB 100. Each is registered.

  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 the content after the comment is added.

  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 adds a comment to 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 has the value of the management ID 312. An ID-added document “Doc3” having “Doc3”, a parent ID 314 value of “Doc1”, and an operation type value of “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. By adding a comment, the document content changes from the document content of the ID-added document “Doc1”. In the document registration unit 130 of the document management server 10, the process of the example of FIG. 7 is performed on the ID-added document “Doc3”. Since the ID-added document “Doc3” has the same operation type “response” and parent ID “Doc1” as the ID-added document “Doc2”, the processing in the example of FIG. 7 proceeds in the same manner as the procedure described above for the document “Doc2”. Thus, the record of the management ID “Doc3” is registered in the derivation relationship DB 110.

  Furthermore, when userA performs a “browsing” operation on the ID-added document “Doc1” on its own client terminal 20, the client terminal 20 generates an ID-added document “Doc4” as a result of browsing, and the ID-added document. It is replaced with “Doc1” and transmitted to the document management server 10. In the document registration unit 130 of the document management server 10, the processing of the procedure in the example of FIG. 7 for processing the ID-added document “Doc4” is neither “new registration” nor “revision registration”. In addition, since registration restriction information is not set for the ID-added document “Doc1” that is the parent of the ID-added document “Doc4”, the process proceeds in the same manner as the procedure described above for the ID-added document “Doc2”. In the derivation relationship DB 110, a record with a management ID “Doc4” is registered. The table in the example of FIG. 5A shows an example of data contents of the derivation relationship DB 110 at this time.

  After the ID-added document “Doc4” is registered in the document management server 10, userA edits the ID-added document “Doc4” by the document operation unit 200 of the client terminal 20 to create a new version of the document. Instruct "Revision registration" on the menu. The client terminal 20 generates an ID-added document “Doc5” as a result of the “revision registration” operation, and transmits it to the document management server 10. The document registration unit 130 of the document management server 10 performs the process of the example of FIG. 7 with the ID-added document “Doc5” as a processing target. Referring to FIG. 7, since the operation type of the ID-added document “Doc5” is not newly registered, the process proceeds to NO as a result of the determination in step S10, and registration restriction information search processing (step S20) is performed. At this point, the derivation relationship DB 110 has the data contents of the example of FIG. 5A. Since registration restriction information is not set for the ID-added document “Doc4” that is the parent of the ID-added document “Doc5” and the ID-added document “Doc1” (root node) that is the parent of the ID-added document “Doc5”. The search result of the information search process (FIG. 8) is NULL, and the process proceeds from step S30 to step S40 in FIG. Since the operation type of the ID-added document “Doc5” to be processed is revision registration, registration restriction information setting processing (step S50, FIG. 9) is performed. In the registration restriction information setting process, a record in the derivation relationship DB 110 corresponding to a new registration node that appears retroactively from the document derivation relationship tree structure (FIG. 6) from the ID-added document “Doc4” that is the parent of the ID-added document “Doc5”. Registration restriction information is set for (management ID “Doc1”). The record of management ID “Doc1” in the table of the example of FIG. 5B shows an example of a record as a result of the registration restriction information setting process. When the registration restriction information setting process is completed, the record of the management ID “Doc5” of the ID-added document to be processed is registered in the derivation relationship DB 110 in step S60 of FIG.

  At this time, the ID-added document “Doc5” is the latest version of the documents derived from the newly registered ID-added document “Doc1”. After that, userB and userC who have received this latest version of the ID-added document “Doc5” from userA by e-mail or the like add a comment to the ID-added document “Doc5” in their client terminal 20, respectively. Perform a "response" operation. The records of management IDs “Doc6” and “Doc7” in FIG. 5B correspond to ID-added documents as a result of the “response” operations of userB and userC, respectively. The process of the example procedure of FIG. 7 in the document registration unit 130 of the document management server 10 when the ID-added documents “Doc6” and “Doc7” are received from the client terminal 20 proceeds in the same manner. In the registration information search process (step S20, FIG. 8), registration restriction information is not set in the ID-added document “Doc5” that is the parent of the ID-added document “Doc6” (“Doc7”) to be processed, and Since the operation type of the ID-added document “Doc5” is revision registration, the process proceeds in the order of steps S204, S210, and S212 in FIG. 8, and the search result is NULL. Furthermore, since the operation type of the ID-added document “Doc6” (“Doc7”) to be processed is “response”, the process proceeds to NO in the determination of step S40 in FIG. 7, and the registration restriction information setting process (step S50) is performed. Instead, the record of the management ID “Doc6” (“Doc7”) is registered in the derivation relationship DB 110. FIG. 5B is an example of the data contents of the derivation relationship DB 110 at this point.

  In the specific example described above, the restriction process (step S70 in FIG. 7) using the registration restriction information is not performed. Hereinafter, a specific example when the restriction process is performed will be described. For example, when the data of the example of FIG. 5B is registered in the derivation relationship DB 110, the userD adds a comment to the ID-added document “Doc1” at the client terminal 20 and performs a “response” operation. Suppose you went. The ID-added document “Doc8” (parent ID is “Doc1”) generated by the client terminal 20 of userD as a result of the “response” operation is transmitted to the document management server 10. When the document registration unit 130 of the document management server 10 performs the process of the example of FIG. 7 with the document “Doc8” as a processing target, as a result of the registration restriction information search process (steps S20 and FIG. 8 of FIG. 7), The registration restriction information set in the record with the management ID “Doc1” in FIG. 5B is acquired. This registration restriction information represents that registration of an ID-added document that is a child of the document corresponding to the management ID “Doc1” and whose operation type is “response” is prohibited from being registered in the document management server 10. The registration restriction processing unit 136 instructs the derivation relationship registration unit 132 not to register the record corresponding to the ID-added document “Doc8” in the derivation relationship DB 110 according to the contents represented by the registration restriction information. As a result of this instruction, the meta information of the ID-added document “Doc8” is not registered in the derivation relationship DB 110. Further, the document content of the ID-added document “Doc8” is not registered in the document DB 100. At this time, the registration restriction processing unit 136 may return information indicating that the document “Doc8” is not registered in the document management server 10 to the client terminal 20 that is the transmission source of the document “Doc8”.

  Also, for example, the “response” operation is performed on the ID-added document “Doc5” which is the latest version of the documents included in the tree structure of the derivation relationship to which the parent document “Doc1” of the document “Doc8” belongs. Information prompting the user may be sent to the client terminal 20. In this way, when information that prompts execution of an operation on the latest document in the restriction process is transmitted to the client terminal 20, the registration restriction processing unit 136 searches for the management ID of the latest document as follows, for example. First, a child of an ID-added document in which registration restriction information acquired by the registration restriction information search process is set (a document corresponding to an attention ID at the end of the process of FIG. 8; in this example, “Doc1”) Search for an ID. The child ID is obtained by extracting a record having the management ID value of the ID-added document as a parent ID from the derivation relationship DB 110 and acquiring the management ID value of the extracted record. In this example, “Doc2”, “Doc3”, and “Doc4” are obtained as child IDs of the document “Doc1” for which registration restriction information is set. And the descendant search process illustrated in FIG. 10 is performed about each child ID.

  Referring to FIG. 10, first, the registration restriction processing unit 136 sets the child ID as the attention ID (Step S11). Next, a record corresponding to the attention ID is acquired from the derivation relationship DB 110 (step S12), and the acquired record is put in the intermediate result list (step S13). Thereafter, the child ID of the attention ID is searched (step S14), and it is determined whether or not the child ID has been searched (step S15). If there is a child ID (YES in step S15), a descendant search process (step S4) is recursively executed for each child ID. 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.

  When the descendant search process in the example of FIG. 10 is completed for all the child IDs of the ID-added document for which registration restriction information is set, the intermediate result list corresponds to the descendants of the ID-added document for which registration restriction information is set. Records corresponding to the documents to be stored. The management ID of the record with the latest operation date / time among the records stored in the intermediate result list and whose operation type is “revision registration” is the management ID of the latest document.

  In this example with reference to FIG. 5B, as a result of the descendant search process of the example of FIG. 10, the intermediate result list includes management IDs “Doc2”, “Doc3”, “Doc4”, “Doc5”, “Doc6”, “Doc7”. "Each record is accumulated. Of these records, the record whose operation type is “revision registration” is only the record with the management ID “Doc5”, so “Doc5” is acquired as the management ID of the latest version document.

  In another example of the restriction process, an ID-added document as a result of an operation performed on a document corresponding to an ancestor of the latest document may be registered in the document management server 10 as a child of the latest document. FIG. 11 shows an example of data contents of the derivation relationship DB 110 when registration restriction information representing restriction processing of this example is set. FIG. 12 shows a tree structure formed by the management ID group in the data content illustrated in FIG.

  The history of the document in the example of FIGS. 11 and 12 will be briefly described in chronological order. First, the document “Doc11” with ID is registered in the document management server 10 by the “new registration” operation of userA. At this point, the registration restriction item for the record with the management ID “Doc11” in the derivation relationship DB 110 is empty. Thereafter, userB and userC sequentially perform a “response” operation to the document “Doc11”, and ID-added documents “Doc12” and “Doc13” (both parent IDs are “Doc11”) are registered. Next, when userA performs a “revision registration” operation on the document “Doc11”, the revised ID-added document “Doc14” is generated and registered in the document management server 10. At this time, since the operation type of the document “Doc14” is “revision registration”, the registration restriction information is registered in the record of the derivation relationship DB 110 corresponding to the document “Doc11” which is the parent document and the document of the “new registration” operation. Is set. Referring to FIG. 11, the value set in the registration restriction item of the record with management ID “Doc11” is “child: response: moved to latest version, child: revised registration: prohibited”. Of these, the “child: response: move to latest version” portion is derived as a child of the latest version of the ID-added document for the ID-added document as a result of the “response” operation for the ID-added document corresponding to the corresponding record. It represents registering in DB110. Further, the “child: revision registration: prohibition” portion is the document management of the ID-added document as a result of the “revision registration” operation for the ID-added document corresponding to the corresponding record, as in the above example referring to FIG. 5B. This indicates that registration to the server 10 is prohibited. At the time when the document “Doc14” is registered in the document management server 10, the document “Doc14” is the latest version among the documents derived from the document “Doc11” of the “new registration” operation, and the management ID “Doc14” Registration restriction information is not set for the record.

  After that, a “response” operation for the document “Doc14” is performed by each of userB and userC, and each operation is an operation for the latest version of the document. “Doc15” and “Doc16” are registered in the document management server 10. Furthermore, when userA performs a “revision registration” operation on the latest version of the document “Doc14” at the current time, the document “Doc17” is generated and registered in the document management server 10 as a result. The document “Doc17” is a new latest document. Since the operation type of the document “Doc17” is “revision registration”, registration restriction information setting processing is performed, and the document “Doc14” which is the parent document of the document “Doc17” and the operation type is “revision registration” is processed. Registration restriction information is set in the corresponding record of the derivation relationship DB 110. The content of the registration restriction information set in the record with the management ID “Doc14” is the same as the record with the management ID “Doc11”.

  Further, in the table of the example of FIG. 11, after the record of the management ID “Doc17” is registered, a comment is added to the ID-added document “Doc11” (operation type is “new registration”) in the client terminal 20 of userD. It is assumed that the “response” operation to be added is performed. When a new ID-added document “Doc18” (parent ID is “Doc11”) generated by the client terminal 20 of userD as a result of the “response” operation is received, the document registration unit 130 of the document management server 10 reads the document “ The processing of the procedure in the example of FIG. 7 is started with Doc18 ”as the processing target. At this time, as a search result of the registration restriction information search process (step S20 in FIG. 7, FIG. 8), the registration restriction information “child” set for the document “Doc11” that is the parent of the document “Doc18” to be processed. : Response: Move to latest version, Child: Revision registration: Prohibited ”is acquired. In accordance with the registration restriction information, the registration restriction processing unit 136 of the document registration unit 130 performs a restriction process (step S70 in FIG. 7). In this restriction process, since the operation type of the processing target document “Doc18” is “response”, the registration restriction processing unit according to the “child: response: move to latest version” portion of the registration restriction information of the search result In 136, the document “Doc18” is registered in the derivation relationship DB 110 as a child document of the latest version document. For this purpose, the registration restriction processing unit 136 performs descendant search processing in the procedure of the example of FIG. 10 to search for the management ID of the latest version document. In this example referring to FIG. 11, the management ID of the latest version document is a document corresponding to a descendant of the document “Doc11” in which the registration restriction information acquired by the registration restriction information search process is set, and the operation type is the operation type. Among the documents “Doc14” and “Doc17” which are “revision registration”, the management ID “Doc17” of the document whose operation date and time is the latest. When the management ID “Doc17” of the latest version document is acquired, the registration restriction processing unit 136 converts the ID-added document “Doc18” (the “response” operation result document for “Doc11”) to the child of “Doc17”, which is the latest version document. The document is registered in the derivation relationship DB 110 as a document.

  The record of the management ID “Doc18” in FIG. 11 is an example of a record registered by the restriction process of this example. In the record of the management ID “Doc18”, the management ID “Doc17” of the latest version document is set as the value of the parent ID. The operation type is “response”, and the operator is userD who performed the operation. Further, information indicating that the actual parent document of the ID-added document “Doc18” is “Doc11” is registered in the “information” item of the record of the management ID “Doc18”. FIG. 12 shows an example of the tree structure formed by the derivation relationship at the time when the management ID “Doc18” is registered in the derivation relationship DB 110 in the table of the example of FIG. Through the restriction processing described above, the document “Doc18” generated as a child document of the old version document “Doc11” is managed as a child document of the latest version document “Doc17” in the document management server 10.

  In still another example of the restriction process, an ID-added document as an operation result for the old version document is registered in the derivation relationship DB 110 as a child document of the old version document, similarly to the registration process when the restriction process is not performed. The reference information for the child document is set as the child document of the latest version of the ID-added document. FIG. 13 shows an example of the data contents of the derivation relationship DB 110 when the restriction process of this example is performed. The operation history of the documents with the management IDs “Doc11” to “Doc17” in the example of FIG. 13 is the same as the history illustrated in FIG. Only the contents of the registration restriction information set in the records of the management IDs “Doc11” and “Doc14” are different. In the table of the example of FIG. 13, the registration restriction information set in the records of the management IDs “Doc11” and “Doc14” is “child: response: reference setting to latest version, child: revision registration: prohibited”. Among these, the “child: revision registration: prohibition” portion is the same as the example of FIG. The “child: response: reference setting for latest version” portion is a document that is an execution target of the “response” operation for a document with an ID that is subject to registration restriction and the operation type is “response”. This indicates that registration is made in the derivation relationship DB 110 as a child of (parent document), and reference information for the registered document is registered as a child document of the latest document.

  A specific example of processing of the document registration unit 130 when the restriction processing of this example is performed will be described below. Similar to the above example described with reference to FIG. 11, useD is set to ID when records from the management IDs “Doc11” to “Doc17” in the table of the example of FIG. 13 are registered in the derivation relationship DB 110. Assume that a comment is added to the attached document “Doc11” and a “response” operation is performed. In the document management server 10 that has received the ID-added document “Doc18” as a result of the “response” operation, as a result of the registration restriction information search process (step S20 in FIG. 7, FIG. 8), the document “Doc18” is the parent. The registration restriction information set for a document “Doc11” is acquired. Since the operation type of the document “Doc18” is “response”, restriction processing (step S30 in FIG. 7) is performed according to “child: response: reference setting to latest version” in the acquired registration restriction information. In the restriction process of this example, the registration restriction processing unit 136 first registers the meta information of the ID-added document “Doc18” in the derivation relation DB 110 and the document content in the document DB 100. The record with the management ID “Doc18” in FIG. 13 is an example of a record registered in the derivation relationship DB 110 at this time. In the record with the management ID “Doc18”, the parent ID is “Doc11” and the operation type is “response”. This registration process is similar to the registration process for ID-added documents that are not subject to the registration restriction process. Furthermore, the registration restriction processing unit 136 newly generates a record representing reference information for the ID-added document “Doc18” that is the target of restriction processing in the derivation relationship DB 110. As the value of the parent ID of the new record, the management ID of the latest document is set. The management ID of the latest version document is retrieved by executing the descendant search process of the procedure illustrated in FIG. 10 as in the above example referring to FIG. 5B or FIG. In addition, the registration restriction processing unit 136 generates a management ID of a new record representing the reference information, and sets the generated value as the management ID value of the record. For example, the registration restriction processing unit 136 generates a new management ID by performing the same processing as the ID assignment unit 202 of the document operation unit 200 of the client terminal 20. The record of the management ID “Doc19” in the table of the example of FIG. 13 is an example of a new record registered as described above. In the record of the management ID “Doc19”, the value of the parent ID is set to the management ID “Doc17” of the latest version document, and the “reference information” item includes the ID-added document “Doc18” subject to registration restriction. A management ID is registered. FIG. 14 shows an example of a tree structure formed by the derivation relationship of the table in the example of FIG.

  In the example of various processes of the document registration unit 130 described above, the tree structure of the derivation relationship is scanned and updated every time the management ID of the latest document is required in the restriction process (step S70 in FIG. 7). A process for searching the management ID of the version document is performed. In another example, the management ID of the latest version document at that time may be stored in the derivation relationship DB 110 in association with the root node of the tree structure of the document derivation relationship (the node of the “new registration” operation). Good. In the case of this example, for example, when registering an ID-added document whose operation type is “revision registration” in the derivation relationship DB 110, the ID is associated with the management ID of the document of the root node of the tree structure to which the ID-added document belongs. The management ID of the document with ID of the “revision registration” operation is registered in the derivation relationship DB 110 as the management ID of the latest version document. In this example, in the restriction process, the registration restriction processing unit 136 refers to the record in the derivation relation DB 110 corresponding to the root node of the tree structure to which the parent document of the ID-added document to be processed belongs, and sets the management ID of the latest version document. get.

  The processing of the document registration unit 130 of the document management server 10 when receiving an ID-added document from the client terminal 20 has been described above. Next, an example of processing performed by the request processing unit 140 of the document management server 10 when a service request is received from the client terminal 20 will be described. In the following, an example of processing in response to a service request that requests to provide information related to a comment corresponding to a management ID specified in the service request or a document derived from the document will be described. .

  Referring to FIG. 15, first, the request processing unit 140 extracts the management ID of the designated document from the service 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 the descendant search process described with reference to FIG. 10 for each child ID.

  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 stored in the intermediate result list. The request processing unit 140 determines whether or not a record satisfying the search condition specified in the service request exists in the intermediate result list (step S5). In this example, a search condition for extracting a record related to adding a comment to a document is specified in the service request. For example, a search condition “operation type is“ response ”” is specified. Further, for example, when the document registration unit 130 performs a restriction process for registering reference information to a document as a result of a “response” operation for an old version document as a child of the latest version document (see FIG. 13), the search condition is ““ The operation type may be “response” ”or“ the value of the reference information item is not NULL ”. If there is a record that satisfies the search condition (YES in step S5), the request processing unit 140 provides comment information included in the document corresponding to the record that satisfies the search condition as a search result (step S6). For example, the request processing unit 140 may extract and provide the comment information portion from the document content of the corresponding document, or may provide all of the document content of the corresponding document. Furthermore, part or all of the content of the record of the corresponding document derivation relationship DB 110 may be sent to the client terminal 20. Further, for example, when a record including reference information to the document of the “response” operation (for example, a record with the management ID “Doc19” in FIG. 13) is acquired as a record that satisfies the search condition, the request processing unit 140 refers to the reference Comment information included in the document represented by the information is provided as a search result. 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).

  In the processing of various examples of the document registration unit 130 described with reference to FIGS. 7 to 14, the latest version of documents derived from a document of a certain “new registration” operation (the latest “revision registration” operation). When a “revision registration” operation or a “response” operation is performed on a document corresponding to an ancestor in the tree structure of the derivation relationship, the operation result document is not registered in the document management server 10. (FIG. 5B), or registered in the document management server 10 so as to be searchable by searching the child of the latest version document (FIGS. 11 and 13). Therefore, after registering the latest version of the document, search for the document that corresponds to the ancestor of the latest version of the document for information about operations performed on the documents included in the tree structure of the derivation relationship to which the latest version of the document belongs. Without searching, it is obtained simply by searching for a document corresponding to a descendant of the latest version of the document.

  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. As shown in FIG. 16, for example, the computer includes 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 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. It is a figure which shows the example of the data content of derivation relation DB after progress for a fixed time from the state illustrated to FIG. 5A. FIG. 5B is a diagram schematically representing a tree structure formed by a management ID group in the data content illustrated in FIG. 5B. It is a flowchart which shows the example of the procedure of the process which a document registration part performs. It is a flowchart which shows the example of the procedure of the process which searches registration restriction information. It is a flowchart which shows the example of the procedure of a process which sets registration restriction information. 6 is a flowchart illustrating an example of a procedure of descendant search processing performed in the document management server 10. It is a figure which shows the other example of the data content of derivation relation DB. 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 other example of the data content of derivation relation DB. FIG. 14 is a diagram schematically illustrating a tree structure formed by a management ID group in the data content illustrated in FIG. 13. It is a flowchart which shows the example of the procedure of the process which a request process part performs. It is a figure which shows the 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, 134 Registration restriction determination unit, 136 Registration restriction processing unit, 140 Request processing unit, 200 Document operation unit, 202 ID allocation unit, 204 Derived relationship incorporation unit, 210 Registration processing unit, 300 Document with ID, 310 Meta Information, 320 document content.

Claims (6)

A registration unit that receives from the information processing apparatus information about a derivation relationship in which the first document is a parent and a second document that is a result of an operation on the first document is a child; A registration unit that receives an operation type and a time for the first document from the information processing apparatus, and registers the operation type and a time in association with the second document in the storage unit;
In the tree structure represented by the group of derivation relations registered in the storage unit and to which the first document in the derivation relation information received by the registration unit from the information processing apparatus belongs, the first document is A determination unit that determines whether the latest version document that is a document associated with the latest revision operation among documents included in the tree structure corresponds to an ancestor;
When the determination unit determines that the first document corresponds to an ancestor in the tree structure with respect to the latest document, information regarding an operation on the first document is stored in the latest document in the tree structure. A processing unit that performs processing for associating;
Equipped with a,
The processing unit is a case where the determination unit determines that the first document corresponds to an ancestor in the tree structure with respect to the latest document, and the registration unit has the derivation relationship from the information processing apparatus. When the type of operation received together with information corresponds to a response operation, the process for associating is performed.
Document management device comprising a call. In the processing for associating, the information processing apparatus transmits information prompting a user to perform an operation of the type of operation received by the registration unit from the information processing apparatus together with the derivation relation information on the latest document. Including processing to output
The document management apparatus according to claim 1 . The process for associating is a process of registering in the storage unit derivation relationship information indicating that the second document in the received derivation relationship information is a child of the latest document.
The document management apparatus according to claim 1 . In the process for associating, the reference information to the second document in the received derivation relationship information is generated and registered in the storage unit, and the latest document is a parent and the reference information is a child. It is a process of registering derivation relationship information in the storage unit.
The document management apparatus according to claim 1 . A registration step of receiving information of a derivation relationship having the first document as a parent and the second document as a child as a result of the operation on the first document from the information processing apparatus and registering the information in the storage unit; A registration step of receiving an operation type and time for the first document from the information processing apparatus and registering the operation type and time in association with the second document in the storage unit;
In the tree structure represented by the group of derivation relations registered in the storage unit and to which the first document in the derivation relation information received by the registration unit from the information processing apparatus belongs, the first document is A determination step of determining whether the latest version document that is a document associated with the latest revision operation among the documents included in the tree structure corresponds to an ancestor;
When it is determined in the determination step that the first document corresponds to an ancestor in the tree structure with respect to the latest document, information regarding an operation on the first document is stored in the latest document in the tree structure. A processing step for performing processing for associating;
To the computer ,
The processing step is a case where it is determined in the determination step that the first document corresponds to an ancestor in the tree structure with respect to the latest version document, and the derivation relationship is determined from the information processing apparatus in the registration step. When the type of operation received together with information corresponds to a response operation, the process for associating is performed.
Document management program, wherein a call. An information processing device and a document management device;
The information processing apparatus includes:
Derivation relationship information having a first document as a parent and a second document as a child as a result of an operation on the first document, and an operation type and time for the first document, as the document management apparatus A transmission unit for transmitting to,
The document management apparatus includes:
A registration unit that receives the derivation-related information from the information processing apparatus and registers the information in the storage unit, and further receives an operation type and a time for the first document from the information processing apparatus, and And a registration unit that registers the time in the storage unit in association with the second document;
In the tree structure represented by the group of derivation relations registered in the storage unit and to which the first document in the derivation relation information received by the registration unit from the information processing apparatus belongs, the first document is A determination unit that determines whether the latest version document that is a document associated with the latest revision operation among documents included in the tree structure corresponds to an ancestor;
When the determination unit determines that the first document corresponds to an ancestor in the tree structure with respect to the latest document, information regarding an operation on the first document is stored in the latest document in the tree structure. A processing unit that performs processing for associating;
Bei to give a,
The processing unit is a case where the determination unit determines that the first document corresponds to an ancestor in the tree structure with respect to the latest document, and the registration unit has the derivation relationship from the information processing apparatus. When the type of operation received together with information corresponds to a response operation, the process for associating is performed.
Document management system, wherein a call.

Images