Query Field Abstraction Layer for Database Usability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As databases grow in size and complexity, the number of fields presented to users in graphical user interfaces for building queries becomes unwieldy, leading to usability issues due to the inclusion of rarely used fields, which complicates the query building process.

Innovation Solution

Implementing a data repository abstraction layer that monitors and limits the number of fields presented to users based on usage characteristics, hiding or removing infrequently used fields to simplify the query building process and reduce processing overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If all fields from the data model are presented to the user in the GUI, then complete data access capability is provided, but the GUI becomes too complex and difficult for users to understand and use

Engineering Contradiction:
Improvedata access capabilityVSAvoidusability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent extracts and removes rarely used fields from the GUI field list based on usage monitoring data. The system automatically identifies fields that are not frequently accessed and excludes them from the user interface, thereby simplifying the GUI while preserving access to complete data functionality through alternative means.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements a dynamic field filtering mechanism that adapts the GUI field list based on monitored usage characteristics. The system continuously monitors which fields are actually used in queries and dynamically adjusts which fields are presented to users, making the interface adaptable to actual usage patterns rather than static.

Inventive Principle:
Principle #15Dynamics

2Loss of information

If all fields are presented to the user, then no data is lost, but the number of fields becomes unwieldy and processing overhead increases

Engineering Contradiction:
Improvedata completenessVSAvoidfield list complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements a feedback loop where the system monitors usage of fields in building queries and uses this information to automatically adjust which fields are presented in the GUI. This closed-loop system continuously optimizes the field list based on actual usage patterns, reducing complexity while maintaining data completeness.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent changes the parameter of field visibility in the GUI based on usage characteristics. By monitoring usage frequency and adjusting the visibility parameter of each field accordingly, the system transforms the static field list into a dynamically optimized set that reduces complexity without losing essential data access capabilities.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If rarely used fields are included in the GUI, then complete data model coverage is achieved, but user understanding and query building becomes difficult

Engineering Contradiction:
Improvedata model coverageVSAvoidquery building difficulty
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent extracts and removes rarely used fields from the GUI based on monitored usage patterns. By identifying fields that contribute minimally to actual query building activities and excluding them from the interface, the system reduces the cognitive load on users while maintaining comprehensive data model coverage through other access mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS7734646B2Data model simplification through field fallout
Publication Date: 2010.06.08 SAP SE
  • US7734646B2 patent drawing
  • US7734646B2 patent drawing
  • US7734646B2 patent drawing

AI summary

The present invention generally provides methods, articles of manufacture and systems for simplifying a query building process by limiting the number of fields presented to a user for building queries. The number of fields presented to the user may be limited by hiding one or more logical fields from the user based on usage characteristics. For example, a logical field that is rarely used or has not been used within a predetermined period of time may be hidden from the user. For some embodiments, a fallout manager may monitor the use of logical fields in building queries, update usage characteristics, and mark logical fields as hidden based on the usage characteristics. A graphical user interface may not present to a user logical fields that have been marked as hidden.