JP5309664B2 - Document management apparatus and program - Google Patents

Description

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

  Electronic documents (hereinafter also simply referred to as documents) such as text document data, audio data, and multimedia data are registered in a server, and the documents are provided in response to user requests. There is also known a system that provides an electronic document corresponding to an identifier input by a user by assigning a unique identifier to the electronic document. In another known system, when an electronic document is printed on paper, the identifier of the electronic document is encoded and embedded in the paper document, and the identifier embedded in the paper document is recognized when the paper document is copied. The electronic document corresponding to the identifier is acquired and printed on paper.

  In the system disclosed in Patent Document 1, the content copying machine reads a content ID from a copy original of the content in which the content ID is embedded, and manages the read content ID and copy event attribute information via the network. Send to center. The content ID management center acquires the original content from the received content ID, assigns a new content ID, records the content ID and copy event attribute information, and uses the new content ID as the original content. Then, it is embedded and returned to the copy request source. The content copying machine outputs it as a copy result. In this system, when the content ID management center issues a new content ID in response to the content ID received from the content copy machine, it records that the copy source of the new content ID is the received content ID. (For example, the end of the 41st paragraph of Patent Document 1).

  In the system disclosed in Patent Document 2, an ID is associated with a document, and when an operation such as browsing / copying / editing is performed on the document, a new ID is issued and associated with the document after the operation. Change the ID to the new ID. Then, log information including an ID newly associated with the document, an old ID, various attributes relating to operations such as a user and date / time, and the like is recorded. In this system, the derivation relationship of log information can be obtained from the correspondence relationship between the new and old IDs, and by tracing this derivation relationship, it is possible to provide the old version and the latest version of the document.

  On the other hand, as a general story, when a plurality of people collaborate on the same document, the editing result of one person may not be reflected in the editing of another person. For example, the following case is an example. That is, first, user A copies document D to his machine in order to edit document D on the common repository, and then user B likewise edits the same document D on the common repository. Copy the document to your machine. Next, user A edits document D to generate document Da, and then user B edits document D to generate document Db. Thereafter, the user A overwrites the document Da with the document D in the common repository in order to reflect the editing result. Thereafter, the user B overwrites the document Db with the document D in the common repository in order to reflect the editing result. When this exemplary procedure is performed, the document finally stored in the common repository is Db, and the editing result performed by the user A is not reflected in this document.

  In order to deal with such problems, a version management system called CVS (Concurrent Versions System) has been developed. In CVS, a file is version-managed by a server. When a file is copied from the server to a local machine, the version number at that time is recorded locally. When the update made on the local machine is reflected on the server, if a newer version than the recorded version number is registered on the server, a warning is issued and the update is not reflected on the server.

  Further, in Patent Document 3, when a server starts editing a document in a system that shares the same online document among a plurality of servers on the network, it notifies other servers of that fact. The notified server locks the document so that it cannot be edited.

  When CVS is applied to the system of Patent Document 2, the CVS version number is the ID of the system, the specific version of the document is log information having a specific ID, and the new version is new log information (corresponding to the original ID) New log information derived from the log information), respectively. According to this, a control is made such that “when a document is edited, a warning is issued if another log information derived from the log information already exists for the log information of the old ID”. It becomes possible.

JP 2002-016788 A JP 2007-4649 A Japanese Patent Laid-Open No. 11-272534

  However, in the system of Patent Document 2, a derivative attribute is generated even in an operation other than editing, for example, an operation in which document contents such as browsing and copying are not updated, so that a warning is issued even in a case unrelated to the editing result of others. Problems occur.

