Graphical Mapping Interface for Schema Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data transformation techniques, such as custom-coded solutions and off-the-shelf products, are expensive, difficult to adapt, and require extensive programming, especially when dealing with multiple data sources and complex schema mappings, including hierarchical data structures and event-driven transformations.

Innovation Solution

A graphical mapping interface and method that includes a schema map with a main map window displaying source and target schemas, allowing for the creation of links and mini-maps to simplify complex schema mappings, support multi-mode targets, and enable event-driven transformations through Event-Condition-Action rules, facilitating data transformation between disparate data sources and targets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If custom-coded solutions or off-the-shelf products are used for data transformation, then data transformation capability is achieved, but implementation cost and complexity increase significantly

Engineering Contradiction:
Improveease of implementationVSAvoidsystem complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary component (data transformation service with visual mapping interface) that mediates between data sources and data targets. This intermediary provides pre-built transformation capabilities and visual mapping tools, eliminating the need for custom coding while managing complexity through abstraction. The service acts as a bridge that simplifies implementation for business personnel.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent employs copying by providing pre-built transformation templates, mappings, and configurations that can be reused across different data transformation scenarios. Instead of creating custom-coded solutions from scratch, users can copy and adapt existing transformation patterns, significantly reducing implementation effort and cost while maintaining consistency.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If conventional data transformation tools are used, then basic transformation functionality is provided, but adaptability to new or changing circumstances is limited

Engineering Contradiction:
ImproveadaptabilityVSAvoidease of adaptation
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent implements dynamics by providing a flexible visual mapping interface where transformation rules can be dynamically created, modified, and updated without requiring system reconfiguration or custom coding. The mapping between data sources and targets can be adapted to new scenarios by simply adjusting the visual mappings, enabling rapid response to changing business requirements.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The data transformation service provides universal functionality by supporting multiple data sources, multiple data targets, and various transformation operations through a single unified platform. The visual mapping interface can handle different data formats and structures, making the system adaptable to diverse scenarios without requiring specialized tools for each case.

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

3Productivity

If extensive programming is required for data transformation, then precise control over transformation logic is achieved, but development time and cost increase

Engineering Contradiction:
Improvetransformation speedVSAvoiddevelopment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent enables self-service by allowing business personnel to directly create and configure data transformations using the visual mapping interface without requiring programmer assistance. Users can independently define mappings, select transformation operations, and deploy transformations, eliminating the time loss associated with custom coding and programmer dependency while maintaining precise control over transformation logic.

Inventive Principle:
Principle #25Self-service

4Ease of operation

If graphical mapping tools are used, then ease of creation is improved, but support for complex hierarchical schema mappings and event-driven transformations is limited

Engineering Contradiction:
Improveease of mapping creationVSAvoidsupport for complex mappings
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent applies nesting by enabling hierarchical schema mappings where complex data structures can be represented through nested visual mappings. The system supports mapping hierarchical source schemas to hierarchical target schemas by allowing nested mapping configurations, maintaining ease of graphical creation while accommodating complex hierarchical relationships.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent uses segmentation by dividing complex transformation logic into discrete, manageable mapping elements that can be configured independently in the visual interface. Event-driven transformations are segmented into separate event handlers and action definitions, allowing complex mappings to be broken down into manageable segments that retain graphical ease of operation while supporting sophisticated transformation scenarios.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9430114B1Data transformation system, graphical mapping tool, and method for creating a schema map
Publication Date: 2016.08.30 ACTIAN CORP
  • US9430114B1 patent drawing
  • US9430114B1 patent drawing
  • US9430114B1 patent drawing

AI summary

Graphical mapping interface embodiments and method are provided for creating and displaying a schema map, which may be used by a data transformation system to perform a data transformation between at least one source schema and at least one target schema. According to one embodiment, the graphical mapping interface may comprise a source schema region for displaying a graphical representation of at least one source schema, a target schema region for displaying a graphical representation of at least one target schema, and a mapping region for displaying graphical representations of a plurality of links connecting the source nodes displayed in the source schema region to the target nodes displayed in the target schema region. The plurality of links may comprise at least one control link having at least one ECA rule associated therewith and at least one data link having at least one textual-based target field expression associated therewith.