Component State Manager for UI Data Context Preservation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing and locating specific data in large hierarchies becomes increasingly difficult as the size of data increases, leading to time-consuming navigation processes and inefficiencies, especially when sharing or accessing previously located data without repeating lengthy navigation steps.

Innovation Solution

Implementing a system that allows users to save and restore state information through a component state manager, utilizing technologies like JSF and Ajax, which enables UI components to register and store state information in an XML document, facilitating easy retrieval and sharing across different user interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If data is stored in large hierarchies with multiple tables and metadata, then data organization and context provision are improved, but data location and management difficulty increase

Engineering Contradiction:
Improvedata contextVSAvoiddata location
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent creates a simplified copy or representation of the complex data hierarchy structure that can be easily navigated and referenced. Instead of requiring users to traverse the entire multi-table hierarchy, the system generates a condensed view or pointer system that replicates the essential navigation paths, allowing quick access to data locations without exposing the full complexity of the underlying hierarchical structure.

Inventive Principle:
Principle #26Copying

2Loss of information

If comprehensive metadata and categorization are implemented, then data classification and context are improved, but navigation time and complexity increase

Engineering Contradiction:
Improvedata classificationVSAvoidnavigation time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system pre-calculates and stores navigation paths, data locations, and hierarchical relationships in advance. When a user needs to access data, the pre-computed information is immediately available without requiring real-time traversal of the complex metadata structure. This preliminary preparation of navigation data eliminates the time penalty that would otherwise accompany comprehensive metadata classification.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If detailed hierarchical structures are used for data organization, then data context and categorization are improved, but sharing data locations becomes difficult

Engineering Contradiction:
Improvedata contextVSAvoiddata sharing
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent extracts the essential location information from the complex hierarchical structure into a separate, simplified representation. This extracted data location information can be shared independently from the full hierarchical context, allowing users to share specific data locations without requiring other users to understand or navigate the complete hierarchical structure. The essential navigation data is separated from the comprehensive organizational framework.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8001145B1State management for user interfaces
Publication Date: 2011.08.16 AMAZON TECH INC
  • US8001145B1 patent drawing
  • US8001145B1 patent drawing
  • US8001145B1 patent drawing

AI summary

State information for a page can be stored and restored using a component state manager to extract and set state information for various components on a page. Each appropriate component can register with the state manager, such that when a user requests to store state information, the state manager can extract state information for each registered component and store the state information accordingly. The user can be provided with a tag or other identifier that allows the user to subsequently request recreation of that state. In response to receiving the identifier, the state manager retrieves the stored state information and sets the state of each respective registered component on the page. The identifiers can be shared with other users to allow those users to also quickly access the same state.