Dynamic Data Association via Configurable Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing relational database systems require complex operations to associate data across tables, limiting flexibility and ease of use in managing both structured and unstructured data.

Innovation Solution

Implementing dynamic data association methods that allow users to create ad-hoc relationships between data items from different tables or documents within a relational database using configurable metadata, which can be unidirectional or bidirectional, and are stored in system tables, enabling flexible data management without requiring traditional database join operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional database join operations are used to associate data across tables, then data association is achieved, but device complexity and ease of operation deteriorate due to requiring complex operations and predefined schema modifications

Engineering Contradiction:
Improveease of data associationVSAvoidcomplexity of database operations
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the data association mechanism from the traditional database schema and join operations. By using configurable metadata stored in system tables, the system allows users to associate data across tables without modifying the database schema or using complex join operations, thereby simplifying the operation while maintaining data association capabilities

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces configurable metadata as an intermediary layer between data items and the database schema. This metadata acts as a mediator that defines relationships between data from different tables without requiring changes to the underlying database structure, enabling flexible data association through a simplified interface

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If ad-hoc data association is implemented without database operations, then ease of operation improves, but reliability may deteriorate due to potential conflicts with existing database operations

Engineering Contradiction:
Improveflexibility in data associationVSAvoidconsistency of data association
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements notification mechanisms that provide feedback when data items are modified. When a data item is updated, the system notifies associated metadata and triggers appropriate responses, ensuring that ad-hoc associations remain consistent with database changes and maintaining reliability while preserving user flexibility

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent makes the data association system dynamic by allowing associations to be created, modified, and deleted without requiring database schema changes. The configurable metadata can dynamically adapt to different data structures and relationships, maintaining reliability through flexible yet consistent association management

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8626795B2Dynamic data association
Publication Date: 2014.01.07 APPLE INC
  • US8626795B2 patent drawing
  • US8626795B2 patent drawing
  • US8626795B2 patent drawing

AI summary

Methods, program products, and systems implementing dynamic data association are described. Relations between a first data item and a second data item can be created in an ad hoc manner. The first data item can include a row of data in a table in a relational database. The second data item can include a row of data in the same table, in another table in the relational database, or a document outside the relational database. Configurable metadata can be created to link the first data item and the second data item. The link can be directional. The configurable metadata can include data specified by a user. The configurable metadata can be stored in one or more system tables in the relational database. The configurable metadata can be specific to the user, or to a work group of the user. The configurable metadata can change when the first data item or the second data item is modified.