Document management method, document management system, revision suggestion method, and revision suggestion system

Abstract

The present invention provides a document management method to be executed by a processor, the document management method comprising: acquiring an electronic document containing revision history information related to a history of revisions; generating, on the basis of the electronic document and the revision history information, at least one earlier-version document, which is an earlier version of the electronic document in accordance with a revision process corresponding to the history of revisions; and storing the at least one earlier-version document in a memory, in association with version information related to the version of the document in the revision process corresponding to the at least one earlier-version document.

Description

Document management method, document management system, correction suggestion method, and correction suggestion system

[0001] The present disclosure relates to a document management method, a document management system, a document management program, a correction suggestion method, a correction suggestion system, and a correction suggestion program.

[0002] 2. Description of the Related Art Conventionally, there are known techniques for generating past documents and suggesting document revisions based on the revision history of the documents.

[0003] For example, the document creation support device described in Patent Document 1 generates template contract split data and modified contract split data by dividing template contract data and modified contract data by article. The document creation support device then generates comparison data based on the template contract split data and modified contract split data, which indicate the correspondence between the articles of both contracts and the differences between the corresponding articles. Furthermore, the document creation support device extracts, based on the comparison data, review item data related to the differences from the review item data specified for each article of the template contract, and generates output data based on the comparison data and the extracted review item data.

[0004] JP 2010-92227 A

[0005] However, the document creation support device described in Patent Document 1 does not take into consideration processing of a document that includes revision history information relating to revision history.

[0006] Therefore, one embodiment of the present invention aims to provide a document management method, a document management system, a document management program, a correction proposal method, a correction proposal system, and a correction proposal program that are capable of document management or correction proposal for electronic documents that include correction history.

[0007] A document management method according to one aspect of the present invention is a document management method executed by a processor, and includes: acquiring an electronic document including revision history information relating to a revision history; generating at least one older version document that is a previous version of the electronic document based on the electronic document and the revision history information, in accordance with a revision process corresponding to the revision history; and storing the at least one older version document in memory in association with version information relating to a version of the document in the revision process corresponding to the at least one older version document.

[0008] According to one embodiment of the present invention, it is possible to provide a document management method that allows document management or revision suggestions for electronic documents that include revision histories.

[0009] 1 is a diagram showing an overview of processing in the revision suggestion system 10 and document management system 100 according to an embodiment of the present invention. FIG. 2 is a diagram showing the configurations of the revision suggestion system 10 and document management system 100 according to an embodiment of the present invention. FIG. 3 is a diagram showing an example of history document information stored in the storage unit 110. FIG. 4 is a diagram showing an example of revision history information stored in the storage unit 110. FIG. 5 is a diagram showing an example of classification information stored in the storage unit 110. FIG. 6 is a diagram showing an example of old version document information stored in the storage unit 110. FIG. 7 is a diagram showing an example of the revision process of an electronic document and at least one old version document, displayed on the user terminal 200. FIG. 8 is a diagram showing an example of target document information stored in the storage unit 135. FIG. 9 is a diagram showing an example of item information stored in the storage unit 135. FIG. 10 is a diagram showing an example of the revision process in a history document. FIG. 11 is a diagram showing an example of correspondence information stored in the storage unit 135. FIG. 12 is a diagram showing an example of provision of revision suggestion information by the revision suggestion unit 165. FIG. 13 is a diagram showing an example of provision of revision suggestion information by the revision suggestion unit 165. FIG. 14 is a flowchart showing an example of processing in the document management system 100. FIG. 15 is a flowchart showing an example of processing in the revision suggestion system 10. FIG. 16 is a diagram showing an example of the hardware configuration of a computer 1500.

[0010] 1 is a diagram showing an overview of the processing in a revision suggestion system 10 and a document management system 100 according to an embodiment of the present invention.

[0011] The electronic document is amended and completed as necessary. For example, if the electronic document is a business report, it is drafted by a business manager, and then amended by a business supervisor (e.g., a person in a higher position than the business manager) before the business report is finalized.

[0012] For example, if the electronic document is a contract, one or both parties may inspect and revise the contract when they reach an agreement. For example, in the case of a contract between companies, the legal department in charge of contract inspection may inspect the contents of the contract and revise it as necessary. Note that contract inspection is also sometimes called confirmation, examination, or review.

[0013] Such modifications to an electronic document may be performed using a modification history recording function provided in an application for editing the electronic document. For example, if the electronic document is a contract, one or both of the contracting parties may inspect and modify the contract while recording the modification history in the editing application.

[0014] However, an electronic document containing revision history information may be a single electronic document file, which can be quite time-consuming for users when referencing the revision history (i.e., document versions). Furthermore, saving each revision as a separate file (i.e., saving each version of the document) can be quite time-consuming for users. Furthermore, when the electronic document is a contract, it is necessary to manage versions according to the review of the contracting parties, so the auto-save function of the editing application can be quite time-consuming for users when referencing the revision history.

[0015] Therefore, the document management system 100 of this embodiment generates an old version document, which is a previous version of the electronic document, according to the revision process.

[0016] Specifically, the document management system 100 is an information processing system realized by a document management program, and generates an old document, which is a previous version of an electronic document, in accordance with the revision process corresponding to the revision history based on revision history information related to the revision history, and stores the old document in memory in association with version information related to the version of the document in the revision process corresponding to the old document.More specifically, the document management system 100 classifies the revision history information into groups according to the revision process, and generates an old document, which is a previous version of the electronic document, for each group in accordance with the revision process corresponding to the group, and stores the old document in memory in association with the version information.

[0017] Furthermore, electronic documents may be modified by referring to the modification history of similar electronic documents in the past. For example, if the electronic document is a contract, the contract may be inspected and modified by one or both of the contracting parties based on, for example, past modification cases or contract cases.

[0018] Therefore, the correction suggestion system 10 of this embodiment proposes corrections to a target document that is different from the electronic document, based on the electronic document and an older version document that is an earlier version of the electronic document.

[0019] Specifically, the revision suggestion system 10 is an information processing system realized by a revision suggestion program, and provides revision suggestion information regarding suggested revisions to target items in a target document based on post-revision information that indicates the contents of items in an electronic document including revision history information, and that is stored in memory in association with pre-revision information according to the revision process that revised the pre-revision information of an older version document generated based on the revision history information.

[0020] The revision suggestion system 10 and the document management system 100 may be independent information processing systems, or the document management system 100 may be an information processing system incorporated into the revision suggestion system 10. In the following description of this embodiment, the document management system 100 will be described as an information processing system incorporated into the revision suggestion system 10.

