JP2008181446A - Document management device, information processor, document management system, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technique for limiting documents to be provided when retrieving and providing documents on the basis of a derivation relation. <P>SOLUTION: When performing an operation on a document with an ID including a management ID, a client generates a new document with the ID, which includes a newly generated management ID, the original management ID (master ID), log information after the operation, and document contents after the operation, and sends it to a server. When a classification of the operation corresponds to a preliminarily registered classification, an "open" attribute is built in the log information. A document registration part 130 of the server registers the sent management ID, master ID, log information, and document contents with a derivation relation DB 110 and a document DB 100. When a user uses a document with an ID to request retrieval, a request processing part 140 traces a derivation relation group in the derivation relation DB 110 with this document as a start point and provides documents meeting a retrieval condition, out of documents to which the "open" attribute is set. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

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

  An electronic document (hereinafter simply referred to as a document) such as text document data, audio data, and multimedia data is registered in a server, and the document is provided in response to a user request. There is also known a system that provides a unique identifier to an electronic document and provides the electronic document corresponding to the identifier input by the user. In 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, a content copying machine reads a content ID from a copy original of a content in which the content ID is embedded, and manages the content ID and the information of the copy event attribute 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 according to the content ID received from the content copy machine, it records that the new content ID copy source is the received content ID. (For example, the 41st paragraph end of patent document 1).

  In the system disclosed in Patent Document 2, when an electronic document is printed on paper, the document identifier of the electronic document is embedded and printed. When a paper document is input, the system extracts a document identifier from the paper document, and downloads and prints an electronic document corresponding to the document identifier. Also, in this system, when a downloaded electronic document is updated, the updated electronic document is registered in association with a new document identifier, and a paper document in which the new document identifier is embedded is printed.

  In the system disclosed in Patent Document 3, handwritten edits on a paper document are directly reflected in the electronic document, and the updated version series of the electronic document is held as a tree structure having the electronic document as a node. There is also disclosed an example of a document history tree in which a document or file is a node and a version generated by updating the document or file can be managed as a branched version. Such a version control system is widely known as CVS (Concurrent Versions System). Patent Document 3 discloses a method of managing a document history tree so that a history related to updating an electronic document has an electronic document before update as a parent and an electronic document after update as a child.

  In the system disclosed in Patent Document 4, the terminal device reads the content ID from a copy of the content in which the content ID is embedded or a part thereof, and transmits the content ID and search auxiliary information to the content ID management center. To do. When the content ID management center receives the content ID and the auxiliary search information, the content ID management center returns the original content corresponding to the content ID or the related content to the terminal device.

