Document Revision History Reconstruction for Version Navigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing document management systems fail to effectively manage and utilize revision history information, making it difficult for users to refer to and manage multiple versions of electronic documents, particularly contract documents, which require careful review and revision by multiple parties.
Innovation Solution
A document management system that generates old version documents based on revision steps and stores them in association with version information, allowing users to manage and reference document versions systematically, and a revision proposal system that suggests revisions based on past revision histories.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If revision history information is stored without generating separate old version documents, then storage space is saved and device complexity is reduced, but users cannot effectively manage and refer to multiple document versions
Solution Approach 1:
The system creates copies of old version documents by extracting and storing document content at specific revision steps. These copies are stored in association with version information, allowing users to reference past versions without requiring the original document structure to be maintained separately.
Solution Approach 2:
The revision history is segmented into discrete revision steps, and the document is divided into versioned segments. Each old version document corresponds to a specific revision step, enabling users to navigate and reference specific versions independently.
2Loss of information
If multiple old version documents are stored for each revision step, then users can reference past versions effectively, but storage space increases and device complexity increases
Solution Approach 1:
Instead of storing complete original documents for every version, the system creates targeted copies of only the necessary document portions at each revision step. These copies are stored in association with version information, reducing redundant storage while maintaining accessibility.
Solution Approach 2:
The system extracts and stores only the essential document content and version information needed for reference, rather than storing entire document histories. This extraction approach reduces the quantity of data stored while preserving revision history accessibility.
3Ease of operation
If revision history is not systematically organized with version information, then device complexity is reduced, but users cannot systematically manage and navigate document versions
Solution Approach 1:
The system performs preliminary organization of revision history data by pre-establishing version information associations before user access is needed. Revision steps are pre-linked with version information, creating a structured framework that simplifies future navigation and reference operations.
Solution Approach 2:
The version information association structure serves multiple functions: it enables document retrieval, version comparison, revision tracking, and historical reference. This multi-functional design simplifies data organization by using a single systematic approach for various operations.
Data Source
AI summary
A document management method executed by a processor includes: acquiring an electronic document including revision history information regarding a revision history; generating at least one old version document that is an old version of the electronic document according to a revision step corresponding to the revision history based on the electronic document and the revision history information; and storing the at least one old version document in a memory in association with version information regarding a document version in the revision step corresponding to the at least one old version document.