Object Model for Automatic Join Type Resolution in Data Visualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Analyzing data from multiple data sources is challenging due to the difficulty in accessing and combining information from various tables and databases, particularly when users are unsure of the relationships between data objects and the need to specify join types for data visualizations.

Innovation Solution

An object model is used to organize data sets, allowing users to leverage relationships between data sets by storing them as objects and classes, enabling the creation of new data fields and visualizations without combining all data into a single set, and automatically determining join types based on user selections and object relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users manually join tables to access data from multiple data sources, then data visualization can be created, but the process becomes complex and error-prone due to the need to specify join types and understand relationships between data objects

Engineering Contradiction:
Improveease of accessing data from multiple data sourcesVSAvoidcomplexity of joining tables and specifying join types
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the object model with automatically determined join types) between the user and the underlying table structures. Instead of directly manipulating table joins, users interact with high-level data objects and their relationships, which are automatically translated into appropriate SQL join operations. This intermediary abstraction shields users from the complexity of specifying join types while still enabling access to data from multiple sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs self-service by automatically determining the appropriate join types between tables based on the object model and relationship metadata. Rather than requiring users to manually specify join types (INNER JOIN, LEFT JOIN, etc.), the system autonomously analyzes the relationships between data objects and generates the correct join logic, thereby eliminating a major source of complexity and potential errors.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If all data from multiple tables is combined into a single data set, then data analysis flexibility is improved, but aggregation errors occur due to improper joining of tables

Engineering Contradiction:
Improveflexibility in data analysisVSAvoidaccuracy of data aggregation
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-defining the relationships between data objects in the object model before data analysis occurs. The join types and relationship metadata are established in advance, ensuring that data from multiple tables is correctly associated prior to aggregation. This preliminary structuring prevents aggregation errors while maintaining the flexibility to analyze combined data across multiple sources.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If users are required to understand relationships between data objects to access data from multiple tables, then data accuracy is improved, but user productivity decreases due to the learning curve and complexity

Engineering Contradiction:
Improveaccuracy of data accessVSAvoidspeed of creating data visualizations
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system performs self-service by automatically determining the appropriate join types between tables based on the object model and relationship metadata. Rather than requiring users to manually specify join types (INNER JOIN, LEFT JOIN, etc.), the system autonomously analyzes the relationships between data objects and generates the correct join logic, thereby eliminating a major source of complexity and potential errors.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11599533B2Analyzing data using data fields from multiple objects in an object model
Publication Date: 2023.03.07 TABLEAU SOFTWARE INC
  • US11599533B2 patent drawing
  • US11599533B2 patent drawing
  • US11599533B2 patent drawing

AI summary

A method for analyzing data from data sources includes receiving user selection of a data source and displaying an interface that includes a schema region and a plurality of shelf regions. Each data field in the schema region is associated with a respective system-defined object from the data source. In a first display mode, each data field is displayed as associated with a respective system-defined object. In a second display mode, each data field is displayed in a respective user-defined folder. The method also includes displaying a data visualization according to a user placement of first and second data fields into the first and second shelf regions.