Japanese Patent No. 3383793 JP 2006-053686 A JP-A-2005-135211 JP 2002-014978 A

  By the way, when an operation is performed on a document, a derivation relationship indicating that the document after the operation is derived from the document before the operation is recorded, and a document having a derivation relationship with respect to the specified document is recorded in the record. A service that is sought and provided based on this is considered. However, if an unlimited number of documents derived according to the derivation relationship are provided, an inconvenient document may be disclosed.

  The present invention provides a technique for restricting documents to be provided when documents are retrieved and provided based on a derivation relationship.

  The invention according to claim 1 is a second document obtained as a result of the operation of the first document from the information processing apparatus, disclosure attribute information indicating whether or not the second document is a disclosure target, Are registered in the storage unit in association with each other, and when the first document is already registered in the storage unit, the parent of the second document is the first document. In the tree group formed by the group of derivation relations stored in the storage unit in accordance with a registration instruction for further registering the derivation relation indicating that in the storage unit, and a search instruction specifying the target document and the search condition A search result providing unit that provides, as a search result, a document that satisfies the search condition and that corresponds to the disclosure attribute information indicating that it is a disclosure target among documents included in a tree to which the target document belongs. Device.

  The invention according to claim 2 is the invention according to claim 1, wherein the registration unit further includes search boundary information indicating whether or not a search boundary is between the second document and the first document. The subtree group received from the information processing apparatus and registered in the storage unit in association with the second document, the search result providing unit being delimited by the search boundary in the tree group formed by the derivation relation group Among the documents belonging to the subtree to which the target document belongs, a document that satisfies the search condition and corresponds to the disclosure attribute information indicating that it is a disclosure target is provided as a search result.

  The invention according to claim 3 is a second document obtained as a result of the operation of the first document from the information processing device, disclosure attribute information indicating whether or not the second document is a disclosure target, Are registered in the storage unit in association with each other, and when the first document is already registered in the storage unit, the parent of the second document is the first document. A step of further registering a derivation relationship indicating that it is present in the storage unit, and in response to a search instruction specifying a target document and a search condition, the tree group in the tree group formed by the derivation relationship group stored in the storage unit A program for causing a computer to execute, as a search result, a document corresponding to disclosure attribute information that satisfies the search condition and is a disclosure target among documents included in a tree to which the target document belongs. is there.

  The invention according to claim 4 is an operation execution unit that performs an operation on a document, and a determination information storage that stores, for each operation, determination information that defines whether a document obtained as a result of the operation is to be disclosed. And when the operation execution unit executes an operation on the first document, the determination is made on the disclosure attribute information indicating whether or not the second document obtained as a result of the operation is to be disclosed And a transmission unit that generates the information based on the information and transmits the disclosure attribute information to the document management apparatus in association with the second document.

  The invention according to claim 5 is an operation execution unit that performs an operation on a document, and a determination information storage that stores, for each operation, determination information that defines whether or not a document obtained as a result of the operation is to be disclosed. And when the operation execution unit executes an operation on the first document, the determination is made on the disclosure attribute information indicating whether or not the second document obtained as a result of the operation is to be disclosed It is a program for causing a computer to function as a transmission unit that is generated based on information and transmits the disclosed attribute information to the document management apparatus in association with the second document.

  The invention according to claim 6 includes an information processing device and a document management device, and the information processing device discloses an operation execution unit that executes an operation on the document, and a document obtained as a result of the operation for each operation. A determination information storage unit that stores determination information that defines whether or not to be a target, and a second result obtained as a result of the operation when the operation execution unit executes an operation on the first document A transmission unit that generates disclosure attribute information indicating whether or not a document is to be disclosed based on the determination information, and transmits the disclosure attribute information to the document management apparatus in association with the second document. The document management device includes a second document obtained as a result of the operation of the first document from the information processing device, disclosure attribute information indicating whether or not the second document is a disclosure target, Registered and registered in the storage unit in association with each other. If the first document is already registered in the storage unit, a derivation relationship indicating that the parent of the second document is the first document is further registered in the storage unit. A document included in a tree to which the target document belongs in a tree group formed by a derivation relation group stored in the storage unit, in response to a search instruction that specifies a registration unit, a target document, and a search condition, A search result providing unit that provides, as a search result, a document that satisfies the search condition and that corresponds to the disclosure attribute information indicating that it is a disclosure target.

  According to the first aspect of the present invention, it is possible to control whether or not to provide the operation result document as a search result in accordance with the disclosure attribute information from the information processing apparatus.

  According to the invention which concerns on Claim 2, the search range with respect to a search instruction | indication can be further limited according to the search boundary information from information processing apparatus.

  According to the third aspect of the present invention, it is possible to control whether or not to provide the operation result document as a search result in accordance with the disclosure attribute information from the information processing apparatus.

  According to the fourth aspect of the present invention, it is possible to instruct the document management apparatus whether or not to disclose the document of the operation result in accordance with the operation executed on the document.

  According to the invention which concerns on Claim 5, according to operation performed with respect to a document, it can be instruct | indicated to a document management apparatus whether the document of the operation result may be disclosed.

  According to the sixth aspect of the present invention, it is possible to control whether or not to provide the operation result document as a search result in accordance with the disclosure attribute information from the information processing apparatus.

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

  The client terminal 20 will be described with reference to FIG. A client terminal is a terminal used by a user to operate a document, such as a personal computer or a digital multifunction peripheral. 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 log information 316 can also include a “public” attribute indicating whether or not the ID-added document 300 is a public (shared) target. For example, if the “publish” attribute value of an ID-added document to be published is “1” and the “publish” attribute value of an ID-added document that is not to be published is “0”, the “publish” attribute is “0”. The ID-added document can be prevented from being opened to anyone other than a privileged user such as an operator or administrator who has performed an operation for generating the document.

  Note that the value of the “public” attribute is determined according to the type of operation. The type of operation serving as a reference for determining the public attribute value may be the type of operation executed by the document operation unit 200 or the type of operation according to the log recording purpose classification. Which one is to be used may be set in the document operation unit 200.

  A specific example of the meta information 310 generated by the document operation unit 200 is shown below.