[0021] First, the document management system 100 acquires an electronic document (electronic document 101) containing revision history information, and classifies the revision history information into at least one group (first revision history group 102, second revision history group 103) corresponding to the revision process. Next, the document management system 100 generates old-version documents (first old-version document 104, second old-version document 105) for each group in accordance with the revision process corresponding to the group, and stores the old-version documents in memory in association with version information.

[0022] Next, the revision suggestion system 10 generates post-revision information 106 indicating the contents of the items in the electronic document 101 and pre-revision information (pre-revision information 107, pre-revision information 108) indicating the contents of the items in the old version document, and stores the pre-revision information and post-revision information in association with each other in memory.The revision suggestion system 10 then provides revision suggestion information 109 regarding a proposal for revision of the target item in a target document different from the electronic document 101 based on the post-revision information.

[0023] Fig. 2 is a diagram showing the configurations of a revision suggestion system 10 and a document management system 100 according to an embodiment of the present invention. Note that, although Fig. 2 shows the document management system 100 as an information processing system incorporated into the revision suggestion system 10, the revision suggestion system 10 and the document management system 100 may each be an independent information processing system.

[0024] The revision suggestion system 10 and the document management system 100 are communicably connected to a user terminal 200 via a network such as the Internet. The revision suggestion system 10 will be described in detail later.

[0025] The user terminal 200 is, for example, a computer used by a user of the correction suggestion system 10, such as a smartphone, a tablet terminal, or a personal computer.

[0026] For example, a user accesses the document management system 100 through the user terminal 200 and uploads an electronic document including revision history information to the document management system 100. Furthermore, the user uploads a target document to the revision suggestion system 10 through the user terminal 200. Then, the user is provided with revision suggestion information for a target item in the target document through the user terminal 200.

[0027] 2, only one user terminal 200 is shown, but the number of user terminals 200 is not limited to this. Also, one user terminal 200 may be used by multiple users.

[0028] Next, the details of the correction suggestion system 10 and the document management system 100 will be described.

[0029] The document management system 100 of this embodiment includes a storage unit 110, a history document acquisition unit 115, a group classification unit 120, a previous version generation unit 125, and an output unit .

[0030] The revision suggestion system 10 of this embodiment includes a document management system 100, and further includes a memory unit 135, a target document acquisition unit 140, an item division unit 145, a correspondence setting unit 150, a correspondence extraction unit 155, a revision suggestion information generation unit 160, and a revision suggestion unit 165.

[0031] Each unit shown in FIG. 2 can be realized by using a storage area or by a processor executing a program stored in the storage area, for example.

[0032] The storage unit 110 of this embodiment stores information to be processed in the document management system 100. The storage unit 110 can store, for example, historical document information, classification information, and old version document information, which will be described later. The storage unit 110 may be, for example, a memory.

[0033] The historical document acquisition unit 115 of this embodiment acquires a historical document, which is an electronic document including revision history information relating to the revision history, and stores the historical document information relating to the historical document in the storage unit 110 .

[0034] Here, the historical document may be, for example, an electronic contract document. The contract may be, for example, an electronic document created using predetermined electronic document creation software, or an electronic document obtained by digitizing a paper contract using predetermined image analysis technology (e.g., OCR (Optical Character Recognition) technology). Furthermore, contracts processed by the document management system 100 and the revision proposal system 10 are, for example, documents that include clauses and produce predetermined legal effects, and include applications, memoranda, etc.

[0035] The contract includes not only a contract that both parties have agreed upon, but also a contract that both parties are currently reviewing (i.e., a draft contract), a contract that has been exchanged between the parties but has not resulted in an agreement, or a contract template that has been created for reference when entering into a contract with another party. In the description of this embodiment, unless otherwise specified, the term "contract" includes not only a contract that both parties have agreed upon, but also a contract that both parties are currently reviewing (i.e., a draft contract), a contract that has been exchanged between the parties but has not resulted in an agreement, or a contract template that has been created for reference when entering into a contract with another party.

[0036] Furthermore, in this embodiment, the historical document (i.e., an electronic document including revision history information) may be a finalized historical document or the latest version of the historical document, or may be a historical document that is not the latest version. A historical document that is not the latest version may be, for example, when there is a series of historical documents including a first version, a second version, and a latest version, and the historical document acquisition unit 115 acquires the second version of the historical document. This allows the document management system 100 (particularly the old version generation unit 125 described below) to generate an old version document (in this case, the first version) described below based on the second version of the historical document without requiring the latest version of the historical document.

[0037] The revision history information is information relating to the revision history of an electronic document, and includes, for example, at least one of revision user information indicating the user who made the revision and revision date information indicating the date on which the revision was made.

[0038] Here, the modification may be any editing operation on the electronic document, and includes, for example, replacing or deleting characters written in the electronic document, adding new characters, applying a predetermined effect to characters (for example, changing the layout or format, more specifically, changing the font, changing to italic, underlining, highlighting, adding or removing indentation), inserting a graphic or table, and adding a comment using the comment function. Thus, the modification history information includes information related to the modification history.

[0039] The editing user is a subject who edits a historical document using a specific application. The editing user may be a user of the document management system 100, or may not be a user of the document management system 100. For example, the editing user may be the user name of the application that edited the document, and the information is saved in the document file. The editing user may also be a natural person, or a computer (for example, a computer that performs automatic editing using natural language processing technology).

[0040] The editing user can refer to the content of the edits made by the editing user on a predetermined date based on the edit history information by referring to the history document using a predetermined application. The editing user can also refer to the content after the edit and the content before the edit.

[0041] 3 is a diagram showing an example of history document information stored in the storage unit 110. The history document information stored in the storage unit 110 includes, for example, a history document ID, status information, position information, type information, history document content information, and revision history information.

[0042] The historical document ID in this embodiment is information for identifying historical document information stored in the storage unit 110 .

[0043] The status information in this embodiment is information indicating the status of the electronic document and the revision status of the electronic document. If the electronic document is a contract, the status information may be, for example, "Partner's Draft" indicating that it is a draft (e.g., a first draft) of the contracting party, "Partner's Revision Proposal" indicating that the contract has been revised by the contracting party, "Reviewed" indicating that the contract has been reviewed by the user's company (e.g., the company to which the user belongs), or "Concluded" indicating that the contracting parties have reached an agreement.

