Universal Index Mediates Database Schema Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of multiple databases with overlapping but disparate data types and purposes is complex, requiring substantial maintenance efforts and custom code to manage variations in data field definitions and formatting, leading to increased complexity and potential integration failures.

Innovation Solution

A Universal Index system that maintains and evolves data field definitions transparently, allowing for the equivalence of data fields across databases, reducing the need for repetitive integration efforts by establishing a central point for data field equivalencies and propagating changes across integrated systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple databases with disparate data types and purposes are integrated, then data sharing and collaboration between databases is improved, but system complexity and maintenance burden increase

Engineering Contradiction:
Improvedata sharing capabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a universal index as an intermediary layer between disparate databases. This universal index contains standardized field definitions that mediate between different database schemas, allowing data exchange without direct complex integration between each database pair. The universal index acts as a translator that converts between different data formats and structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The universal index provides a universal data field definition structure that can accommodate multiple different database types and purposes. Instead of creating custom integration logic for each database pair, the system uses a single universal index that serves all databases, reducing overall system complexity while maintaining versatility.

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

2Reliability

If custom code is written to manage variations in data field definitions and formatting, then data accuracy and integrity are improved, but maintenance effort and time increase

Engineering Contradiction:
Improvedata integrityVSAvoidmaintenance time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent establishes universal index field definitions in advance, before actual data integration occurs. These pre-defined field structures include standardized formatting rules and data type definitions that are prepared beforehand. When databases are integrated, the system automatically applies these pre-established definitions rather than requiring custom code to be written for each integration scenario.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables automatic data field matching and formatting through the universal index without requiring manual intervention or custom code maintenance. The universal index automatically provides the rules and structures needed for data integration, allowing the system to self-configure and reducing the need for ongoing maintenance of custom integration code.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If data field definitions are standardized across databases, then integration ease is improved, but adaptability to specific database purposes decreases

Engineering Contradiction:
Improveintegration easeVSAvoiddatabase purpose flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent allows each database to maintain its own specific field definitions and formatting characteristics while also providing a universal index with standardized definitions. The system can apply local, database-specific definitions when needed while falling back to universal standardized definitions for common operations. This enables both standardization for ease of integration and local customization for specific database purposes.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8515903B2Collaboration of plural databases by interaction through universal index
Publication Date: 2013.08.20 DATABASE LOGIC
  • US8515903B2 patent drawing
  • US8515903B2 patent drawing
  • US8515903B2 patent drawing

AI summary

For integrating diverse databases, a server and universal index are provided to support a lexicon of variable definitions and formatting information. Subscribing databases establish equivalences between local variables and variables in the universal index, either directly or with translation such as a format conversion. For managing qualifying, preliminary processes can analyze database schema and stored variable values to assess likely matches between variables and universal definitions in the lexicon, presented tentatively to the local operator for approval or rejection. Matches can become approved for use in interaction with other subscribing databases. Processes enable the universal lexicon to be revised, e.g., expanded when a variable does not appear to match an existing definition. The universal index server can function as a data intermediary, or as a source of index definitions. Databases can indicate their compliance with the index during transmission of variable data referenced to index definitions.