Document Collaboration via Layered Event Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current document collaboration systems are inefficient and non-concurrent, requiring sequential user input and file version management, leading to delays and confusion, especially when multiple users need to collaborate on the same document.
Innovation Solution
A document collaboration system that allows multiple users to concurrently view and edit a shared document, with real-time annotation and modification capabilities, using user layers and meta-data to track changes and maintain document history, enabling selective viewing and management of user contributions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If sequential file version management is used for document collaboration, then each user can individually edit and save versions, but the process creates delays and requires waiting for each user turn to complete before the next user can begin
Solution Approach 1:
The patent segments the document into a base version and multiple annotation layers, where each user's edits are stored as separate annotation objects rather than sequential file versions. This allows concurrent access to the base document while maintaining individual user contributions in separate layers, eliminating the need to wait for sequential version saves.
Solution Approach 2:
The patent transitions from a temporal dimension of version management (v1, v2, v3) to a spatial dimension of layer management (base layer, annotation layer 1, annotation layer 2). This dimensional change enables multiple users to work simultaneously on different layers without blocking each other, as annotations are叠加 on the base document rather than requiring sequential overwrites.
2Adaptability or versatility
If multiple users create separate document files for their edits, then each user can work independently, but multiple users need to look at each different version file to understand all inputs, which is slow and inefficient
Solution Approach 1:
The patent merges all user annotations into a single shared annotation layer that is visible to all users simultaneously. Instead of each user viewing separate version files, all users view the base document with all annotations overlaid in one consolidated view, enabling efficient collaboration while maintaining independent editing capabilities.
Solution Approach 2:
The patent creates a copy of the base document for each user's annotations rather than requiring users to view multiple version files. Each user's edits are copied into separate annotation layers that can be independently managed but are all displayed together in the final view, simplifying the collaboration process.
3Loss of information
If red-lined markup versions are created for each user edit, then changes are tracked, but the process creates more and more new separate document files leading to complexity in managing multiple versions
Solution Approach 1:
The patent segments change tracking into discrete annotation objects within annotation layers rather than creating separate document files. Each annotation is an independent object that can be tracked, identified, and managed individually, reducing the complexity of version management while maintaining complete change tracking capabilities.
Solution Approach 2:
The patent moves from managing versions across temporal dimensions (file names like v1, v2, v3) to managing annotations across spatial dimensions (layer 1, layer 2, layer 3). This dimensional transformation simplifies the management structure while preserving the ability to track all changes made by all users.
Data Source
AI summary
A plurality of computing appliances, each used by a respective user, provide for collaboration on a common project having an associated base image display. Data is stored in each of a plurality of separate respective data layers, of respective user data associated with a respective display for a respective user, responsive to user input. The user data is comprised of event content data (comprised of change reference data, and change content data, wherein the event content data is representative of a unique event, for each input by the respective user) generated in a defined order of entry relative to other of the events. Mapping logic defines a mapping of event content to corresponding respective data layers. A plurality of events is selected as a selected set of events. Event content data for said events in the selected set are retrieved from respective data layers, and used to generate presentation data.