Document Version Identification Metadata and Persistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing document versioning systems lack effective methods for users to identify and prioritize important document versions within a version history, leading to difficulties in discoverability and persistence of valuable information.
Innovation Solution
An automated system and method that allows users to append identification metadata to selected document versions, enabling improved discoverability and ensuring that important versions are persisted in storage by marking them as priority versions, thus preventing purging during storage management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If document versions are stored with basic metadata only, then storage space is conserved and system complexity is reduced, but user ability to identify important versions is poor and discoverability is low
Solution Approach 1:
The patent segments metadata into two categories: basic metadata (automatically generated, low complexity) and identification metadata (user-provided, high value). This segmentation allows the system to maintain low baseline complexity while enabling enhanced discoverability when users need it, by adding descriptive tags and keywords to specific document versions without requiring complete metadata overhaul of the entire system.
Solution Approach 2:
The system enables users to self-serve by allowing them to directly input and append identification metadata to document versions they find important. This self-service approach transfers the complexity of information organization from the system to the user, who naturally understands what makes a version important, thereby improving discoverability without significantly increasing system complexity.
2Loss of information
If all document versions are retained in storage, then no information is lost and complete history is preserved, but storage resources are consumed and storage management becomes complex
Solution Approach 1:
The patent applies local quality by differentiating the retention policy based on document version importance. Instead of uniform retention, the system marks certain versions as 'important' using identification metadata, and these marked versions are preserved while other versions may be purged. This allows the system to optimize storage resources by retaining only the locally important versions that matter to users, rather than uniformly keeping all versions.
Solution Approach 2:
The system implements a selective discarding mechanism where document versions without identification metadata or marked as less important can be discarded (purged) to free storage resources. However, versions with identification metadata indicating importance are protected from purging, ensuring that valuable information is recovered and retained. This balance allows storage optimization while preserving critical document history.
3Measurement precision
If manual identification of important document versions is required, then precise identification is achieved, but user time and effort are increased
Solution Approach 1:
The patent applies preliminary action by allowing users to mark document versions as important at the time they are created or when they become relevant. By appending identification metadata proactively rather than retrospectively searching for important versions, users perform the identification action in advance, which precisely marks the important versions and eliminates future time spent searching through version histories to locate them.
Solution Approach 2:
The system uses visual differentiation (analogous to color changes) by displaying identification metadata prominently in the version history interface. Important versions marked with identification metadata are visually distinguished from unmarked versions, allowing users to quickly scan and identify important versions without reading detailed information, thereby reducing the time required to locate important document versions while maintaining precise identification.
Data Source
AI summary
Document version discoverability and persistence are provided. A version history of a document includes snapshots of the document as it is created and edited over time. When a version history for a document is invoked, a list of the previous versions of the document is generated for display. Certain versions may be more important to a user. Upon selection of a version, an option to append identification metadata to the selected version is displayed. Received text input is appended to the version of interest, and stored as identification metadata. When a user subsequently selects to view the version history of the document, the identification metadata are displayed with the version of interest, enabling the user to quickly and easily identify the version of interest. Additionally, the version of interest is prioritized, ensuring that it is persisted and not purged when older versions are removed from storage.