Batch Metadata Management System for Business Intelligence

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Business intelligence systems face challenges in managing large and complex metadata, leading to increased operational complexity and a higher risk of user errors due to the need for manual updates across multiple metadata layers.

Innovation Solution

A metadata management system with a user interface generator, content editor, and communication manager that facilitates batch processing of metadata modifications, automating the update of metadata names, expressions, and security settings across the business intelligence architecture, ensuring metadata integrity and reducing manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual updates are used to modify metadata across multiple layers, then flexibility and control are maintained, but operational complexity increases and user errors rise

Engineering Contradiction:
Improvemetadata integrityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service automated batch processing that allows users to initiate and monitor metadata updates without requiring deep technical knowledge of the underlying complex metadata layers. The automated engine handles the complexity internally while providing simple user interfaces for initiation and monitoring.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

An automated batch processing engine acts as an intermediary layer between users and the complex metadata repository. This intermediary automatically manages the evaluation, modification, and propagation of metadata changes across multiple layers, shielding users from operational complexity while maintaining reliability through systematic processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If manual updates are used to modify metadata across multiple layers, then precise control over each change is maintained, but the risk of user errors increases

Engineering Contradiction:
Improveease of metadata updatesVSAvoidrisk of user errors
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs self-validation and self-correction through automated evaluation of metadata content before and during batch processing. The automated engine identifies potential errors, validates syntax and semantics, and maintains rollback capabilities, eliminating the need for manual error checking while improving reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms that automatically monitor metadata changes, validate modifications against integrity rules, and provide real-time status information. This feedback loop ensures errors are detected and corrected automatically, reducing the risk associated with manual operations while maintaining ease of use.

Inventive Principle:
Principle #23Feedback

3Productivity

If automated batch processing is implemented, then user errors are reduced and efficiency improves, but system complexity increases

Engineering Contradiction:
Improvemetadata processing efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The automated batch processing system is segmented into distinct functional modules: metadata evaluation, content modification, validation, and propagation. Each module handles a specific aspect of the processing workflow, making the overall complex system manageable through clear separation of concerns while maintaining high productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The automated batch processing engine is designed as a universal system that can handle multiple types of metadata modifications across different layers through a single interface. This multi-functional approach consolidates what would otherwise require multiple separate tools, improving productivity without proportionally increasing perceived system complexity.

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

4Reliability

If comprehensive metadata evaluation is performed on each object, then metadata integrity is maintained, but processing time increases

Engineering Contradiction:
Improvemetadata integrityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary evaluation of metadata content before actual batch processing begins. This preliminary action identifies potential integrity issues in advance, allows for validation rule configuration, and prepares the processing pipeline, ensuring integrity maintenance while optimizing processing time by avoiding re-evaluation of already-validated content.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The comprehensive metadata evaluation is implemented as periodic validation rather than continuous checking. The system evaluates metadata at key checkpoints during batch processing (before modification, during propagation, and after completion) rather than continuously, maintaining integrity while minimizing time loss through strategic validation timing.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS8073863B2Batch management of metadata in a business intelligence architecture
Publication Date: 2011.12.06 AVT TECHNOLOGY SOLUTIONS LLC
  • US8073863B2 patent drawing
  • US8073863B2 patent drawing
  • US8073863B2 patent drawing

AI summary

A metadata management system is described for a business intelligence architecture having a metadata repository for content that defines a user environment of the business intelligence architecture. The metadata management system includes a user interface generator to display information regarding a plurality of objects in the metadata repository and to facilitate selection of a group of the plurality of objects, a content editor to evaluate the content stored in the metadata repository for each object of the selected group and to modify in a batch job the content for each object of the selected group for storage of the modified content in the metadata repository, and a communication manager to issue instructions for the storage of the modified content in the metadata repository, the instructions being configured in accordance with a communication protocol of the business intelligence architecture utilized to control the metadata repository.