Change Tracking System for Collaborative Document Version Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Collaborative document editing systems face challenges in distinguishing between temporary and committed changes, leading to difficulties in maintaining version control and user experience, as temporary comments and edits are often indistinguishable from original content.
Innovation Solution
Implementing a system that detects content changes and categorizes them as temporary or committed, presenting these changes through distinct channels, allowing collaborators to view and manage temporary changes separately from committed ones, and storing this information as metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If change tracking is used to store temporary comments and edits in a collaborative document, then real-time collaboration efficiency is improved, but temporary changes cannot be distinguished from original document content
Solution Approach 1:
The patent segments document changes into distinct categories: original content, temporary changes, and committed changes. Each category is visually distinguished through different display treatments, allowing collaborators to clearly differentiate between types of content while maintaining real-time collaboration efficiency.
Solution Approach 2:
The patent employs color-coding to visually distinguish temporary changes from original and committed content. Temporary changes are displayed with distinct visual indicators (such as color highlighting or styling) that make them immediately recognizable, preventing confusion with permanent document content.
2Ease of operation
If all content changes are presented through the same channel, then implementation simplicity is maintained, but collaborators cannot filter or manage different types of changes effectively
Solution Approach 1:
The patent divides the change presentation system into separate channels or views: one for temporary changes and another for committed changes. This segmentation allows collaborators to filter and manage changes by type, improving ease of operation without requiring complex additional infrastructure.
3Ease of manufacture
If temporary and committed changes are stored together without distinction, then storage simplicity is maintained, but version control and document integrity become difficult to maintain
Solution Approach 1:
The patent segments stored document data into distinct categories: original content, temporary changes, and committed changes. Each category is stored with appropriate metadata markers that enable reliable version control and document integrity maintenance while keeping the storage structure relatively simple.
Solution Approach 2:
The patent introduces an intermediary layer (metadata or tracking information) that sits between the raw changes and the stored document. This intermediary layer maintains information about the nature of each change (temporary vs. committed) without complicating the core storage structure, ensuring both storage simplicity and version control reliability.
Data Source
AI summary
Additional document information may be stored through change tracking. In some examples, an application, such as a document processing application, may allow collaborative creation and/or editing of a document. As individual collaborators enter new content or make changes to existing content, the new content and/or changes go through two phases. As an individual collaborator is editing, the change is temporary. The collaborator may decide not to integrate it to the document. The temporary content may become permanent or integrated through a save action (manual or automatic). In some examples, the temporary content may be shared with other collaborators through a scheme to indicate its status as temporary giving the collaborators a true collaboration experience.