[0044] The position information in this embodiment is information indicating the position of the electronic document, for example, information indicating the position of the company (the business to which the user belongs). If the electronic document is a contract, the position information may be, for example, "outsourcing party" indicating the outsourcing party in a business outsourcing contract, or "disclosing party" indicating the disclosing party of confidential information in a confidentiality agreement.

[0045] The type information in this embodiment is information indicating the type of the electronic document. If the electronic document is a contract, the type information is information indicating the contract type of the contract, and includes, for example, a "service contract" or a "non-disclosure agreement."

[0046] The historical document content information in this embodiment is information (for example, character data) that indicates the content of the historical document.

[0047] 4 is a diagram showing an example of revision history information stored in the storage unit 110. The revision history information stored in the storage unit 110 includes, for example, a revision history ID, revision user information, revision date information, and revision content information.

[0048] The correction history ID in this embodiment is information that identifies the correction history information stored in the storage unit 110. The correction content information in this embodiment is information that indicates the content of the correction, and may include, for example, information that indicates the correction location and information that indicates the correction operation (for example, adding, replacing, deleting, or the like of characters).

[0049] The history document acquisition unit 115 may acquire history document information from, for example, the user terminal 200. That is, the user may provide (upload) a history document to the document management system 100 via the user terminal 200, and the history document acquisition unit 115 may acquire the history document information of the uploaded history document.

[0050] At this time, the history document acquisition unit 115 may acquire history document information from the user, for example, through operation of the user terminal 200. In this case, when receiving an upload of a history document from the user terminal 200, the history document acquisition unit 115 may acquire the history document information by accepting input (for example, input from a keyboard or selection of an item set in advance in the document management system 100) of at least some of the history document information (for example, status information, position information, type information) from the user.

[0051] The group classification section 120 of this embodiment classifies the revision history information into at least one group corresponding to the revision process, and stores classification information indicating the results of the classification in the storage section 110.

[0052] The group classification section 120 can classify the revision history information into at least one group corresponding to the revision process based on at least one of the revision user information and the revision date information included in the revision history information.

[0053] The group classification section 120 may classify the revision history information into one group or into multiple groups.

[0054] The group classification unit 120 can classify multiple revision history information into one group. In this case, the group classification unit 120 can classify into groups based on predetermined or arbitrary conditions, and may classify revision history information of consecutive revision histories by the same user into one group. Furthermore, the group classification unit 120 may classify revision history information of revision histories made on the same day into one group. This allows the old version generation unit 125, which will be described later, to generate an old version document, which is an earlier version of the electronic document, for each group in the revision process, making it easier for users to manage and use the electronic document.

[0055] In this way, each group classified by the group classification unit 120 corresponds to the revision process and indicates the version transition of the historical document. In other words, unlike an automatic save function of an editing application (for example, a function that saves an electronic file at regular intervals), the series of revision histories of each group corresponds to each version of the historical document, and is a meaningful group in the user's document management.

[0056] 5 is a diagram showing an example of classification information stored in the storage unit 110. The classification information stored in the storage unit 110 includes, for example, a revision history ID and a group ID. The group ID in this embodiment is information that identifies the group into which the revision history information is classified.

[0057] The old version generation unit 125 of this embodiment generates, for each group, at least one old version document that is a previous version of the electronic document (history document) in accordance with the revision process corresponding to the group, based on the electronic document (history document) and the revision history information, and stores the old version document information related to the old version document in the storage unit 110. That is, the old version generation unit 125 generates at least one old version document, associates the at least one old version document with version information related to a document version in the revision process corresponding to the at least one old version document, and stores the at least one old version document in memory (e.g., the storage unit 110).

[0058] Furthermore, the old version generation unit 125 can generate a first old version document corresponding to a first revision process among multiple revision processes corresponding to multiple groups, and a second old version document corresponding to a second revision process carried out before the first revision process, based on the electronic document (history document) and the revision history information. The old version generation unit 125 then stores the first old version document in memory in association with first version information related to the version of the document in the first revision process, and stores the second old version document in memory in association with second version information related to the version of the document in the second revision process.

[0059] That is, the old version generation unit 125 can generate multiple old version documents according to multiple revision processes corresponding to multiple groups based on the electronic document (history document) and revision history information. As a result, when a user uploads a history document to the document management system 100, the document management system 100 processes the old version document according to the revision process.

[0060] The old version generating unit 125 generates old versions of documents according to the revision process, allowing the user to easily manage the transition of versions of the historical document.

[0061] The old version generation unit 125 may generate the old version document as a document file in the same format (for example, extension) as the history document, or may generate difference information (for example, meta-information) indicating the difference from the history document and handle the history document and the difference information as the old version document. In the following, the explanation will be given assuming that the old version generation unit 125 generates the old version document as a document file.

[0062] The old version generating unit 125 can generate an old version document ID for identifying the old version document according to the revision process, for example, and include the ID in the old version document information.

[0063] Furthermore, the old version generating unit 125 can include version information relating to a document version in the revision process corresponding to the old version document in the old version document information, thereby enabling the old version generating unit 125 to associate at least one old version document with the version information.

[0064] Here, the version information is information about a version of a document in the revision process corresponding to the old version document, and may be, for example, a historical document ID of a historical document corresponding to the old version document (i.e., the latest version document obtained by revising the old version document), or an old version document ID (e.g., an old version document ID of an older version document that is even older than the old version document, or an old version document ID of an older version document that is newer than the old version document). In other words, the version information may be information indicating, for example, which electronic document (e.g., the old version document) the old version document is a document after it has been revised, or which electronic document (e.g., the historical document or the old version document) the old version document is a document before it has been revised.

[0065] 6 is a diagram showing an example of old-version document information stored in the storage unit 110. The old-version document information stored in the storage unit 110 includes, for example, an old-version document ID, version information, a group ID, and old-version document content information. The old-version document content information in this embodiment is information (for example, character data) that indicates the content of the old-version document.

[0066] Although FIG. 6 shows a historical document ID as the version information, the version information is not limited to this and may be, for example, an old version document ID.

[0067] The output unit 130 of this embodiment outputs information for displaying the revision process of at least one old version document to the user terminal 200. The output unit 130 may also output information for displaying the revision process of the electronic document and at least one old version document to the user terminal 200. The output unit 130 can output information for displaying the revision process based on, for example, version information.

[0068] The output unit 130 can output, for example, information indicating at least one old-version document (e.g., the file name of the old-version document) arranged in the order of the revision process and displayed. The output unit 130 can also output, for example, information indicating an electronic document and information indicating at least one old-version document (e.g., the file names of the electronic document and the old-version document) arranged in the order of the revision process and displayed.

