Metadata Tagging for Automated Application Merging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing metadata-based applications face challenges in integrating new functionality with existing systems, as new definitions often lack consistent properties and manual reconciliation is costly in terms of time and effort.

Innovation Solution

A method and system for merging metadata-based applications by determining changes, generating tags that describe database definitions, and wrapping them into a mergeable metadata application, which can be transmitted and reconciled with the target application to identify and resolve conflicts, enabling seamless integration of new functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If new functionality is integrated with existing systems using manual reconciliation, then the system can be modified and extended, but the time and effort costs increase significantly

Engineering Contradiction:
Improvesystem extensibilityVSAvoidreconciliation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining consistent properties and naming conventions in the metadata schema before integration. This allows new functionality to be defined upfront with standardized attributes, enabling automated merging without time-consuming manual reconciliation later. The metadata definitions include pre-established properties that ensure compatibility with existing systems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes parameters by transforming the integration approach from manual property-by-property reconciliation to automated merging based on standardized metadata parameters. The system uses defined properties in metadata definitions as key parameters for automated comparison and integration, fundamentally changing how system extensions are handled.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If new definitions are created to describe new functionality, then the system can be extended, but consistency with existing definitions becomes difficult to maintain

Engineering Contradiction:
Improvenew functionality definitionVSAvoiddefinition consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent applies universality by creating a standardized metadata schema that serves multiple purposes: it defines new functionality while maintaining consistency with existing definitions. The universal property definitions and naming conventions can be applied across different functionality types, ensuring both extensibility and consistency simultaneously.

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

Solution Approach 2:

The patent applies homogeneity by ensuring all metadata definitions, whether existing or new, follow the same structure, properties, and naming conventions. This homogeneous approach to metadata definition ensures that new functionality integrates seamlessly with existing definitions without compromising consistency.

Inventive Principle:
Principle #33Homogeneity

3Adaptability or versatility

If metadata definitions are extended to handle new business constructs, then the system can accommodate new concepts, but integration with existing functionality becomes increasingly challenging

Engineering Contradiction:
Improvebusiness construct coverageVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the integration process into manageable components: metadata definition, property specification, and automated merging. This segmentation allows new business constructs to be added through standardized metadata extensions without overwhelming integration complexity, as each component handles a specific aspect of the integration.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9612825B2Systems and methods for merging metadata-based applications
Publication Date: 2017.04.04 CHERWELL SOFTWARE LLC
  • US9612825B2 patent drawing
  • US9612825B2 patent drawing
  • US9612825B2 patent drawing

AI summary

Systems and methods for mergeable metadata-based applications may be provided. According to some embodiments, a method may include determining, by a computer including one or more processors, one or more changes to be made to an application on a target computer. The method may also include identifying metadata associated with the application, the metadata corresponding to the one or more changes to be made. Furthermore, the method may include generating at least one tag associated with the metadata. The at least one tag may include information that describes one or more database definitions included in the metadata. Additionally, the method may include wrapping the at least one tag and the metadata into a mergeable metadata application and transmitting, to the target computer, the mergeable metadata application.