Database Interface Metadata Segmentation for Data Subset Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Non-technical skilled users face challenges in efficiently retrieving and presenting complex data from large databases without requiring specialized programming skills, as existing tools often rely on generic query tools that provide summarized data in lengthy lists rather than user-friendly, task-specific displays.

Innovation Solution

A method and system for creating a complex graphical user interface using generic database software that defines metadata for a specific data subset domain, including Task Specifications, Report Specifications, and View Specifications, allowing users to navigate and modify domain-specific data sets through a user-friendly interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If generic query tools are used to retrieve data from large databases, then data retrieval capability is provided, but the data is presented in lengthy lists with mere summary lines rather than user-friendly displays

Engineering Contradiction:
Improvedata presentation usabilityVSAvoiddata detail visibility
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent segments the database information into multiple hierarchical levels. The first level provides summary information in a condensed format, while subsequent levels provide progressively more detailed information. This allows users to navigate from high-level overviews to specific data details as needed, resolving the contradiction between concise presentation and complete information visibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a temporal dimension to data presentation by implementing drill-down capability. Instead of presenting all data in a single flat list, the system organizes data across multiple temporal levels (summary level, detail level, granular level), allowing users to navigate through time-dimensional layers of information density to achieve both brevity and completeness.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If specialized database programming skills are required to efficiently retrieve data, then data retrieval efficiency is improved, but the system becomes inaccessible to non-technical users

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoiduser accessibility
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary layer between the database and the user - a specialized software application with a graphical user interface. This intermediary handles the complex query formulation and data retrieval operations, while presenting simplified interactions to users. The GUI acts as a mediator that translates user-friendly operations into efficient database queries, resolving the contradiction between retrieval efficiency and user accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service capabilities where the software automatically performs complex data retrieval operations without requiring user intervention in the programming aspect. The application autonomously formulates and executes optimized queries based on user selections, eliminating the need for users to possess programming skills while maintaining high retrieval efficiency through automated optimization.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If a complex database system is designed to meet many usage requirements, then system versatility is improved, but the interface complexity increases

Engineering Contradiction:
Improveusage requirement coverageVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by providing different interface complexities for different user needs and contexts. The system offers simplified views for common operations while providing access to advanced features when needed. Each user interaction context receives appropriately tailored interface complexity - simple for routine tasks, more complex for specialized operations - resolving the contradiction between versatility and interface simplicity.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The interface implements dynamic adaptation based on user behavior, data context, and operational state. The system adjusts the displayed information density, navigation options, and available operations dynamically rather than presenting a static complex interface. This dynamic behavior allows the interface to remain simple for common operations while providing comprehensive functionality when required, resolving the versatility-complexity contradiction.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9672228B2Methods and systems for creating a complex user interface adapting a generic database software application to individually manage subset domains in complex database
Publication Date: 2017.06.06 HONEYWELL INTERNATIONAL INC
  • US9672228B2 patent drawing
  • US9672228B2 patent drawing
  • US9672228B2 patent drawing

AI summary

Methods are provided for creating a complex user interface using a generic computer readable database software application to manage only a specific data subset domain of the database in accordance with a work package. The method comprises creating metadata defining a data subset domain, the metadata including a task specification, a report specification and a view specification and defining attribute metadata, entity metadata and relationship metadata for the data subset domain. The method also comprises data package specification for the data subset domain, specifying a data package hierarchy within the data subset domain, specifying user groups for the data subset domain, specifying view specifications for the user groups. Further the view specification is associated with the task specification and the report specification after which the generic software application is released to a user.