Change History Listing for Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for tracking changes in a data store with multiple write access struggle to scale effectively when there are multiple updates or changes made by different individuals to the same information, leading to data integrity issues and an overwhelming change history.

Innovation Solution

A system and process for generating a change history listing that allows users to define change objects, associate values, and display change instances with attributes such as source, date, and reasons, enabling customizable control over change capture and visualization, including the option to group changes and revert to previous versions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If known redlining and change note schemes are used to track changes, then data integrity is maintained for single updates, but the system does not scale well when there are multiple updates or changes by different individuals

Engineering Contradiction:
Improvedata integrityVSAvoidchange history management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the change tracking system into distinct change objects, each representing a specific data element that can be independently tracked. This segmentation allows the system to manage multiple changes without creating an overwhelming monolithic change history, resolving the contradiction between maintaining data integrity and managing complexity at scale.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces change objects as intermediary entities between the data store and the change tracking mechanism. These change objects serve as mediators that capture, structure, and manage change information, enabling scalable tracking of multiple updates while maintaining data integrity through a standardized interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If traditional change tracking methods are used, then simple changes are recorded, but the system becomes overwhelming when significant numbers of different individuals make changes

Engineering Contradiction:
Improvechange tracking efficiencyVSAvoidchange history volume
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges multiple change attributes (source, date, reasons, old value, new value) into unified change objects. This consolidation reduces the complexity of managing separate change records and enables efficient tracking of changes by multiple individuals without creating an overwhelming volume of分散ed change information.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The change objects serve multiple functions: they track the source of changes, record timestamps, store reasons for changes, capture before and after values, and enable revert operations. This multi-functionality allows the system to handle diverse change tracking needs with a single unified mechanism, improving productivity while controlling complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of information

If detailed change tracking is implemented for all updates, then complete change history is maintained, but the system becomes difficult to manage and visualize

Engineering Contradiction:
Improvechange history completenessVSAvoidchange history visualization
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent applies local quality by allowing users to define specific change objects with customized attributes relevant to their needs. Instead of uniformly tracking all changes with the same level of detail, the system enables selective tracking with varying degrees of information capture, maintaining completeness where needed while simplifying visualization elsewhere.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically adapts the change tracking granularity based on user-defined change objects. Users can configure which attributes to capture for different change types, allowing the system to maintain complete change history where important while keeping the interface manageable and visualizable by filtering and customizing the displayed information.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9514158B1Methods, devices, and mediums associated with generating a change history listing associated with a value of information
Publication Date: 2016.12.06 INTELLECTUAL VENTURES FUND 79 LLC
  • US9514158B1 patent drawing
  • US9514158B1 patent drawing
  • US9514158B1 patent drawing

AI summary

In an example, an electronic device may be configured to determine whether a selection is received to display a change history corresponding to a value of information. The electronic device may be configured to generate a change history listing of at least one change instance corresponding to the value of the information in response to determining that the selection is received.