[0069] FIG. 7 is a diagram showing an example of the process of correcting an electronic document and at least one old version document displayed on the user terminal 200.

[0070] The screen shown in Fig. 7 includes a selection area 701 that the user selects when uploading an electronic document, a history document area 702 that displays information indicating the history document uploaded by the user, a first old-version document area 703 that displays information indicating the first old-version document generated by the old-version generation unit 125, and a second old-version document area 704 that displays information indicating the second old-version document generated by the old-version generation unit 125. On the screen shown in Fig. 7, the history document area 702, the first old-version document area 703, and the second old-version document area 704 are displayed vertically in the order of the revision process. This allows the user to visually understand the revision process.

[0071] Furthermore, when the user selects (for example, by touching or clicking with a mouse) the history document area 702, the first old-version document area 703, or the second old-version document area 704 through the user terminal 200, the corresponding document (history document, first old-version document, or second old-version document) may be displayed. This allows the user to refer to the document corresponding to the revision process.

[0072] The screen displayed on the user terminal 200 based on the information output by the output unit 130 is not limited to the screen shown in FIG.

[0073] 7, when a user selects the history document area 702, the first old-version document area 703, or the second old-version document area 704, a flow of revisions to the selected history document or old-version document may be displayed. In other words, if the history document or old-version document has a revision history, the revision history may be displayed. The information output by the output unit 130 may be, for example, information for displaying the contents indicated by the revision content information in the order of the date indicated by the revision date information based on the revision history information stored in the storage unit 110.

[0074] Next, the correction suggestion system 10 will be described in detail.

[0075] The storage unit 135 of this embodiment stores information processed by the revision suggestion system 10. The storage unit 135 can store, for example, target document information, item information, correspondence relationship information, and revision suggestion information, which will be described later. The storage unit 135 may be, for example, a memory.

[0076] The target document acquisition unit 140 of this embodiment acquires a target document that is different from a history document, and stores target document information relating to the target document in the storage unit 135 .

[0077] Here, the target document is an electronic document that is different from the electronic document (history document) used to generate the old version document acquired by the history document acquisition unit 115, and is an electronic document that includes target items that are the subject of revision suggestions by the revision suggestion unit 165 described below.

[0078] 8 is a diagram showing an example of target document information stored in the storage unit 135. The target document information stored in the storage unit 135 includes, for example, a target document ID, status information, position information, type information, and target document content information. The target document ID is information that identifies the target document information stored in the storage unit 135. The target document content information is information (for example, character data) that indicates the content of the target document.

[0079] The item division unit 145 of this embodiment divides the contents of the electronic document (historical document, old version document, target document) into items contained in the electronic document (historical document, old version document, target document) and stores item information related to the items in the memory unit 135.

[0080] Here, the items may correspond to the provisions contained in the electronic document. That is, the item dividing unit 145 can divide the contents of the electronic document into, for example, "articles," "paragraphs," or "subparagraphs."

[0081] The item dividing unit 145 can, for example, analyze the contents of an electronic document and divide the contents of the electronic document into items based on the positions of characters corresponding to the items (e.g., the characters "article" or "paragraph"). Note that the item dividing unit 145 does not have to divide all electronic documents into items, and it does not have to divide all items of an electronic document into items. In other words, the item dividing process by the item dividing unit 145 may be performed on a portion of the electronic document, or may be performed on a part of the electronic document.

[0082] The item dividing unit 145 can divide an old-version document (for example, a first old-version document, a second old-version document) into items and generate pre-editing information indicating the pre-editing content of each item as item information.

[0083] The item dividing unit 145 can divide the history document into items and generate post-correction information indicating the post-correction content of each item as item information.

[0084] That is, the post-editing information and pre-editing information of the corresponding items have a relationship in which the content indicated by the pre-editing information has been modified by the user to the content indicated by the post-editing information.

[0085] The item dividing unit 145 can also divide the target document into items and generate target information indicating the content of each item as item information.

[0086] 9 is a diagram showing an example of item information stored in the storage unit 135. The item information stored in the storage unit 135 includes, for example, an item ID, a document ID, and item content information.

[0087] The item ID in this embodiment is information that identifies the item information processed in the revision suggestion system 10. The document ID in this embodiment is information that indicates an electronic document that includes the content indicated by the item information, and includes, for example, a history document ID, an old version document ID, or a target document ID. The item content information in this embodiment is information that indicates the content corresponding to an item, and is, for example, information that indicates the content of each clause.

[0088] In addition, whether the item information stored in the memory unit 135 is pre-correction information, post-correction information, or target information may be determined, for example, based on the document ID included in the item information (specifically, for example, whether it is a history document ID, an old version document ID, or a target document ID).

[0089] The correspondence setting unit 150 of this embodiment associates pre-editing information indicating the content of an item in at least one old-version document with post-editing information obtained by correcting the pre-editing information and indicating the content of an item in an electronic document (historical document) according to the edit process, and stores the association information in memory. The correspondence setting unit 150 generates correspondence information that associates the pre-editing information and the post-editing information according to the edit process, and stores the correspondence information in the storage unit 135.

[0090] The correspondence information in this embodiment is information that associates the contents before correction with the contents after correction for each item of the history document and the old version document.

[0091] Note that the item corresponding to the pre-revision information and the item corresponding to the post-revision information may both have the same item ID (in other words, for example, an article number, or an article and paragraph number). Specifically, if the pre-revision information and the post-revision information both correspond to "Article 1" in the electronic document, the revision suggestion system 10 may determine that the pre-revision information and the post-revision information correspond to each other.

[0092] Furthermore, the item corresponding to the pre-revision information and the item corresponding to the post-revision information may have different item IDs. In this case, the revision suggestion system 10 may determine that the pre-revision information and the post-revision information correspond to each other, for example, based on the contents indicated by the pre-revision information and the post-revision information.

[0093] Specifically, if the contents indicated by the pre-revision information and the post-revision information both relate to the scope of responsibility of the contracting parties, they correspond to the same item whether their item IDs are the same or different. On the other hand, if the contents indicated by the pre-revision information indicate the expiration date of the contract and the contents indicated by the post-revision information indicate the scope of responsibility of the contracting parties, they do not correspond to the same item whether their item IDs are the same or different.

[0094] The item ID may be linked to an issue that appears in the contract or the type of contract. For example, the item ID may be linked to information indicating whether the contract is automatically renewed, or to an issue such as governing law or jurisdiction. Furthermore, for example, if the type of contract is a confidentiality agreement, the item ID may be assigned in association with an issue that appears depending on the type of contract (for example, if the type of contract is a confidentiality agreement, an issue such as the scope of confidential information or disposal of confidential information).

