Data Transformation Toolkit Automating ETL via Archetype Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing ETL tools are complex, error-prone, and require extensive expertise for data transformation, especially in large data environments with incremental updates and denormalized to normalized data transformations, leading to cumbersome and error-prone processes.

Innovation Solution

A data transformation toolkit engine that identifies a data transformation archetype based on the target field's characteristics, allowing automated transformation of source data to target data using pre-defined transformation code, reducing the need for manual engineering and minimizing errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional ETL tools are used for data transformation, then data can be transformed from source to target database, but the process becomes complex and error-prone requiring extensive software development skills

Engineering Contradiction:
Improvetransformation accuracyVSAvoiddevelopment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically generating transformation code based on archetype identification. The data transformation engine autonomously selects appropriate transformation logic without requiring manual coding, enabling the system to serve itself in creating transformation pipelines.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes the parameter of transformation approach from manual coding to automated archetype-based selection. By parameterizing the transformation process around pre-defined archetypes, the system shifts from complex custom development to simplified archetype instantiation.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If manual data transformation development is performed, then custom transformations can be created, but the process becomes cumbersome and time-consuming

Engineering Contradiction:
Improvetransformation flexibilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-defining transformation archetypes that cover common data transformation scenarios. These archetypes are prepared in advance and can be directly applied without requiring new development, thus reducing development time while maintaining adaptability through archetype selection.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The archetype-based approach provides universality by creating multi-functional transformation templates that can handle various data transformation scenarios. A single archetype framework serves multiple transformation needs, reducing the time required to develop custom transformations while maintaining flexibility.

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

3Ease of operation

If ETL tools are designed to be user-friendly with graphical interface, then accessibility improves, but handling large volumes of data from diverse sources becomes complex

Engineering Contradiction:
Improveuser accessibilityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system applies segmentation by dividing the complex data transformation process into discrete archetype components. Each archetype represents a specific transformation pattern that can be independently selected and configured, making the overall complex system manageable through modular archetype selection.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12072904B1Data transformation toolkit
Publication Date: 2024.08.27 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12072904B1 patent drawing
  • US12072904B1 patent drawing
  • US12072904B1 patent drawing

AI summary

Transformation of source data from a source field of a source table to a target field of a target table using data transformation archetypes. A set of data transformation archetypes may be defined that each comprises transformation code for transforming the source data. A data transformation archetype may be identified by a data transformation toolkit engine for application to the source data based on the target field of the target table. In this way, a characteristic or relationship of the target field (e.g., as described by a target schema and/or target semantic) may be used to identify the data transformation archetype for use in transforming source data mapped to the target field. Accordingly, a more efficient and less error-prone Export, Transform, and Load (ETL) tool may be provided that provides automation of the transformation without requiring a user to dictate the transformation operations manually.