Schema Mapping via Layout and Content Visualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data transformation tools are time-consuming and prone to errors, particularly for non-technical users, as they require manual mapping and debugging without providing actual data values, making it difficult to interpret schema elements and ensure consistency between heterogeneous data sources.

Innovation Solution

A computer-implemented method and system for schema mapping and data transformation that displays layouts of source and target documents with data values, allowing users to create associations between elements through a graphical user interface, and stores these associations with layout data for mapping, enabling direct data transformation and consistency management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If existing mapping tools are used to transform data between schemas, then data transformation capability is provided, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improvedata transformation efficiencyVSAvoidmapping accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system enables self-service mapping by automatically analyzing data values and suggesting mappings between source and target schemas. The tool autonomously processes data instances, identifies corresponding elements based on value patterns, and generates mapping recommendations without requiring extensive manual intervention, thereby improving both efficiency and accuracy

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms by displaying actual data values during the mapping process and allowing users to verify and adjust automated mapping suggestions. This feedback loop enables users to confirm whether suggested mappings are correct based on real data evidence, reducing errors while maintaining high productivity

Inventive Principle:
Principle #23Feedback

2Ease of operation

If manual schema mapping is performed without data values, then mapping structure can be defined, but interpretation of schema elements becomes difficult and error-prone

Engineering Contradiction:
Improveschema element interpretabilityVSAvoidmapping correctness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary action by loading and displaying actual data values from source and target schemas before the user performs mapping. This allows users to understand the meaning and content of schema elements in advance, making the mapping process more intuitive and accurate

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces data values as an intermediary between the user and schema elements. Instead of directly mapping abstract schema definitions, users can reference actual data instances that illustrate what the schemas represent, making interpretation easier and mapping more reliable

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If existing mapping tools require debugging cycles, then transformation results can be verified, but the process becomes time-consuming

Engineering Contradiction:
Improvetransformation verificationVSAvoidmapping development time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary verification by displaying mapping results with actual data values immediately after mapping is defined, rather than requiring a separate debugging cycle. Users can see the transformed data and verify correctness in real-time, significantly reducing the time needed for verification while maintaining reliability

Inventive Principle:
Principle #10Preliminary action

4Device complexity

If tools work at technical schema level without data values, then mapping structure can be created, but user understanding of schema meaning is limited

Engineering Contradiction:
Improvemapping interface simplicityVSAvoidschema element meaning
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The system merges the schema structure view with actual data value display in a unified interface. Users can simultaneously see the structural relationship between schema elements and the actual data values they contain, maintaining interface simplicity while preserving complete information about schema meaning

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8234312B2Schema mapping and data transformation on the basis of layout and content
Publication Date: 2012.07.31 SAP SE
  • US8234312B2 patent drawing
  • US8234312B2 patent drawing
  • US8234312B2 patent drawing

AI summary

Systems and methods are provided for schema mapping and the transformation of data. In accordance with one implementation, a computer-implemented method is provided that includes the steps of simultaneously displaying to a user, via a graphical user interface, layouts of the first and second documents, wherein the first and second documents have different data schemas and are instantiated with elements containing data values, and acquiring one or more associations from the user to map a first element of the first document to a second element of the second document. The method further includes the steps of indicating to the user a second association between elements in the first and second documents based on the association acquired from the user, and storing the association including the layout data corresponding to the first and second elements.