Context-Dependent Data Management for Catalog Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current electronic catalog systems require either duplicating item entries or complex coding to present items differently based on context, such as currency or demographic, which is inefficient and prone to errors.

Innovation Solution

A context-dependent data management system that stores item data with both common and context-specific attributes, allowing for seamless selection and display of relevant data based on specified contexts, eliminating the need for duplicate entries or complex coding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If item data is duplicated for each context, then context-specific information can be stored, but data redundancy increases and system complexity grows

Engineering Contradiction:
Improvecontext-specific information storageVSAvoiddata entry complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments item data into common attributes (valid across all contexts) and context-specific attributes (valid only for particular contexts). This segmentation allows the system to store context-specific information without duplicating entire item records, reducing data redundancy while maintaining adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal data structure that can serve multiple contexts simultaneously. By using a single item record with both common and context-specific attributes, the system eliminates the need for multiple duplicate records, thereby reducing complexity while maintaining the ability to provide context-specific information.

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

2Adaptability or versatility

If complex coding is implemented in display software, then appropriate data can be selected for different contexts, but software complexity and error potential increase

Engineering Contradiction:
Improvecontext-specific data selectionVSAvoiddisplay software complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Instead of having complex display software select and filter data based on context, the patent inverts the approach by having the data structure itself organize information by context. The context-specific attributes are pre-organized within the item record, allowing simple retrieval without complex coding in the display layer.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces an intermediary data structure layer between the raw data and the display software. This intermediary structure pre-organizes data by context, acting as a mediator that simplifies the interface between data storage and display logic, thereby reducing software complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple duplicate item entries are used, then different contexts can be supported, but data management efficiency decreases

Engineering Contradiction:
Improvemulti-context supportVSAvoiddata management efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges common item attributes and context-specific attributes into a single unified item record. This consolidation eliminates the need for multiple separate records, improving data management efficiency while maintaining support for multiple contexts through the structured attribute organization.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10417685B2Context dependent data management and display
Publication Date: 2019.09.17 ORACLE INT CORP
  • US10417685B2 patent drawing
  • US10417685B2 patent drawing
  • US10417685B2 patent drawing

AI summary

A system receives a request for item data from a stored data set. The request may include a specified context for providing the item data. The stored data set includes an item, at least one common item attribute, a value for each of the common item attributes, and at least one context item attribute. The system provides the requested item data. The provided item data includes context attribute values for the specified context and common attribute values for attributes that are not in the specified context attributes.