Semantic Layer Nested Group Hierarchies for Analytics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data storage systems for analytics applications do not allow end users to dynamically create hierarchies, leading to inefficient data retrieval and storage overburden, as they rely on database administrator configurations that consume storage space and hinder efficient analytics functions.
Innovation Solution
A computer system configured to create a hierarchy object in a semantic layer based on user-defined hierarchical relationships, allowing end users to dynamically create and manage nested group hierarchies without adding metadata to the database layer, enabling efficient data retrieval and display in a hierarchical format.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If database administrator configures hierarchies in the database, then hierarchical data structure is established, but storage space is consumed and database performance is degraded
Solution Approach 1:
The patent introduces a semantic layer as an intermediary between the database layer and the application layer. This semantic layer stores hierarchy definitions and metadata, acting as a mediator that provides hierarchical structure to applications without requiring the database itself to store hierarchical relationship data. The database remains in its native relational format while the semantic layer translates and presents data in hierarchical form when needed.
2Stability of the object's composition
If database administrator configures hierarchies, then hierarchical structure is created, but end user dynamic creation capability is lost
Solution Approach 1:
The patent enables end users to self-configure hierarchical structures through the semantic layer without requiring database administrator intervention. Users can dynamically create, modify, and manage hierarchy definitions through user interfaces that interact with the semantic layer, allowing the system to serve its own configuration needs without external administrative assistance.
3Stability of the object's composition
If hierarchical data is stored in the database, then data retrieval follows hierarchical structure, but data retrieval efficiency is reduced due to database overburden
Solution Approach 1:
The patent segments the system into distinct layers: the database layer stores raw data in its optimal format without hierarchical overhead, the semantic layer handles hierarchy definitions and data transformation, and the application layer consumes hierarchical results. This segmentation allows each layer to operate independently at peak efficiency, with the database focused on fast data retrieval and the semantic layer focused on hierarchical structure management.
Data Source
AI summary
Techniques for implementing nested group hierarchies for analytics applications are disclosed. In some embodiments, a computer-implemented method comprises: creating a hierarchy object in a semantic layer based on a request comprising a definition for a nested group hierarchy, the definition specifying a hierarchical relationship structure for non-leaf group nodes and at least one leaf node, the non-leaf group nodes and the leaf node(s) corresponding to data stored in a data source in a non-hierarchical structure, the hierarchy object specifying the hierarchical relationship structure based on the definition; generating a query result based on a request comprising an indication of the hierarchy object using the hierarchy object from the semantic layer to retrieve the data from the data source; and causing the query result to be displayed on a computing device using the hierarchy object to display the retrieved data in a hierarchical format indicating the hierarchical relationship structure.