[0095] The revision suggestion system 10 may determine that the pre-revision information and the post-revision information correspond to each other based on both the matching status of the item IDs and the matching status of the content. In this case, the revision suggestion system 10 may place more importance on either the matching status of the item IDs or the matching status of the content based on a predetermined priority.

[0096] Furthermore, the order of the item division process by the item division unit 145 for the electronic document and the process by the correspondence setting unit 150 does not matter. That is, the correspondence setting unit 150 may set the correspondence between the history document and the old version document based on the document information, and then the item division unit 145 may perform item division processing to generate correspondence information between the pre-editing information and the post-editing information for each item. Alternatively, after the item division process by the item division unit 145, the correspondence setting unit 150 may perform processing to generate correspondence information for each item.

[0097] In this way, the item division process by the item division unit 145 and the process by the correspondence setting unit 150 allow the user to manage the changes in versions of a historical document for each item (for example, "article" or "paragraph").

[0098] 10A is a diagram showing an example of the correction process for a history document. Item information 1001 is item information for the second old-version document. Item information 1002 is item information for the first old-version document. Item information 1003 is item information for the history document. In other words, the content indicated by item information 1001 was corrected to the content indicated by item information 1002, and the content indicated by item information 1002 was further corrected to the content indicated by item information 1003, thereby generating the history document.

[0099] Fig. 10B is a diagram showing an example of correspondence information stored in the storage unit 135. The example of correspondence information shown in Fig. 10B corresponds to the correction process shown in Fig. 10A. The correspondence information stored in the storage unit 135 includes, for example, pre-correction information and post-correction information. The correspondence information may include, for example, corresponding item IDs as the pre-correction information and the post-correction information.

[0100] 10A is made, the correspondence relationship information stored in the storage unit 135 will be, for example, as shown in the example of Fig. 10B. That is, the correspondence relationship information will hold, for example, item information 1001 and 1002 as pre-correction information, and will hold item information 1003 as post-correction information so as to correspond to the item information 1001 and 1002.

[0101] The correspondence information may hold item information 1002 instead of item information 1003 as post-correction information corresponding to item information 1001 of pre-correction information, or may hold both item information 1002 and item information 1003. This allows the correction suggestion system 10 to have correspondence information for each correction process.

[0102] The correspondence extraction unit 155 of this embodiment extracts at least one piece of correspondence information from the pre-editing information and post-editing information for each item of an electronic document (historical document, old version document) based on the target information in the target document.

[0103] Furthermore, the correspondence extraction unit 155 can extract at least one piece of correspondence information based on the degree of association between the pre-correction information and the target information. Specifically, the correspondence extraction unit 155 can extract correspondence information corresponding to the pre-correction information including an item that has a high degree of association with the target item indicated by the target information (in particular, for example, the post-correction information associated with the pre-correction information).

[0104] Here, the degree of relevance is, for example, the degree of relevance between the content indicated by the pre-revision information and the content indicated by the target information. Specifically, the degree of relevance may be based on at least one of the contents of the pre-revision information and the target information, the position or type in the electronic document corresponding to the pre-revision information and the post-revision information, and the points of contention included in the pre-revision information and the target information.

[0105] The relevance based on the content of the pre-revision information and the target information is, for example, the relevance between the content of the item indicated by the pre-revision information and the target information (e.g., the content of the article). That is, for example, if the content indicated by the pre-revision information and the content indicated by the target information are evaluated to be similar based on a predetermined natural language processing, the relevance may be evaluated as high. This allows the revision suggestion system 10 to extract pre-revision information having content similar to the target information, and to perform the revision suggestion process without the user having to modify the content of the target information.

[0106] The relevance based on the position or type of the electronic document may be highly evaluated, for example, when the position or type of the electronic document and the target document are the same. This allows the revision suggestion system 10 to extract pre-revision information of electronic documents with a similar position or type to the target document and perform revision suggestion processing.

[0107] The issues contained in the Pre-Revised Information and the Subject Information are, for example, matters that should be noted in the content of the Pre-Revised Information and the Subject Information. In other words, the issues relate to matters that the company should particularly confirm, such as the definitions of terms stated in contracts with other companies or the scope of the stated content.

[0108] The relevance based on the issue may be highly evaluated when the issue included in the pre-revision information and the target information is the same or similar. This allows the revision suggestion system 10 to extract pre-revision information that includes an issue that is the same or similar to an issue of the target information, and to make a revision suggestion.

[0109] Here, the points of contention may be set in advance by an administrator of the revision suggestion system 10 in correspondence with predetermined content. Alternatively, the points of contention may be set at parts that are frequently revised by users based on the correspondence relationship information.

[0110] The revision suggestion system 10 can extract points of contention by analyzing the contents of the contract based on predetermined natural language processing.

[0111] The relevance may also be a relevance based on comment information indicating the content of comments included in the electronic file of the electronic document (historical document, old version document).