[Example 1]
<metadata sid = "Doc1" date = "2006-10-01T10: 00" method = "register" filename = "aaa.doc" user = "user1"/>

  Here, the sid attribute is a management ID, the date attribute is an operation date and time, and the method attribute is an operation type. The filename attribute is the file name of the ID-added document, and the user attribute is user identification information of the user who has instructed the operation. The method attribute value “register” in Example 1 is an operation type name indicating a new document registration operation (not registered in the document management server 100). Since a new document is registered, the pid attribute indicating the parent ID is omitted. Instead of omitting, an attribute such as pid = "null" indicating that there is no parent ID may be explicitly incorporated. Further, in this example, since the document registered by the new document registration is not made public, the shared attribute indicating whether or not it is made public is omitted. Instead of omitting it, you may explicitly incorporate an attribute indicating that it is not a public object, such as shared = "0".

  Also, in Example 2 shown below, when a user whose user identification information is “user4” performs an operation of reading a paper document in which the management ID “Doc2” is embedded with a scanner and “registering as an approved version” Meta information 310 to be generated.

[Example 2]
<metadata sid = "Doc4" pid = "Doc2" date = "2006-10-01T11: 28" method = "update" filename = "200610011128.jpg" user = "user4" shared = "1"/>

  Here, the method attribute value “update” indicates an update operation. In this example, the file name of the scanned image is a value automatically generated based on the operation date and time. This example is an example in which a document registered by the update operation is a publication target, and the shared attribute value is a value “1” indicating that the document is a publication target.

  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. Further, the derivation relationship incorporating unit 204 holds information indicating whether or not a document as a result of the operation of the type is to be disclosed for each operation type, and determines a shared attribute value based on this information. . 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 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, and in this case, the content ID may be incorporated in the meta information 320. Further, instead of the content ID, the document content 320 may be stored in the document DB 100 in association with the management ID of the ID-added document 300 corresponding to the document content.

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

  The derivation relationship DB 110 is a database that accumulates meta information mainly including derivation relationship information among such ID-added documents 300. FIG. 5 shows an example of data contents of the derivation relationship DB 110. One line of information in the table shown in FIG. 5 is a meta information record corresponding to one ID-added document 300. In this example, items of parent ID, node address, operation type, operator, operation date, “public” attribute, and document storage path 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, the operation date and time, and the public attribute have already been described. The node address indicates the position of the node corresponding to the management ID (document with ID) in the tree formed by the derivation relationship between documents with ID. In the notation of the node address, “/” indicates a tree depth hierarchy delimiter, and indicates the order between siblings derived from the same parent. For example, the node “/ 1” indicates a root node corresponding to a document registered by a new document registration operation. Further, the node “/ 1/1” represents the first child of the root node “/ 1”, and the node “/ 1/2” represents the second child of the root node “/ 1”. In order to avoid complication, FIG. 5 shows only a meta information record group belonging to one tree derived from one root node “/ 1”. A meta information record group of a plurality of trees can be registered, such as a tree derived from “1” and a tree derived from the root “/ 2”. The document storage path is a path name indicating a storage location of the document content 320 in the document DB 100. In the example of FIG. 5, the document content is registered in a folder “\ doc” in the E drive with a file name in which the filename attribute (file name) is continued after the date attribute (operation date and time). If the document DB 100 has a function of searching the document content 320 by the content ID, the content ID may be registered in the meta information record instead of the document storage path.

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

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

  The history of documents shown in the examples of FIGS. 5 to 6 will be described in the order of time series as follows. In this example, the flow of work in which a user registers a form (model document) such as an application form in this system, another user fills in the form, and registers the completed form in this system. Represents.

  In this example, first, a “registration” operation of a document (form) is executed at the client terminal of user1. The “registration” operation is an operation for registering in the server 10 a document that is not registered in the document management server 10 (that is, a document that does not have a management ID). In response to this operation, the ID-added document “Doc1” including the meta information with the management ID “Doc1”, the parent ID is empty, and the operation type is “registration” and the document content of the document is a document from the client terminal of user1. Sent to the management server 10. Here, since the “registration” operation is not the target of “publication”, the value of the “publication” attribute is not included in the meta information. In response to this, the document management server 10 registers the document contents in the ID-added document “Doc1” in the document DB 100 and meta information in the derivation relationship DB 110. Here, since the operation type is “register” and the parent ID is empty, the document management server 10 is not a child of the ID-added document already registered in the document management server 10, but is a new one. The node is determined to be the root (founder) of the tree, and the value of the node address (“/ 1” in this example) is set accordingly. In the following description, the registered document content is represented by “Content1” for identification. After that, user1 distributes the registered ID-added document to other users user2, user3,. 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 user2 prints the ID-added document “Doc1” using the document operation unit 200 of his / her client terminal. What is printed is the document content "Content1" or the document content resulting from editing. At this time, the document operation unit 200 embeds the management ID “Doc2” newly assigned to the paper document as the print result. The paper document in which the management ID is embedded in this way is called a paper document with an ID. Further, the client terminal generates an ID-added document “Doc2” as a result of printing and registers it in the document management server 10. The management ID in the meta information of the ID-added document is “Doc2” and the parent ID is “Doc1”. The operator is user2. The operation type is printing. Further, since the “print” operation is not the target of “publication”, the value of the “publication” attribute is not included in the meta information of the ID-added document. 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, and since it is the first child, the document “Doc2” The node address is “/ 1/1”.

  It should be noted that the ID-added document “Doc1” that was in the client terminal 20 of user2 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. In addition, the derivation relationship incorporating unit 204 changes the value of the operation type in the log information 316 to “print” that is the type of the current operation, changes the value of the operation time to the date and time of browsing, and Change the value to user2. The document content 320 is print data or a document file indicating the document content at the time when the print instruction is given.

  Thus, when the ID-added document “Doc1” is browsed, the ID-added document “Doc2” after browsing is replaced. 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. Note that user2 passes the print result paper document “Doc2” to another user, user4.

  Thereafter, another user user3 browses the ID-added document “Doc1” with the document operation unit 200 of his / her client terminal. The document content with the content ID “Content1” is browsed. The client terminal generates an ID-added document “Doc3” as a result of browsing and registers it in the document management server 10. Here, since the “browsing” operation is not the target of “publication”, the value of the “publication” attribute is not included in the meta information of the ID-added document. In the “browsing” operation, the document content is not changed, so the document content remains “Content1”. When an operation that does not change the document content is performed, the client terminal 20 may send an ID-added document with the document content omitted to the document management server 10. Note that the ID-added document “Doc1” in the client terminal 20 of user3 before this operation is replaced with the ID-added document “Doc3” 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. In addition, the derivation relationship incorporating unit 204 changes the value of the operation type in the log information 316 to “view” that is the type of the current operation, changes the value of the operation time to the date and time of the view, and Change the value to user3. Since the current operation is browsing, the document content 320 does not change.

  Next, user4 writes the ID-added paper document “Doc2” received from user2, sets the written paper document in the scanner, and selects “read” from the operation menu of the reading control software on the client terminal 20. Suppose you select the “Register as approved version” operation. Then, the reading control software reads the paper document by controlling the scanner, and the ID-added document “Doc4” including the image data of the reading result as the document content (hereinafter, this document content is named “Content2” for identification). Is generated and sent to the document management server 10 and stored in the client terminal 20. The management ID included in the meta information 310 in the ID-added document “Doc4” is “Doc4”, and the parent ID is “Doc2”. The parent ID “Doc2” is a management ID read from a paper document. The user attribute is user4. Further, an operation “register as an approved version” in the document operation unit 200 is classified into an operation type “update” for the purpose of log recording, and therefore the method attribute in the meta information is “update”. In this example, since the operation type “update” is set to “public”, the value of the shared attribute in the meta information is “1” (this value means “public”). ).

  Next, the user 4 edits the document with the ID “Doc4” by the document operation unit 200. As a result, a new ID-added document “Doc5” including the document content “Content3” of the edited result and including “Doc4” as the parent ID is generated and registered in the document management server 10. The ID-added document “Doc4” in the client terminal 20 of user4 is replaced with this ID-added document “Doc5”.

  Next, when user3 edits the ID-added document “Doc3” in his / her client terminal using the document operation unit 200 and instructs “register as update” on the operation menu, the client terminal has the management ID 312. An ID-added document “Doc6” having a value “Doc6”, a parent ID 314 value “Doc3”, and an operation type value “update” is generated and replaced with the ID-added document “Doc3”, and the ID The attached document “Doc6” is registered in the document management server 10. Due to the editing, the document content has changed from “Content3” to “Content4”. Since the “update” operation is a disclosure target, the shared attribute of the ID-added document “Doc6” is “1”. A record with a management ID “Doc6” is registered in the derivation relationship DB 110 of the document management server 10.

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

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

  Returning to the description of FIG. 4, the request processing unit 140 provides a service using the derivation relationship DB 110 in response to a service request including the management ID from the client terminal 20. As a service provided by the request processing unit 140, for example, there is a service for searching for the latest version of a document corresponding to the management ID in the service request. Another example is a service that provides log information about an ancestor (root) document corresponding to the management ID in the service request or the ancestor. As another example, there is a service that provides a history of the management ID, that is, a history of operations that the document has passed from the founder to the management ID (for example, a list of information indicating who performed what operation when). There is also a service that accepts specification of search conditions for attribute items registered in the derivation relationship DB 110 and provides a list of ID-added documents that satisfy the search conditions. The service 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 above-described service that provides information on the original document can be regarded as a service that provides a search result for the condition that “the node address indicates the root”.

  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, 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. In this case, as shown in FIG. 7, when the user performs a predetermined operation such as right button click on the icon 410 or 414 of the document with ID displayed on the file management screen 400 provided by the operating system, The system displays a menu 420 associated with the ID-added document on the screen. In the illustrated example, the icon 410 or 414 of an ID-added document can be distinguished from other types of files 412 by a mark 411 indicating that it is an ID-added document of this system. When the user selects a desired item from among the service items on the menu 420, the client terminal 20 requests the document management server 10 to execute the selected service item.

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

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

  The processing procedure of the request processing unit 140 when a service request is received will be described below with reference to FIGS. In the following, when the data contents in the derivation relation DB 110 are those illustrated in FIGS. 5 and 6, user2 designates the ID-added document “Doc2” in his client terminal 20 as the target. A case where a request for a document satisfying the search condition is made will be described as a specific example.

  In this procedure, the request processing unit 140 extracts a management ID included as a processing target from the service request received from the client terminal 20, and sets the management ID as a target ID (S1). Next, a record corresponding to the attention ID is acquired from the derivation relationship DB 110 (S2). The record corresponding to the attention ID is a record having the attention ID as the value of the item “management ID” in the record. Then, it is checked whether or not the value of the operation type item in the acquired record is “registration” (S3). If it is not “registration”, the value of the attention ID is changed to the value of the parent ID in the record. Replace (S4) and execute steps S2 and S3. This loop of steps S2 to S4 represents a process for tracing back the tree structure of the derivation relationship from the management ID in the service request and finding the “registration” operation of the original form (root). When the determination result in step S3 is Yes, the attention ID at that time corresponds to the root "registration" operation. In the example of FIG. 5, the management ID “Doc1” that is the root is finally reached by tracing back the tree structure from the management ID “Doc2”.

  When the “registration” operation that is the root is reached, the request processing unit 140 searches for a child ID of the attention ID (root) at that time (S5). “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. When all the child IDs of the target ID are obtained, the request processing unit 140 executes a descendant search process as shown in FIG. 9 for each child ID (S6).

  In the descendant search process (S6), the request processing unit 140 sets the child ID as an attention ID (S11), and acquires a record corresponding to the attention ID from the derivation relationship DB 110 (S12). Then, it is determined whether or not the value of the “public” attribute in the record is “1” (S13). If it is “1”, the record is put in the intermediate result list (S14). The intermediate result list is a list constructed on the storage device of the client terminal 20 in order to accumulate information that is a material for obtaining the processing result of the requested processing. If the “public” attribute is not “1”, step S14 is skipped. Then, the request processing unit 140 searches for the child ID of the attention ID (S15), and determines whether the child ID has been searched (S16). If there is a child ID, the request processing unit 140 recursively executes a descendant search process (S6) for each of the child IDs. When the descendant search process for all the child IDs ends, the process for the attention ID ends. Even when it is determined in step S16 that there is no child ID, the process for the attention ID is ended.

  Returning to the procedure of FIG. 8, when the descendant search process (S6) is completed for all the child IDs of the root ID-added document, the intermediate result list at that time includes all the ID-added documents derived from the root. , All records corresponding to those whose “public” attribute is “1” are accumulated. The request processing unit 140 obtains a record satisfying the search condition from the record group accumulated in the intermediate result list (S7). Then, the ID-added document corresponding to the obtained record is provided to the requesting user (user2 in this example) as a search result for the request (S8).

  For example, in the example of FIG. 6, two records with management IDs “Doc4” and “Doc6” are accumulated in the intermediate result list by the process of step S6. For example, if the search condition is a condition of “document with the latest operation date / time”, the document “Doc6” with the latest operation date / time in the intermediate result list is provided to the requesting user 2 as a search result.

  If a plurality of ID-added documents are obtained as search results in step S7, all of the plurality of documents may be returned to the requesting user. Alternatively, a list of ID-added documents as search results may be returned to the user, and the user may select and obtain a desired one from the list.

  As described above, in the present embodiment, only a document resulting from an operation corresponding to a specific operation type is disclosed. In addition, since the operation result of which operation type is to be disclosed can be individually set for each document operation unit 200 of each client terminal 20, the operation result according to the circumstances of each client terminal or each document operation unit 200 You can control the public / private release.

  The following modification will be described. In the above embodiment, the request processing unit 140 searches the entire tree to which the management ID in the service request belongs. On the other hand, in this modification, a search boundary is set according to the type of operation performed by the document operation unit 200, and the search is performed within a range delimited by these boundaries.

  As an example for explanation, a derivation relationship as shown in FIGS. 10 and 11 is considered. This derivation relationship shows a state when the following operation is further applied after the state shown in FIGS.

  That is, after the state shown in FIGS. 5 and 6, user3 prints the ID-added document “Doc6” and distributes the printed paper document to user5. By this printing, an ID-added document “Doc7” is generated and registered in the document management server 10. Next, user5 confirms the contents of the paper document received from user3, sets it in the scanner, and performs an operation of “register as an approved version”. As a result, the ID-added document “Doc8” including the scan result image is generated and registered in the document management server 10. Then, when user 5 opens the ID-added document “Doc8”, performs editing, and performs a “register as update” operation, the ID-added document “Doc9” is generated and registered in the document management server 10. The derivation relationship shown in FIGS. 10 and 11 is the state at this point. In this example, as in the examples of FIGS. 5 and 6, both the operation of “registering the scanned image as an approved version” and the operation of registering the edited result of the electronic document as “updated version” have both “public” attributes. It is assumed that the operation is a value “1”.

  In this example, the search boundary can be set in the tree structure of the derivation relationship. When the request processing unit 140 scans the tree starting from the management ID in the received service request, the request processing unit 140 does not advance scanning beyond the search boundary to the ancestors and descendants. As described above, in this modification, the search range is not the entire tree including the management ID in the service request, but the management ID is included in each subtree that can be divided by the search boundary. Only the subtree is used as the search range. In this modified example, when a specific type of operation is performed on a document, a search boundary is set between the document before the operation and the operation result document.

  In order to represent the search boundary, in the illustrated example, a “boundary” attribute is incorporated in the meta information of the ID-added document. If the value of the “boundary” attribute of a document is “1”, this indicates that the search boundary is between the document and its parent. If the value of the “boundary” attribute of a document is “0”, the document and its parent belong to the same search range. The type of operation result to be used as a search boundary is registered in the document operation unit 200 in advance. In the example of FIGS. 10 and 11, a “register” operation and a “register as update version” operation (for an electronic ID-added document) are set as operation types that generate search boundaries, and the documents “Doc1”, “ The “Boundary” attribute of “Doc6” and “Doc9” is “1”. When an operation of such registered type is performed, the document operation unit 200 sets the “boundary” attribute of the ID-added document as the operation result to “1”. Otherwise, the value of the “boundary” attribute is set to “0”, or the “boundary” attribute itself is omitted.

  For example, the meta information record of the ID-added document “Doc9” is as shown in Example 3 below.