One aspect of the present invention is a receiving unit that receives, from an information processing device, a type of an operation performed on a first document and a second document that is a result of the operation, and the receiving unit If the type of operation received by the user does not correspond to editing, the type of operation and the second document as a result of the operation are associated with each other and registered in the storage device, and the first document First registration control means for performing control for further registering in the storage device a derivation relationship indicating that the parent of the second document is the first document when already registered in the storage device When the type of operation received by the receiving unit corresponds to editing, the operation of the ancestor document of the second document in the tree formed by the derivation relation group stored in the storage device Documents whose type is edit or register Identified as point document, the which is the type editing operation of the operation in the offspring of the origin document in the tree, when said second document than is present, the result of the operation and the type of the operation And a second registration control means for controlling to stop registering the second document and the derivation relationship to the storage device.

  In one aspect, the second registration control means performs an operation on a tree formed by the derivation relation group stored in the storage device when the type of the operation received by the receiving means corresponds to editing. An ancestor document closest to the second document whose type is an editing operation or a registration operation is specified as the origin document.

  In another aspect, the document management apparatus, when the second registration control unit stops registering the type of the operation, the second document as a result of the operation, and the derivation relationship in the storage device Requesting the information processing apparatus to register in the storage device whether or not to register the type of operation for which registration has been canceled, the second document as a result of the operation, and the derivation relationship; In response to a request, an instruction receiving unit that receives an instruction from the information processing device, and a registration request is received from the instruction receiving unit. And third registration means for registering the second document and the derivation relationship in the storage device.

  In yet another aspect, the document management apparatus, when the receiving unit receives memo information in association with the type of operation and the second document that is the result of the operation, the type of operation and the operation Memo registration means for registering the memo information in the storage device in association with the second document that is the result of the derivation and the derivation relationship, wherein the instruction accepting means When requesting an instruction as to whether or not to register the type and the second document as a result of the operation and the derivation relationship in the storage device, the type of operation among the descendants in the tree of the origin document is Provides memo information associated with a document that is an editing operation.

