JSON Schema Compacting for Data Mapping Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Information handling systems face challenges in mapping and managing data schemas, particularly when dealing with unspecified JavaScript Object Notation (JSON) schemas from product suppliers, which vary and need to be aligned with defined schemas used by data center services providers, including relational databases, to ensure seamless data processing and storage.
Innovation Solution
A method and system for performing data schema mapping operations, involving receiving product information in an unspecified JSON schema, compacting JSON data elements, and mapping them to a defined schema associated with a data center services provider, including components related to relational databases, to facilitate data integration and management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If data schema mapping is performed without compacting JSON data elements, then data structure integrity is maintained, but processing time and computational resources increase
Solution Approach 1:
The patent applies preliminary action by compacting JSON data elements before performing schema mapping operations. The system identifies and compacts repetitive or redundant JSON elements in advance, creating a simplified intermediate representation that accelerates subsequent mapping processes without losing essential data structure information.
Solution Approach 2:
The patent segments the data processing workflow into distinct phases: JSON element identification, compaction operation, and schema mapping. This segmentation allows the system to optimize each phase independently, applying compaction rules to reduce data volume before the more computationally intensive schema mapping operations.
2Adaptability or versatility
If multiple unspecified JSON schemas from different product suppliers are integrated, then data source versatility increases, but schema compatibility and management complexity worsen
Solution Approach 1:
The patent introduces an intermediary compaction layer between diverse JSON schemas and the target schema. This intermediary process standardizes various supplier-specific JSON formats by applying universal compaction rules, creating a common intermediate representation that simplifies integration with the data center's defined schemas.
Solution Approach 2:
The patent implements universality through a generic JSON compaction framework that handles multiple supplier schemas through a single unified process. The compaction operation applies consistent rules across different data sources, enabling the system to manage diverse schemas through a universal mechanism rather than requiring supplier-specific handling logic.
3Productivity
If JSON data elements are compacted before mapping, then processing efficiency improves, but data element identification and compaction operation complexity increase
Solution Approach 1:
The patent applies self-service by enabling the JSON compaction process to automatically identify and process data elements without extensive manual configuration. The system autonomously analyzes the JSON structure, applies appropriate compaction rules based on data patterns, and generates the compacted representation, reducing the need for complex external orchestration.
Solution Approach 2:
The patent utilizes parameter changes by dynamically adjusting compaction based on JSON data characteristics. The system monitors data patterns and modifies compaction parameters in real-time, such as selecting different compaction strategies for different data types or nesting levels, thereby optimizing the balance between processing efficiency and operational complexity.
Data Source
AI summary
A system, method, and computer-readable medium are disclosed for performing a data schema mapping operation. The data schema mapping operation includes receiving product information from a product supplier, the product information comprising a first document corresponding to a first data schema, the first data schema comprising an unspecified JavaScript Object Notation (JSON) schema; identifying a plurality of components within the first document corresponding to the first data schema, the plurality of components comprising a plurality of JSON data elements; compacting the plurality of JSON data elements via a data schema compacting operation to provide a set of compacted JSON data elements; identifying a second plurality of components corresponding to a second data schema, the second data schema comprising a defined data schema; and, mapping a component of the document corresponding to the first data schema to a component corresponding to the second data schema.