[Example 3]
<metadata sid = "Doc9" pid = "Doc8" date = "2006-10-03T14: 34" method = "update" filename = "aaa_v2.doc" user = "user5" shared = "1" unrelated = "1"/>

  In this example, the unrelated attribute is a “boundary” attribute. Note that the operation of reading a paper document and “registering as an approved version” and the operation of registering an electronic ID-added document as “updated version” are the same in the operation type on the log record in the example of the above embodiment. In this modified example, such a classification operation is also distinguished in the determination of the “boundary” attribute. That is, in this example, the value of the “boundary” attribute corresponding to the operation of reading a paper document and “registering as an approved version” is “0”. For example, the “boundary” attribute value of the ID-added document “Doc8” is “0”. In this modification, it can be said that the determination of the “boundary” attribute is performed based on the type of operation in the document operation unit 200. This is merely an example, and the determination may be made according to the operation type on the log record.

  In the state shown in FIG. 10 and FIG. 11, it is assumed that user3 requests “latest form acquisition” for the ID-added document “Doc7” via the user interface screen illustrated in FIG. 7, for example. To do. Taking such a case as an example, an example of the processing procedure of the request processing unit 140 when a request for “latest form acquisition” is received will be described.

  In this case, the request processing unit 140 obtains the latest form, for example, according to the procedure shown in FIGS. In the procedure of FIG. 12, the request processing unit 140 first sets a management ID included as a processing target in the request received from the client terminal 20 as a target ID (S1), and records corresponding to the target ID from the derivation relationship DB 110. Is acquired (S2). Next, it is checked whether or not the value of the “boundary” attribute in the record is “1” (S3A). If it is not “1”, the value of the attention ID is replaced with the value of the parent ID in the record. (S4), Steps S1 to S3A are repeated.

  If the determination result in step S3A is Yes, the derivation relationship is traced back from the requested management ID, and the node at the latest search boundary has been reached. This node is the root of the subtree that is the scope of the current search. The request processing unit 140 checks the public attribute of the attention ID at that time (that is, the root of the subtree) (S9), and if the value of the public attribute is “1”, puts the record corresponding to the attention ID in the intermediate result list ( S10), the process proceeds to step S5. If the public attribute corresponding to the attention ID is not “1” in step S9, step S10 is skipped and the process proceeds to step S5. In step S5, a child ID of the attention ID is searched. Then, the request processing unit 140 executes a descendant search process as shown in FIG. 13 for each child ID (S6).

  In the descendant search process (S6), the request processing unit 140 sets the child ID as an attention ID (S11), and acquires a record corresponding to the attention ID from the derivation relationship DB 110 (S12). Then, it is determined whether or not the value of the “boundary” attribute in the record is “1” (S20). If the value of the “boundary” attribute is “1”, it means that the search boundary in the descendant direction has been reached in the scanning of the subtree, and the processing of FIG. 13 for the attention ID is ended. If the value of the “boundary” attribute is not “1”, it is further determined whether or not the value of the “public” attribute is “1” (S13). If the determination result in step S13 is Yes, the request processing unit 140 places the record in the intermediate result list (S14). If the determination result of step S13 is No, step S14 is skipped. Then, the request processing unit 140 searches for the child ID of the attention ID (S15), and determines whether the child ID has been searched (S16). If there is a child ID, the request processing unit 140 recursively executes a descendant search process (S6) for each of the child IDs. When the descendant search process for all child IDs is completed, or when it is determined in step S16 that there is no child ID, the process for the attention ID is completed.

  Returning to the procedure of FIG. 12, when the descendant search process (S6) is completed for all the child IDs of the root of the subtree specified in step S3A, the intermediate result list at that time belongs to the subtree and “open”. All ID-added documents having the attribute “1” are accumulated. The request processing unit 140 obtains the “latest” record that is the search condition from the record group accumulated in the intermediate result list (S7), and uses the ID-added document corresponding to this record as the search result as the requesting user. (S8).

  For example, in the example of FIG. 10, when the “latest form acquisition” request is made for the ID-added document “Doc7”, “Doc6” that is the root of the subtree of the search range is specified by the loop of steps S1 to S4. The Further, two records with management IDs “Doc6” and “Doc8” are accumulated in the intermediate result list by the processing from step S9. The ID-added document “Doc9” has a “public” attribute value of “1”, but also has a “boundary” attribute value of “1”, so that it is not stored in the intermediate result list in step S20. An ID-added document “Doc8” corresponding to the latest record among the records accumulated in the intermediate result list is obtained as a search result in step S8.

  According to the modification described above, a search boundary can be set between the document before the operation and the operation result document according to the operation on the document. Setting the search boundary can also be understood as handling the document before the operation and the document as the operation result as documents of different systems. Further, in the above modification, it is possible to individually set for each document operation unit 200 of each client terminal 20 whether or not to set a search boundary according to which operation type operation. The search boundary can be controlled according to the circumstances of the document operation unit 200.

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

  Here, 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 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 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. 14, 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. Further, a hard disk drive 48 and a disk drive 50 for reading various types of portable non-volatile recording media such as a CD, a DVD, and a flash memory are connected to the bus 46 via, for example, an I / O interface 44. . Such a drive 48 or 50 functions as an external storage device for the memory. A program in which the processing contents of the embodiment are described is stored in a fixed storage device such as the hard disk drive 48 via a recording medium such as a CD or DVD or via a network, and is installed in a computer. The program stored in the fixed storage device is read into the memory and executed by the CPU, whereby the processing of the embodiment is realized. The same applies to the client terminal 20.