[0112] Here, the comment is, for example, an annotation written by a user (for example, a person in charge of a contracting party (i.e., one's own company) using the revision proposal system 10) describing the intention or concerns of the revision content when inspecting the contract. Note that the comment may also be an annotation written by the other contracting party (for example, a person in charge of another company).

[0113] The comment information in this embodiment is information indicating the content of the comment, and is included in, for example, the electronic file of the contract uploaded by the user. For example, the history document acquisition unit 115 and the target document acquisition unit 140 can acquire the comment information when the user uploads an electronic document (history document or target document).

[0114] The relevance based on the comment information may be evaluated highly, for example, when the content of the comments in the pre-edited information and the target information is identical or similar. This allows the edit suggestion system 10 to extract pre-edited information with identical or similar comments and to suggest edits without the user having to edit the content of the target information.

[0115] The items to be prioritized in calculating the relevance between the pre-revision information and the target information may be set by an administrator or a user of the revision suggestion system 10. That is, for example, if a user sets the calculation of the relevance to prioritize position over content in a contract, the correspondence extraction unit 155 may not extract correspondence information of pre-revision information in which the position in the pre-revision information is not the same as the position in the target information, even if the content in the pre-revision information is similar to the content in the target information. This allows the revision suggestion system 10 to extract pre-revision information that is more suitable for the user's revision.

[0116] In this way, the correspondence extraction unit 155 can extract correspondence information suitable for proposing corrections to the target item in the target document.

[0117] More specifically, the correspondence extraction unit 155 can extract correspondence information corresponding to pre-correction information related to the target item (i.e., pre-correction information having content similar to that of the target item). In this case, since the content indicated by the target information and the content indicated by the pre-correction information are similar, there is a possibility that correction content in the electronic document corresponding to the pre-correction information will also be appropriate for the target document corresponding to the target information. Therefore, the correspondence extraction unit 155 can extract correspondence information suitable for proposing corrections to the target item in the target document.

[0118] The revision proposal information generator 160 of this embodiment generates revision proposal information regarding a proposed revision of a target item in a target document based on the post-revision information, and stores the generated information in the storage unit 135. More specifically, the revision proposal information generator 160 can generate revision proposal information regarding a proposed revision of a target item in a target document based on the post-revision information included in at least one piece of extracted correspondence information.

[0119] The suggested revision information generator 160 may also generate suggested revision information based on post-revision information associated with pre-revision information that is highly relevant to the target item of the target document.

[0120] Here, the correction suggestion information is information for suggesting to the user how to correct the target item.

[0121] The correction suggestion information may include, for example, post-correction information included in at least one of the extracted correspondence information, which allows the user to understand the content of past corrections and correct the target item.

[0122] In addition to the post-correction information, the correction suggestion information may further include comment information added by the user when correcting the item before correction (i.e., comment information included in the electronic document), which allows the user to understand comments made in the past correction process and correct the target item.

[0123] Furthermore, the proposed revision information may include, in addition to the post-revision information, at least one of position information indicating a position in the electronic document and type information indicating a type, thereby enabling the user to understand the position or type in the electronic document corresponding to the proposed revision information and to correct the target item.

[0124] Furthermore, the revision proposal information may further include, in addition to the post-revision information, information (e.g., status information) regarding whether the revision has been adopted. Here, whether the revision has been adopted may be determined, for example, based on the status information of the historical document corresponding to the post-revision information. That is, for example, if the historical document is a contract and the status information of the historical document is "concluded," it may be determined that the revision has been adopted. The revision proposal information may include the "concluded" status information in addition to the post-revision information. This allows the user to understand whether the revised content indicated by the revision proposal information is content that has been agreed upon and whether the revision is likely to be adopted in the current contract being inspected. Note that, if it is unclear whether the revision has been adopted, the revision proposal information may or may not include information indicating whether the revision has been adopted.

[0125] The revision suggestion information does not necessarily have to be prepared by the user, but may be prepared or set by another party. For example, it may be prepared in advance by a vendor that provides the revision suggestion system 10 so that the user can use it. This reduces the effort required to set the revision suggestion information.

[0126] Furthermore, the vendors can revise the revision proposal information as needed to adapt to legal changes, etc. This allows users to receive appropriate revision proposals at the appropriate time.

[0127] In addition, if it is necessary to change the proposed revision information due to legal amendments, changes in standards, etc., the system may have a function for collectively amending the proposed revisions for multiple documents containing similar issues, allowing users to receive appropriate proposed revisions.

[0128] The revision suggestion unit 165 of this embodiment provides revision proposal information to the user terminal 200. That is, the revision suggestion unit 165 provides revision proposal information related to a proposal to correct a target item of a target document that is different from the electronic document (history document) acquired by the history document acquisition unit 115, based on the post-correction information.

[0129] Furthermore, the correction suggestion unit 165 can display the results of a series of correction processes corresponding to the extracted correspondence information on the user terminal 200. Specifically, when multiple corrections (for example, a first correction and a second correction) have been made to a history document corresponding to the extracted correspondence information, the correction suggestion unit 165 can display the results of the first correction and the results of the second correction on the user terminal 200. This allows the user to correct the target item after understanding the detailed correction process.

[0130] Furthermore, the revision suggestion unit 165 can provide the user terminal 200 with a plurality of pieces of revision suggestion information based on a plurality of pieces of correspondence information. In this case, the plurality of pieces of revision suggestion information may be associated with information indicating a predetermined order. Note that the predetermined order may be, for example, the order of the date and time when the revision corresponding to the revised information was made (for example, in order of the most recent date and time when the revision was made), or the order of the status information of the first contract corresponding to the revised information (for example, an order in which the status information of "concluded" is given priority).

[0131] Furthermore, when the revision suggestion unit 165 provides the user terminal 200 with multiple pieces of revision suggestion information based on multiple pieces of correspondence information, it can display similar pieces of revision suggestion information (for example, revision suggestion information whose content is similar to the post-revision information or the pre-revision information) together from among the multiple pieces of revision suggestion information.

[0132] Specifically, for example, the revision suggestion unit 165 can display, on the user terminal 200, one piece of revision suggestion information (e.g., revision suggestion information based on correspondence information corresponding to the latest post-correction information) from among multiple pieces of revision suggestion information that are similar to each other, and a button for displaying other pieces of revision suggestion information that are similar to the one piece of revision suggestion information. At this time, the revision suggestion unit 165 can also display revision suggestion information that is dissimilar to the multiple pieces of revision suggestion information that are similar to each other. This allows the user to simplify the display of similar revision suggestion information and be provided with more revision suggestion information.

[0133] At this time, the revision suggestion unit 165 may change the display order depending on the number of similar revision suggestion information. That is, the more similar the revision suggestion information is, the more the revision suggestion unit 165 may display it at the top of the screen of the user terminal 200. This allows the revision suggestion system 10 to preferentially provide frequently used example sentences to the user.

[0134] The revision suggestion unit 165 may provide the revision suggestion information based on the post-revision information associated with the pre-revision information that is highly relevant to the target item of the target document. That is, the revision suggestion unit 165 may provide the user terminal 200 with the revision suggestion information generated by the revision suggestion information generation unit 160 based on the post-revision information associated with the pre-revision information that is highly relevant to the corresponding item of the target document.

[0135] 11 is a diagram showing an example of provision of suggested revision information by the revision suggestion unit 165. The screen shown in Fig. 11 shows an example of a display screen of the user terminal 200 to which suggested revision information has been provided by the revision suggestion unit 165.

[0136] The screen shown in Figure 11 includes at least a target document area 1110 that displays the target document, a first proposal area 1120 that displays suggested revision information for each item (e.g., article), and a second proposal area 1130. The first proposal area 1120 further includes a post-revision area 1121 that displays post-revision information, a first comment button area 1122 that displays a button for displaying comment information, a status area 1123 that displays status information corresponding to the post-revision information, a type etc. area 1124 that displays type information and position information corresponding to the post-revision information, a modification user name etc. area 1125 that displays the name and date of the user who made the revision during the revision process of the history document, and a reference button area 1126 that displays a button for referencing the history document. Note that the second proposal area 1130 includes an area corresponding to the area included in the first proposal area 1120.

[0137] The content of the post-correction information is displayed as suggested correction information in the post-correction area 1121. That is, in the example screen shown in Fig. 11, post-correction information of the correspondence relationship information extracted based on the description content of the target item (here, Article 1 of the target document) is displayed. The user can refer to the post-correction information displayed in the post-correction area 1121 and correct the target item.

[0138] The user can also refer to the contents displayed in the status area 1123, type area 1124, and user name area 1125 to modify the target item.

[0139] That is, for example, if the status information displayed in the status area 1123 is "reviewed," the user can recognize the suggested revision information displayed in the first suggestion area 1120 as information based on a historical document that has been reviewed by the user's own company.

[0140] Also, for example, if the type information and position information displayed in the type etc. area 1124 are the same as the type and position of the target document, the user can recognize the suggested revision information displayed in the first proposal area 1120 as information based on a history document of the same type or position as the target document.

[0141] Furthermore, for example, if the information indicating the modifying user and date displayed in the modifying user name etc. area 1125 indicates a reliable person in charge or indicates a date close to the present, the user can recognize the proposed modification information displayed in the first proposal area 1120 as more appropriate proposed modification information. That is, the user can determine whether or not the modification in the historical document was made by a reliable modifying user or whether the modification in the historical document was made on a date close to the present, and then determine whether or not to modify the target document based on the proposed modification information.

[0142] As such, the edit user name area 1125 displays information indicating the edit user. In this regard, the edit user of the historical document may be different from the person who uploaded the historical document to the edit suggestion system 10. In such a case, for example, if the person who uploaded the historical document to the edit suggestion system 10 manually generates an old version of the document using an editing application and then uploads the old version of the document to the edit suggestion system 10, the "edit user" may be treated as the uploader in the edit suggestion system 10. Therefore, by classifying groups by edit user in the edit suggestion system 10 (particularly the document management system 100) and generating old versions of the document for each group, the person who made the edits can be accurately displayed on the user terminal 200. This allows the user to more appropriately determine whether to edit the target document based on the edit suggestion information.

[0143] Furthermore, when the first comment button area 1122 is selected, the screen switches to the screen shown in FIG. 12, which will be described later, which displays comment information included in the history document in the extracted correspondence information.

[0144] The user can then refer to the comment information to correct the target item. That is, the user can understand, for example, the intention of the correction in the history document contained in the comment information, and determine whether to correct the target document based on the correction suggestion information.

[0145] Furthermore, when the reference button area 1126 is selected, the history document in the extracted correspondence information is displayed. The user can refer to the history document and correct the target item. That is, the user can, for example, understand other items in the history document and decide whether to correct the target document based on the correction suggestion information.

[0146] The displayed history document may be displayed on the user terminal 200 in a window separate from the window displaying the screen shown in FIG.

[0147] Fig. 12 is a diagram showing an example of provision of revision suggestion information by the revision suggestion unit 165. The example screen shown in Fig. 12 corresponds to Fig. 11, but shows an example of the screen when the first comment button area 1122 in Fig. 11 is selected and comment information is displayed.

[0148] The screen shown in FIG. 12 includes a second comment button area 1127 that displays a button for hiding comment information in the history document, and a comment area 1128 that displays comment information in the history document.

[0149] When the second comment button area 1127 is selected, the screen switches to the screen shown in Fig. 11, in which comment information is not displayed. The user can refer to the comment information displayed in the comment area 1128 to correct the target item. That is, the user can understand, for example, the intention of the correction in the history document contained in the comment information, and decide whether to correct the target document based on the correction suggestion information.

[0150] The revision suggestion unit 165 may also display an area on the user terminal 200 that accepts a user's rating, such as a favorite, or a flag related to a suggestion. That is, for example, if the user finds the proposed revision information appropriate, the user can register the proposed revision information in their favorites. When providing the proposed revision information to the user terminal 200, the revision suggestion unit 165 may also provide information (e.g., a star mark) indicating whether the proposed revision information has been registered in their favorites. The revision suggestion system 10 may also provide the user with a list of proposed revision information registered in their favorites. The revision suggestion unit 165 may also preferentially provide proposed revision information registered in their favorites to the user terminal 200. This allows the revision suggestion system 10 to make revision suggestions that are more suitable for the user. The rating and flag information may be available only to the individual user who performed the rating or flag registration operation, or may be available to other users, such as users in an organization to which the user who performed the registration operation belongs. This allows information about proposed revisions to be shared within an organization, making it possible to provide more appropriate proposed revision information. The original document of the proposed example sentence may also be displayed.

[0151] In this manner, the revision suggestion system 10 according to one embodiment of the present invention performs a revision suggestion process for each item (e.g., clause or issue). This allows the user to easily revise the target document by replacing the proposed revision items. Specifically, the user can revise the target document, for example, by simply replacing the proposed revision items, without performing revision processes that require word replacement (e.g., grammatical revision processes such as dependency corrections).

[0152] This is because an item (e.g., a clause or an issue) corresponds not to a word or character unit but to a certain range of character strings (e.g., a paragraph, a sentence, or a clause) that indicates a certain meaning, and the revision suggestion information generation unit 160 generates the revision suggestion information based on the revised information divided into items.

[0153] The correction suggestion system 10 according to an embodiment of the present invention may use words as items, that is, the correction suggestion system 10 may perform the correction suggestion process for each word.

[0154] FIG. 13 is a flowchart showing an example of processing by the document management system 100.

[0155] First, the history document acquisition unit 115 acquires a history document (S1301).The group classification unit 120 classifies the revision history information into at least one group according to the revision process of the history document (S1302).

[0156] The old-version generating unit 125 generates at least one old-version document for each group, associates the old-version document with version information, and stores the old-version document in memory (S1303).Then, the output unit 130 outputs information for displaying the revision process (S1304).

[0157] FIG. 14 is a flowchart showing an example of the processing of the correction suggestion system 10.

[0158] First, the target document acquisition unit 140 acquires the target document (S1401). The item division unit 145 divides the history document, the old version document, and the target document by item, and generates post-edit information, pre-edit information, and target information, respectively (S1402).

[0159] The correspondence setting unit 150 generates correspondence information that associates the pre-edited information with the post-edited information according to the edit process (S1403). The correspondence extraction unit 155 extracts at least one piece of correspondence information from the pre-edited information and the post-edited information based on the target information in the target document (S1404).

[0160] The revision proposal information generation unit 160 generates revision proposal information regarding a proposal for a revision of the target item in the target document based on the post-correction information contained in at least one of the extracted correspondence information, and the revision proposal unit 165 provides the revision proposal information to the user terminal 200 (S1405).

[0161] 15, an example of a hardware configuration in which the correction suggestion system 10 is realized by a computer 1500 will be described.

[0162] As shown in FIG. 15, a computer 1500 includes, for example, a processor 1501, a memory 1502, a storage device 1503, an input I / F unit 1504, a data I / F unit 1505, a communication I / F unit 1506, and a display device 1507.

[0163] Computer 1500 may be, for example, a server computer, a personal computer (e.g., desktop, laptop, tablet, etc.), a media computing platform (e.g., cable, satellite set-top box, digital video recorder, etc.), a handheld computing device (e.g., PDA, email client, etc.), or any other type of computing or communications platform.

[0164] The processor 1501 is a control unit that controls various processes in the computer 1500 by executing programs stored in the memory 1502 .

[0165] The memory 1502 is a storage medium such as a RAM (Random Access Memory), etc. The memory 1502 temporarily stores the program code of the program executed by the processor 1501 and data required when the program is executed.

[0166] The storage device 1503 is a non-volatile storage medium such as a hard disk drive (HDD), flash memory, etc. The storage device 1503 stores an operating system and various programs for realizing the above-mentioned components.

[0167] The input I / F unit 1504 is a device for receiving input from a user. The input I / F unit 1504 is, for example, a keyboard, a mouse, a touch panel, various sensors, a wearable device, etc. The input I / F unit 1504 may be connected to the computer 1500 via an interface such as a USB (Universal Serial Bus).

[0168] The data I / F unit 1505 is a device for inputting data from outside the computer 1500. The data I / F unit 1505 is, for example, a drive device for reading data stored in various storage media. The data I / F unit 1505 may be provided outside the computer 1500. When the data I / F unit 1505 is provided outside the computer 1500, the data I / F unit 1505 is connected to the computer 1500 via an interface such as a USB.

[0169] The communication I / F unit 1506 is a device for performing data communication via a network such as the Internet, either wired or wirelessly, with devices external to the computer 1500. The communication I / F unit 1506 may be provided outside the computer 1500. When the communication I / F unit 1506 is provided outside the computer 1500, the communication I / F unit 1506 is connected to the computer 1500 via an interface such as a USB.

[0170] The display device 1507 is a device for displaying various types of information. The display device 1507 is, for example, a liquid crystal display, an organic EL (Electro-Luminescence) display, a display of a wearable device, or the like. The display device 1507 may be provided outside the computer 1500. When the display device 1507 is provided outside the computer 1500, the display device 1507 is connected to the computer 1500 via, for example, a display cable. Furthermore, when a touch panel is adopted as the input I / F unit 1504, the display device 1507 may be configured as an integral part of the input I / F unit 1504.

[0171] The above describes one embodiment of the present invention. The document management system 100 acquires an electronic document including revision history information, generates an old version of the document according to the revision process corresponding to the revision history based on the electronic document and the revision history information, and stores the old version of the document in memory in association with version information related to the version of the document in the revision process corresponding to the old version of the document. This allows the document management system 100 to manage electronic documents including revision histories.

[0172] Furthermore, the document management system 100 can classify the revision history information into groups corresponding to the revision process and generate old versions of documents for each group. This allows the document management system 100 to manage electronic documents that include revision histories based on groups corresponding to the revision process.

[0173] Furthermore, the document management system 100 can classify revision history information, which includes at least one of revision user information and revision date information, based on at least one of the revision user information and revision date information, thereby enabling users to manage electronic documents and older versions of documents in units of revision processes that are easy for users to manage.

[0174] Furthermore, the document management system 100 can classify the revision history information into multiple groups, generate a first old-version document and a second old-version document based on the electronic document and the revision history information, associate the first old-version document with the first version information and store it in memory, and associate the second old-version document with the second version information and store it in memory. This allows the user to manage an electronic document that has undergone multiple revision processes by dividing it into versions according to the revision process.

[0175] Furthermore, the document management system 100 can output information for displaying the revision process of the old version of the document to the user terminal 200. This allows the user to understand the revision process of the old version of the document.

[0176] The revision suggestion system 10 can also provide revision suggestion information relating to a proposed revision of a target item in a target document based on post-revision information indicating the content of an item in an electronic document including revision history information, the post-revision information being stored in memory in association with the pre-revision information according to a revision process that has been performed on the pre-revision information of an older version of the document generated based on the revision history information. This allows the revision suggestion system 10 to make revision suggestions for an electronic document including a revision history.

[0177] Furthermore, the revision suggestion system 10 can provide revision suggestion information based on post-revision information associated with pre-revision information that is highly relevant to the target item of the target document, thereby allowing the user to receive revision suggestions based on the post-revision information related to the target item.

[0178] Furthermore, the revision suggestion system 10 can provide revision suggestion information including post-revision information, thereby enabling the user to receive revision suggestions based on past revision results.

[0179] It should be noted that the present embodiment is provided to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and equivalents thereof are also included in the present invention.

[0180] In addition, in the present invention, a "unit" does not simply mean a physical means, but also includes cases where the functions of the "unit" are realized by software. Furthermore, the functions of one "unit" or device may be realized by two or more physical means, devices, or software, and the functions of two or more "units" or devices may be realized by one physical means, device, or software.

[0181] 110 Memory unit, 115 History document acquisition unit, 120 Group classification unit, 125 Old version generation unit, 130 Output unit, 135 Memory unit, 140 Target document acquisition unit, 145 Item division unit, 150 Correspondence setting unit, 155 Correspondence extraction unit, 160 Correction proposal information generation unit, 165 Correction proposal unit, 200 User terminal, 1500 Computer, 1501 Processor, 1502 Memory, 1503 Storage device, 1504 Input I / F unit, 1505 Data I / F unit, 1506 Communication I / F unit, 1507 Display device

Claims

[Claim 1] A document management method executed by a processor, To obtain an electronic document containing revision history information regarding the revision history, Based on the aforementioned electronic document and the revision history information, generate at least one previous version document which is a previous version of the electronic document corresponding to the revision process corresponding to the revision history, The at least one previous version of the document is stored in memory in association with version information relating to the version of the document in the revision process corresponding to the at least one previous version of the document, A document management method that includes this.