Task-Level Version Control for File Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional file versioning systems are cumbersome and non-intuitive for users, especially when managing multiple files related to a single task, as they require manual tracking and versioning of individual files, leading to inefficiencies and storage issues due to duplicate file copies.
Innovation Solution
A system that implements a version control system with a database to manage tasks and their associated files and metadata, allowing for check-out and check-in of tasks, where files and metadata are versioned collectively, enabling synchronization across remote sites using merge rules to avoid conflicts and optimize storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If individual file versioning is implemented, then version control capability is provided, but user operation complexity increases and workflow becomes cumbersome
Solution Approach 1:
The patent merges multiple individual file versioning operations into a single task-level versioning operation. When a task is versioned, all associated files are automatically versioned together as a group, eliminating the need for users to manually track and version each file individually. This combining approach maintains version control reliability while dramatically simplifying user workflow.
Solution Approach 2:
The task entity serves as a universal container that manages multiple files collectively. The task versioning mechanism provides multi-functionality by simultaneously versioning all associated files, managing their relationships, and tracking changes across the entire file set through a single operation, rather than requiring separate versioning operations for each file.
2Reliability
If individual file versioning is tracked automatically, then version control is maintained, but storage duplication increases due to duplicate file copies
Solution Approach 1:
The patent combines the versioning of multiple files into a single task version record. Instead of creating separate version copies for each file, the system creates one task version that references all associated files, eliminating redundant storage of identical file copies across multiple version records and reducing overall storage duplication.
Solution Approach 2:
The system uses intelligent copying where file data is copied only when actually modified within a task version, rather than copying all files for every version. Unchanged files are referenced from previous versions, minimizing duplicate storage while maintaining complete version control tracking capability.
3Ease of operation
If multiple files are managed at individual level, then file-level control is achieved, but project management difficulty increases
Solution Approach 1:
The patent segments project management into task-level operations that group related files together. Users manage files through task containers rather than individually, which segments the complexity of project management into manageable task units. Each task handles its own files independently, reducing overall project management complexity while maintaining file-level control within each task context.
Solution Approach 2:
The task entity acts as an intermediary between individual files and project management. It mediates file operations by providing a centralized management layer that coordinates all files associated with a task, simplifying project management while preserving the ability to control and track individual files within the task context.
Data Source
AI summary
A version control system implemented on at least one server computer is provided, including: a database that stores a plurality of tasks, each task having one or more versions, each version of a given task having files that are associated thereto; a server process that manages versioning of the tasks; wherein responsive to a request to check-out a first version of the given task, the server process retrieves and serves files associated to the first version of the given task; wherein responsive to a request to check-in the previously checked-out first version of the given task, the server process generates a second version of the given task, and receives and stores files in association with the second version of the given task.