It is a block diagram which shows the example of schematic structure of a document utilization management system. It is a block diagram which shows the example of an internal structure of a client terminal. It is a figure which shows typically the example of the data structure of a document with ID. It is a block diagram which shows the example of an internal structure of a document management server. It is a figure which shows the example of the data content of derivation relation DB. FIG. 6 is a diagram schematically illustrating a tree structure formed by a management ID group in the data content illustrated in FIG. 5. It is a figure which shows the example of the display screen which displayed the icon of the document with ID. It is a flowchart which shows a part of example of the process sequence of the request | requirement process part with respect to a service request. It is a flowchart which shows the remaining part of an example of the process sequence of the request process part with respect to a service request. It is a figure which shows the example of the data content of derivation relation DB in a modification. FIG. 11 is a diagram schematically illustrating a tree structure formed by a management ID group in the data content illustrated in FIG. 10. It is a flowchart which shows a part of example of the process sequence of the request process part with respect to the newest form acquisition request. It is a flowchart which shows the remaining part of an example of the process sequence of the request process part with respect to the newest form acquisition request. 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)

The second document obtained as a result of the operation of the first document and the disclosure attribute information indicating whether or not the second document is a disclosure target are received from the information processing apparatus and stored in association with each other. If the first document is already registered in the storage unit, a derivation relationship indicating that the parent of the second document is the first document is provided. A registration unit for registering in the storage unit;
In response to a search instruction that specifies a target document and a search condition, among the documents included in the tree to which the target document belongs in the tree group formed by the derivation relation group stored in the storage unit, the search condition is satisfied A search result providing unit that provides, as a search result, a document corresponding to disclosure attribute information indicating that it is a disclosure target;
A document management apparatus comprising: The registration unit further receives search boundary information indicating whether or not a search boundary is between the second document and the first document from the information processing apparatus, and associates the search boundary information with the second document. Register in the storage unit,
The search result providing unit satisfies and discloses the search condition among documents belonging to a subtree to which the target document belongs among subtree groups delimited by the search boundary in the tree group formed by the derivation relation group. Providing documents corresponding to the disclosure attribute information indicating the target as search results,
A document management apparatus characterized by that. The second document obtained as a result of the operation of the first document and the disclosure attribute information indicating whether or not the second document is a disclosure target are received from the information processing apparatus and stored in association with each other. A registration relationship indicating that a parent of the second document is the first document when the first document is already registered in the storage unit. Registering in the storage unit;
In response to a search instruction that specifies a target document and a search condition, among the documents included in the tree to which the target document belongs in the tree group formed by the derivation relation group stored in the storage unit, the search condition is satisfied Providing a document corresponding to the disclosure attribute information indicating that it is a disclosure target as a search result;
A program that causes a computer to execute. An operation execution unit for performing operations on the document;
A determination information storage unit that stores determination information for specifying whether or not a document obtained as a result of the operation is to be disclosed for each operation;
Based on the determination information, disclosure attribute information indicating whether or not the second document obtained as a result of the operation is to be disclosed when an operation is performed on the first document by the operation execution unit. A transmitting unit that generates and transmits the disclosure attribute information to the document management apparatus in association with the second document;
An information processing apparatus comprising: An operation execution unit for performing operations on the document;
A determination information storage unit that stores determination information for specifying whether or not a document obtained as a result of the operation is to be disclosed for each operation;
Based on the determination information, disclosure attribute information indicating whether or not the second document obtained as a result of the operation is to be disclosed when an operation is performed on the first document by the operation execution unit. A transmitting unit that generates and transmits the disclosure attribute information to the document management apparatus in association with the second document;
Program to make the computer function. An information processing device and a document management device;
The information processing apparatus includes:
An operation execution unit for performing operations on the document;
A determination information storage unit that stores determination information for specifying whether or not a document obtained as a result of the operation is to be disclosed for each operation;
Based on the determination information, disclosure attribute information indicating whether or not the second document obtained as a result of the operation is to be disclosed when an operation is performed on the first document by the operation execution unit. A transmitting unit that generates and transmits the disclosure attribute information to the document management apparatus in association with the second document;
With
The document management apparatus includes:
A second document obtained as a result of the operation of the first document and disclosure attribute information indicating whether or not the second document is a disclosure target are received from the information processing apparatus and associated with each other. A registration unit for registering in a storage unit, and when the first document is already registered in the storage unit, a derivation relationship indicating that a parent of the second document is the first document A registration unit for further registering in the storage unit;
In response to a search instruction that specifies a target document and a search condition, among the documents included in the tree to which the target document belongs in the tree group formed by the derivation relation group stored in the storage unit, the search condition is satisfied A search result providing unit that provides, as a search result, a document corresponding to disclosure attribute information indicating that it is a disclosure target;
Comprising
A document management system characterized by that.

Images