Graph Metadata Layer for Navigable Connected Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing graph database platforms lack a systematic and agnostic way for users to understand data entities and interrelationships, and prior approaches fail to provide a user interface that can navigate metadata from a graph dataset with filters for exploring ontological interconnected domains.
Innovation Solution
Implement a framework that collects, tags, and stores metadata in a separate graph database, allowing users to explore relationships by traversing nodes, and provides an agnostic user interface for metadata and data entities, using an anthological schema model and entity-nested API server schema to automate schema and data exchange.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If graph database platforms store all data and relationships in a single database, then data completeness is maintained, but system complexity and difficulty of navigation increase
Solution Approach 1:
The patent divides the graph database system into two separate databases: a first database storing original data and a second database storing metadata about data entities and their relationships. This segmentation allows users to navigate metadata independently without being overwhelmed by the complete data set, improving ease of navigation while maintaining data completeness across both databases.
Solution Approach 2:
The patent introduces metadata as an intermediary layer between users and the actual data. This metadata layer provides an abstracted view of data entities and relationships, allowing users to explore and understand the graph structure without directly interacting with the complex underlying data, thus reducing perceived system complexity.
2Ease of operation
If a comprehensive user interface for exploring all data relationships is provided, then understanding of interrelationships improves, but interface complexity and development difficulty increase
Solution Approach 1:
The patent creates a universal metadata schema that can represent various types of data entities and relationships in a standardized way. This universal approach allows the user interface to handle diverse data types through a common framework, improving usability without requiring complex specialized interfaces for each data type, thereby reducing development difficulty.
Solution Approach 2:
The patent creates a simplified copy or representation of the actual data structure through metadata. This metadata copy contains essential information about data entities and relationships in an accessible format, allowing the user interface to work with this simplified representation rather than the full complexity of the underlying data, thus improving usability while reducing interface complexity.
3Ease of operation
If metadata is stored separately from data, then navigation and exploration become easier, but data integration and consistency management become more difficult
Solution Approach 1:
The patent establishes bidirectional relationships between the first database (data) and second database (metadata). Changes in the data database trigger updates to the metadata database, and vice versa, ensuring consistency through feedback mechanisms. This allows separate storage for improved exploration ease while maintaining reliability through automated consistency checks and updates.
Data Source
AI summary
A system can present a first graph visual representation of data of a first database in a first user interface. The system can receive user data at the first user interface that is indicative of interacting with the first graph visual representation of the data. The system can determine graph metadata for the data of the first database from the user data. The system can store the graph metadata in a second database, wherein the first database is separate from the second database. The system can determine a second graph visual representation that comprises a combination of the data of the first database and the graph metadata of the second database. The system can present the second graph visual representation in a second user interface, wherein the second user interface comprises the first user interface or another user interface other than the first user interface.