Semantic Layer Set Segmentation for Dynamic Data Foundation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing semantic layer universes in enterprise software systems face challenges in dynamically enhancing capabilities and maintaining integrity and security, as users often require frequent updates and enhancements that are not easily integrated into the original authoring level, leading to incompatibilities and security concerns.
Innovation Solution
The solution involves creating semantic layer sets that can be linked to the universe, allowing for the consolidation of additional features and enhancements at a consumption level, enabling users to dynamically extend the universe with new methods and data representations, while maintaining security through secured universes and set containers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users dynamically enhance semantic layer universe capabilities, then adaptability and functionality are improved, but system integrity and security may deteriorate
Solution Approach 1:
The patent segments the semantic layer universe into distinct components: the core universe and separate sets. Users can create and manage sets independently without modifying the core universe structure. This segmentation allows dynamic enhancement through sets while preserving the integrity and security of the core universe, as sets are isolated units that can be added, removed, or modified without affecting the fundamental system architecture.
Solution Approach 2:
The patent introduces sets as intermediary elements between users and the core semantic layer universe. These sets act as mediators that allow users to add custom data representations, calculations, and logic without directly modifying the core universe. The intermediary layer enables dynamic user enhancements while the core universe maintains its original integrity and security constraints.
2Adaptability or versatility
If users frequently update and enhance the semantic layer universe, then functionality is improved, but system complexity and difficulty of maintenance increase
Solution Approach 1:
By dividing the system into core universe and user-created sets, the patent simplifies maintenance. The core universe remains stable and requires minimal updates, while user needs are met through separate set creations. This segmentation reduces overall system complexity by isolating changes to specific set components rather than requiring comprehensive universe updates.
Solution Approach 2:
The patent implements dynamic set management where users can create, modify, and delete sets on-demand based on changing requirements. This dynamic approach allows the system to adapt to frequent update needs without permanently increasing core complexity, as sets can be activated or deactivated without restructuring the fundamental universe architecture.
3Reliability
If the semantic layer universe structure is maintained for security, then reliability is improved, but ease of operation and dynamic enhancement are reduced
Solution Approach 1:
The sets serve as intermediary containers that provide an easy interface for user enhancements while maintaining security boundaries. Users can operate within the set framework with simplified creation and modification processes, while the underlying core universe remains protected by its original security constraints and structural integrity.
Solution Approach 2:
The patent adds a new dimensional layer (sets) on top of the existing universe structure. This additional dimension provides users with enhanced operational ease for creating custom data representations and logic, while the original universe dimension maintains its security and integrity constraints unchanged.
Data Source
AI summary
A system, method, and computer-readable medium, including creating at least one data foundation table, each of the at least one data foundation tables being created for each of one or more set tables in a database based on information stored in a first set container relying on the one or more set tables; linking at least one of the created data foundation tables to a customer table in the database, the created data foundation table being linked to the customer table based on a primary key for the customer table; and storing all of the created data foundation tables in the a dedicated data structure hosted by the first set container.