In still another aspect, the second registration control unit is configured such that when there is no document other than the second document, the operation type is an editing operation among the descendants in the tree of the identified document. The operation type, the second document as a result of the operation, and the derivation relationship are registered in the storage device.

  FIG. 1 is a block diagram illustrating an example of a schematic configuration of a document usage 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.

  An example of the client terminal 20 will be described with reference to FIG. A client terminal is a terminal used by a user to operate a document, such as a personal computer or a digital copying machine. As shown in FIG. 2, the client terminal 20 includes a document operation unit 200 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 perspective), 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 in accordance with a user instruction or edits the electronic document. Or When an operation is performed on a document, the document operation unit 200 outputs a document 300 with an identifier (ID) 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 time when the operation was performed, the type of the operation, the user (operator) who instructed the operation, but of course not limited to this. The types of operations include, for example, registration (registering a new document in this system), browsing, editing (changing or updating document contents), 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 editing completion time, the identification information of the user who instructed the editing, and “edit” as the type of operation are included.

  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. Accordingly, 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 representing a history of the operation. 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.

  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. As described above, each client terminal 20 registers the ID-added document 300, which 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. 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. In this case, 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 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, an example of 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 100, a derivation relationship DB 110, a document registration unit 130, and a request processing unit 140.

  The document DB 100 is a database (DB) 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 is 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.

  The document registration unit 130 registers the document contents in the ID-added document received from the client terminal 20 in the document DB 100 and the meta information in the derivation relationship DB 110. Among them, the derivation relationship registration unit 132 is in charge of registration of meta information.

  The derivation relationship DB 110 is a database that accumulates meta information mainly including derivation relationship information among such ID-added documents 300. FIG. 5 shows an example of data contents of the derivation relationship DB 110. One line of information in the table shown in FIG. 5 is a meta information record corresponding to one ID-added document 300. In this example, each item of the parent ID, the operation type, the operator, the operation time, and the content ID of the document content is registered in association with the management ID of each ID-added document 300. Of the items listed above, items other than the management ID / parent ID pair and the operation type are not limited to those illustrated. Items that are necessary for management purposes may be recorded.

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

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

  The history of documents shown in the examples of FIGS. 5 to 6 will be described in the order of time series as follows. This example shows a flow of work in which a certain user registers a document in this system, and another user performs editing operations such as addition, deletion, and change on the document.

  In this example, first, a “registration” operation of a document is executed on the user A's client terminal. The “registration” operation is an operation for registering a document that is not registered in the document management server 10 (that is, a document that does not have a management ID) in the server 10. In response to this operation, the ID-added document “1” including the meta information with the management ID “1”, the parent ID is empty, and the operation type is “registration” and the document content of the document is received from the client terminal of the user A Sent to the document management server 10. In response to this, the document management server 10 registers the document contents in the ID-added document “1” in the document DB 100 and the meta information in the derivation relationship DB 110. The registered document content is managed in association with the content ID “Content1”.

  Next, the user B accesses the document management server 10 from his / her client terminal 20 and copies the ID-added document “1”. In this case, the document management server 10 creates a copy of the ID-added document “1” designated by the user B, and assigns a new management ID “2” to the copy result document, thereby adding the ID. Document “2” is generated and provided to user B. The ID-added document “2” includes meta information 310 including items such as a management ID “2”, a parent ID “1”, an operation type “edit”, and an operator “B”. At this time, a derivation relationship indicating that the document “1” is derived from the document “1” is registered in the derivation relationship DB 110. The document content of the ID-added document “2” is the same as the ID-added document “1”.

  Next, when the user C edits the ID-added document “1” distributed from the user A, the ID-added document having the management ID “3” shown in FIG. 5 is registered in the document management server 10. When registering the editing result, the document registration unit 130 according to the present embodiment determines whether the editing result is a result of ignoring other editing results for the document first registered by the user A. . If the other editing result is ignored, the registration of the editing result is suspended and a warning is given to the user C that there is a possibility of ignoring the editing of the other person. This warning processing for ignoring editing will be described in detail later.

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

  Returning to the description of FIG. 4, the request processing unit 140 provides a service using the derivation relationship DB 110 in response to a service request including the management ID from the client terminal 20. As a service provided by the request processing unit 140, for example, there is a service for searching for the latest version of a document corresponding to the management ID in the service request. As another example, a service that provides log information about an ancestor document (original document) corresponding to the management ID in the service request or the ancestor can be cited. 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). As another example, there is a service for collecting the entry results of each user for the original form corresponding to the management ID.

  The service request is issued based on the ID-added document held in the client terminal 20. For example, when a 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. In addition to the management ID and the code indicating the service, 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. Also good.

  As another example, such a service menu may be associated with an object type called an ID-added document and registered in the operating system of the client terminal 20.

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

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

  The system configuration of the embodiment has been described above. Next, the processing procedure of the document registration unit 130 will be described with reference to FIG. This procedure is executed when an ID-added document is received from the client terminal 20. In this procedure, the document registration unit 130 determines whether or not the value of the operation type attribute in the received ID-added document is “edit” (S1). If it is not “edit”, the document with ID is registered in the document DB 100 and the derivation relationship DB 110 (S2). On the other hand, in the case of “edit”, an ID-added document (meta information) having the value of the parent ID attribute of the ID-added document as a management ID is specified from the derivation relationship DB 110. Then, an ID-added document whose operation type reaches “edit” or “registration” first in the retroactive process is traced back to the ancestor direction from the ID-added document that has received the derivation relation tree as a starting document. Specify (S3). That is, in this step, the nearest ancestor document whose operation type is “edit” or “registration” as viewed from the received document is specified as the origin document.

  Then, the descendants of the specified origin document are searched according to a well-known tree search method, and an ID-added document whose operation type is “edit” is searched for among the descendants (S4). Here, although the operation type of the ID-added document that triggered the start of this procedure is “edit”, the ID-added document is not registered in the document DB 100 and the derivation relationship DB 110 at this stage. A corresponding document is searched from ID-added documents other than ID-added documents. As a result of the search, it is determined whether there is a corresponding document (S5). If there is no corresponding document, the received ID-added document is registered in the document DB 100 and the derivation relationship DB 110 as a trigger for starting this procedure ( S2). On the other hand, if it is determined in S5 that there is a corresponding document, warning information is transmitted to the client terminal 20 that is the transmission source of the ID-added document that triggered the start of this procedure (S6). The warning information is, for example, a message indicating that the ID-added document has been edited while ignoring other editing results that have already been performed (that is, a document in which the operation result found in S4 is editing). In this case, the document management server 10 cancels or temporarily suspends the registration of the ID-added document as the trigger in the document DB 100 and the derivation relationship DB 110.

  As described above, in the above procedure executed by the document registration unit 130, a document obtained by editing the document content separately from the ID-added document received from the client terminal 20 exists in documents derived from the same document content. In this case, the person who requests registration is notified that another editing result exists. As a result, it is possible to reduce inconvenience due to registration of an editing result (that is, an ID-added document received from the client terminal 20) ignoring the other editing results.

  Further, in S4 of this procedure, since operations other than editing or registration (that is, operations in which the document content is not changed) are not searched, the document registration unit 130 does not know how many operations in which the document content has not been changed in the past. Do not warn about

  Further, in the procedure of FIG. 7, in S3, the most recent document whose operation type is editing (or registration) among the ancestors including the parent document of the ID-added document received from the client terminal 20 is specified as the starting document. The document whose operation type is edit was searched from the descendants of this origin document. In this way, by setting the latest document whose operation type is editing or registration as the starting document, it is not necessary to consider a group of other editing series derived from the editing results of ancestors, so the search range is narrowed. Can do. However, this is only an example, and a document whose operation type is edit (or registration) of an ancestor that is not the nearest may be used as the starting document.

  The operation type “edit” in the above refers to general operations in which the document content is changed. Therefore, even if the operation type name is not “edit”, it corresponds to “edit” as long as the operation changes the document contents. Similarly, the operation type “registration” refers to an operation for registering in the document management server 10 a document that has not been registered in the document management server 10 and does not have a parent ID. That is, the operation type when the document content is changed for the document registered in the document management server 10 and the result is registered is “edit”. Depending on the design of the system, there may be a plurality of operation types whose document contents are changed. In this case, in S4 of the above procedure, a document corresponding to one of the plurality of operation types can be searched. That's fine. Similarly for S1, it may be determined whether or not the operation type of the ID-added document corresponds to one of the plurality.

  Consider a case where the above-described procedure is applied to the document operation flow illustrated in FIGS. For example, when editing is performed by the user C, which is the third operation, the determination result of S1 is Yes (positive), and the document “1”, which is the most recent document whose operation type is editing or registration in S3, is the starting document. Identified as However, only the document “2” whose operation type is “duplicate” exists in the descendants of the document “1”, and there is no document whose operation type is “edit”. Therefore, the determination result of S5 is No. Thus, the document “3” which is the editing result of the user C is registered in the document DB 100 and the derivation relationship DB 110 in S2.

  Next, a case where the procedure of FIG. 7 is applied to the document operation flow illustrated in FIGS. 8 and 9 will be described.

  In the flow illustrated in FIGS. 8 and 9, the user A first registers the document “1” in the document management server 10 and then edits the document. Next, the documents “2” as the editing result are copied by the users B and C to their client terminals 20 (document “3” and document “4”). User B is editing document “3” (document “5”). FIG. 9 shows the data contents of the derivation relationship DB 110 at this stage.

  Next, consider a case where user C has edited document “4”. In this case, the determination result of S1 in the procedure of FIG. 7 is Yes, and the document “2” that is the latest document whose operation type is editing or registration is specified as the starting document in S3. Since the document “5” whose operation type is “edit” already exists in the descendants of the document “2”, the determination result in S5 is Yes. Therefore, the editing result of the user C is not registered in the document DB 100 and the derivation relationship DB 110, and the user C is warned to ignore editing in S6.

  Next, a modified example will be described. In this modification, the client terminal 20 is provided with means for inputting a user's memo regarding an operation performed on the document by the user. The memo can be used to explain the operation to the user or other users. For example, when a user edits a document registered in the document management server 10 by a “registration” operation for a specific section, it can be input as a memo. The input memo is incorporated into the ID-added document by the document operation unit 200 and registered in the derivation relationship DB 110 of the document management server 10.

  Then, as shown in FIG. 10, when the document management server 10 warns the user that the edit is ignored (when the determination result in S <b> 5 is Yes), the operation type derived from the origin document is “edit”. Memo information (if there are a plurality of relevant documents, all relevant documents) are provided (S6a). Corresponding to this warning, user interface means (for example, a button on a web page) for inputting an instruction as to whether or not to register the editing result of the user to be processed is assigned to the user ( Client terminal). The user who receives the warning, the memo information, and the user interface means determines whether or not to register his / her editing result in the document management server 10 with reference to the memo information even though other editing results exist. Then, the result of the determination is input to the user interface means. The document management server 10 receives the user's input and determines whether or not the input is an instruction for registration (S7). If the input instructs registration, the ID-added document to be processed is registered in the document management server 10 (S2). On the other hand, if the user registration is not instructed, the process ends without registering the ID-added document to be processed in the document management server 10.

  In addition, the processing content of the step which was not demonstrated above among the processing procedures of FIG. 10 may be the same as the processing content of the step of the same code | symbol shown in FIG.

  A specific example of processing according to the procedure of FIG. 10 will be described by taking the flow of operations of FIGS. 11 and 12 as an example.

  In the flow illustrated in FIGS. 11 and 12, the user A first registers the document “1” in the document management server 10. Next, the user B copies the document “1” to his / her client terminal 20 and edits the document “2” as a copy result. Here, the user B inputs memo information indicating that the editing result is limited to a specific group “YY section”, and as a result, the document management server 10 receives “YY section usage”. "3" including memo information "is registered.

  Thereafter, when the user A edits the document “1”, the document “3”, which is the editing result, already exists in the descendant of the document “1” (origin document) at that time. Provides a user interface screen (warning screen) for notifying the existence of the document “3” and the memo information “YY assignment” to the user A (S6a). The user A can determine from the memo information that, for example, the already existing editing result document “3” is “YY assignment”, so that it is not necessary to consider it in his editing. In this case, the user A instructs to register the editing result on the user interface screen. Upon receiving this instruction, the document management server 10 registers the editing result (document “4”) in the document DB 100 and the derivation relationship DB 110.

  Thereafter, when the user A further edits the document “4”, the document “5” is transmitted from the client terminal 20 of the user A to the document management server 10. In this case, when viewed from the document “5”, the nearest ancestor whose operation type is editing or registration is the document “4”, which is the starting document. In this case, since the object of monitoring for editing is limited to the descendants of the document “4”, no warning is issued even if the document “3” exists. Therefore, the document “5” is registered in the document management server 10.

  If there is no memo in the document whose operation type is edit in the descendant of the origin document, the user interface screen may be provided in the same manner as described above, and the user may be instructed to register, Registration may be canceled automatically without receiving instructions.

  By providing the memo information to the user as in this modification, the user can determine whether or not to register the editing result.

  In the embodiment and the modification exemplified above, the management ID is issued at each client terminal 20, but the document management server 10 may issue the management ID instead. In this case, when an operation is performed on the ID-added document, the client terminal 20 includes the management ID in the ID-added document before the operation as the parent ID 314, and further includes log information 316 about the operation and the document content after the operation. 320, the management ID 312 generates blank document data and sends it to the document management server 10. The document management server 10 assigns a new management ID to the received document data, and registers information included in the management ID and the document data in the document DB 100 and the derivation relationship DB 110. Further, 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 the above-described embodiment and the modification can be executed in the same manner.

  In the above embodiment and modification, 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. Only the ID may be stored, and 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.

  When the document management server 10 assigns a management ID, the document management server 10 generates a management ID corresponding to the acquisition operation, associates the management ID with the document, and provides it to the client 20. The log information (operation time, operator, etc.) about the acquisition operation, the original management ID (that is, the 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 above processing, the derivation relationship between operations is accumulated in the document management server 10.

  On the other hand, if 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 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 and the client terminal 20 according to the exemplary embodiment and the modifications described above are realized by causing a general-purpose computer to execute a program representing the processing of each functional module described above, for example. Here, for example, as shown in FIG. 13, the computer includes, as hardware, a microprocessor such as a CPU 1000, a memory (primary storage) such as a random access memory (RAM) 1002 and a read only memory (ROM) 1004, an HDD ( HDD controller 1008 that controls (hard disk drive) 1006, various I / O (input / output) interfaces 1010, network interface 1012 that performs control for connection to a network such as a local area network, and the like via bus 1014, for example. Connected to each other. In addition, for example, a disk drive 1016 for reading from and / or writing to a portable disk recording medium such as a CD or a DVD, a portable memory of various standards such as a flash memory via the I / O interface 1010 is connected to the bus 1014. A memory reader / writer 1018 for reading from and / or writing to the nonvolatile recording medium may be connected. A program in which the processing contents of each functional module exemplified above are described is stored in a fixed storage device such as a hard disk drive via a recording medium such as a CD or DVD, or via a communication means such as a network, and stored in a computer. Installed. The program stored in the fixed storage device is read into the RAM 1002 and executed by a microprocessor such as the CPU 1000, whereby the functional module group exemplified above is realized. Some or all of these functional module groups are used as hardware circuits such as dedicated LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), or FPGA (Field Programmable Gate Array). It may be configured.

It is a block diagram which shows the example of schematic structure of a document utilization management system. It is a block diagram which shows the example of an internal structure of a client terminal. It is a figure which shows typically the example of the data structure of a document with ID. It is a block diagram which shows the example of an internal structure of a document management server. It is a figure which shows the example of the data content of derivation relation DB. FIG. 3 is a diagram schematically representing a tree structure formed by a group of derivation relationships of an ID-added document. It is a flowchart which shows an example of the process sequence of a document registration part. FIG. 10 is a diagram schematically illustrating another example of a tree structure formed by a derivation relationship group of an ID-added document. It is a figure which shows the example of the data content of derivation relation DB corresponding to the tree structure of FIG. It is a figure which shows an example of the procedure of the completed form collection | recovery process in a modification. FIG. 10 is a diagram schematically illustrating another example of a tree structure formed by a derivation relationship group of an ID-added document. It is a figure which shows the example of the data content of derivation relation DB corresponding to the tree structure of FIG. It is a figure which shows an example of the hardware constitutions of a computer.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Document management server, 20 Client terminal, 30 Network, 100 Document DB, 110 Derivation relation DB, 130 Document registration part, 132 Derivation relation registration part, 140 Request processing part, 200 Document operation part, 202 ID allocation part, 204 Derivation relation Built-in unit, 210 Registration processing unit, 300 Document with ID.

Claims (6)

Receiving means for receiving, from the information processing apparatus, the type of operation performed on the first document and the second document as a result of the operation;
If the type of operation received by the receiving means does not correspond to editing, the type of operation and the second document that is the result of the operation are registered in the storage device in association with each other, and the first If the document is already registered in the storage device, the first control is performed to further register the derivation relationship indicating that the parent of the second document is the first document in the storage device. Registration control means;
When the type of operation received by the receiving unit corresponds to editing, the type of operation among the ancestor documents of the second document in the tree formed by the derivation relation group stored in the storage device is When a document that is an editing operation or a registration operation is specified as a starting document, and there is a document other than the second document whose operation type is an editing operation among descendants of the starting document in the tree, Second registration control means for controlling to stop registering the second type of the operation and the second document as a result of the operation and the derivation relationship in the storage device;
A document management apparatus comprising:   When the operation type received by the receiving unit corresponds to editing, the second registration control unit is configured such that the operation type is an editing operation in a tree formed by the derivation relation group stored in the storage device. The document management apparatus according to claim 1, wherein an ancestor document closest to the second document that is a registration operation is specified as the origin document. When the second registration control unit stops registering the type of the operation, the second document as a result of the operation, and the derivation relationship in the storage device, the information processing apparatus Requests an instruction as to whether or not to register the type of the operation for which registration has been canceled, the second document as a result of the operation, and the derivation relationship in the storage device, and instructs the information processing device in response to the request. Instruction accepting means for accepting,
When receiving an instruction for registration from the instruction receiving means, a third document for registering in the storage device the type of operation for which registration has been canceled, the second document as a result of the operation, and the derivation relationship. Registration means,
The document management apparatus according to claim 1 or 2. When the receiving means receives memo information in association with the operation type and the second document that is the result of the operation, the operation type and the second document that is the result of the operation and the derivative Memo registration means for registering the memo information in the storage device in association with the relationship,
The instruction accepting means, when requesting an instruction whether or not to register in the storage device the type of the operation that has been canceled, the second document that is the result of the operation, and the derivation relationship, Providing memo information associated with a document whose operation type is an editing operation among the descendants in the tree of the origin document,
The document management apparatus according to claim 3. When there is no document other than the second document in which the operation type is an editing operation among the descendants in the tree of the identified document, the second registration control unit determines the operation type and The document management apparatus according to claim 1, wherein the second document and the derivation relationship as a result of the operation are registered in the storage device. Computer
Receiving means for receiving the type of operation performed on the first document and the second document as a result of the operation from the information processing apparatus;
If the type of operation received by the receiving means does not correspond to editing, the type of operation and the second document that is the result of the operation are registered in the storage device in association with each other, and the first If the document is already registered in the storage device, the first control is performed to further register the derivation relationship indicating that the parent of the second document is the first document in the storage device. Registration control means,
When the type of operation received by the receiving unit corresponds to editing, the type of operation among the ancestor documents of the second document in the tree formed by the derivation relation group stored in the storage device is When a document that is an editing operation or a registration operation is specified as a starting document, and there is a document other than the second document whose operation type is an editing operation among descendants of the starting document in the tree, Second registration control means for controlling to stop registering the type of the operation, the second document as a result of the operation, and the derivation relationship in the storage device;
Program to function as.

Images