Metadata Service for Automated Data Acquisition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in efficiently exchanging and utilizing metadata between applications, particularly in cross-application scenarios, which hinders effective data processing and integration.
Innovation Solution
A computer-implemented method and system for exchanging metadata between applications, involving a metadata service that defines a service metadata model, establishes connections to data sources, and provides views of content to acquire and transfer metadata based on queries, while utilizing scope functions to determine relevant entities and dependencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual metadata exchange methods are used between applications, then data integration can be achieved, but data processing efficiency is low and resource consumption is high
Solution Approach 1:
The metadata service enables applications to automatically acquire and exchange metadata through standardized interfaces without manual intervention. The system self-configures data sources, entities, and relationships by evaluating queries against the service metadata model, eliminating the need for manual metadata management and improving processing efficiency while reducing resource consumption.
Solution Approach 2:
The metadata service provides a universal platform that handles multiple functions including metadata acquisition, transformation, validation, and exchange across different applications. The service metadata model serves as a common framework that can represent various data sources and entities uniformly, enabling efficient cross-application data integration without application-specific customizations.
2Measurement precision
If applications exchange metadata without a standardized format, then flexibility is maintained, but data integrity is compromised and exchange accuracy decreases
Solution Approach 1:
The service metadata model defines standardized parameters and attributes for representing metadata from different data sources. By transforming application-specific metadata into this standardized format, the system ensures consistent structure, validation rules, and semantics across all exchanged metadata, improving exchange accuracy while maintaining manageability through well-defined parameters.
3Loss of information
If comprehensive metadata is transferred between applications, then data completeness is improved, but data transfer time increases and processing overhead rises
Solution Approach 1:
The system extracts and transfers only the relevant metadata entities and attributes required by the requesting application, rather than transferring all available metadata. The query evaluation mechanism identifies specific entities and relationships needed, extracting only those portions of metadata that are necessary, thus maintaining completeness of required information while reducing transfer time and processing overhead.
4Adaptability or versatility
If applications use different metadata models, then application autonomy is preserved, but interoperability is hindered and integration difficulty increases
Solution Approach 1:
The metadata service acts as an intermediary between applications with different metadata models. It receives queries from requesting applications, translates them into the service metadata model format, retrieves appropriate metadata from data sources, and returns results in a standardized format. This mediator approach preserves application autonomy while enabling seamless interoperability through standardized interfaces and transformation capabilities.
Data Source
AI summary
The present disclosure relates to computer-implemented methods, software, and systems for automatic database configuration. One example method includes receiving, at a database associated with a data warehouse application, a request to generate a configuration to acquire data objects based on executing calls to corresponding programming interfaces provided by a source application, wherein the programming interfaces are identified in the received instructions and are associated with acquiring the data objects associated with metadata entities defined at the database; in response to the received instructions, configuring the database to automatically execute one or more calls to acquire relevant data for a metadata entity defined at the database, wherein the metadata entity is associated with a section of a first programming interface; and invoking the first programming interface at the source application, wherein invoking the first programming interface results in acquiring the relevant data.