Knowledge Graph Data Versioning with Immutable Published States
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack an efficient method for managing and auditing versions of data assets in knowledge graphs, particularly in enterprise data systems, where prior versions are not retained and changes are not accurately tracked.
Innovation Solution
A knowledge graph system that retains prior versions of data assets, allowing new versions to be added and approved before publication, with status indicators determining editability, ensuring that published versions are immutable and maintaining an accurate audit trail.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If prior versions of data assets are retained in the knowledge graph, then version management and auditing capability is improved, but system complexity and storage requirements increase
Solution Approach 1:
The patent segments version management by introducing distinct version nodes (e.g., version1, version2) that are connected to the root data asset node. Each version node stores specific version data independently, allowing the system to retain multiple versions without conflating them in a single structure. This segmentation enables reliable version tracking and auditing while maintaining manageable system complexity through modular organization.
2Reliability
If status indicators are used to control editability of data versions, then data integrity and publication control are improved, but operational complexity increases
Solution Approach 1:
The patent uses status indicators that function similarly to color-coded states to represent different versions of data assets. Published versions are marked with distinct status indicators from draft versions, providing visual differentiation that helps users quickly identify which versions are editable and which are published. This approach maintains data integrity through clear state management while reducing operational complexity by making version status immediately recognizable without requiring complex queries or checks.
Data Source
AI summary
A method includes storing data in a knowledge graph stored in a database. The knowledge graph is defined by nodes connected by edges, in which a root node of the knowledge graph is connected to a first version node by a first edge. The root node represents a data asset, and the first version node represents a first version of the data asset. A status indicator associated with the first version node has a first state indicating that the first version of the data asset is an editable draft version of the data asset. Responsive to receiving an instruction to publish the first version of the data asset, the state of the status indicator is changed to a second state that indicates that the first version of the data asset is a published version of the data asset.