Graph File System Interface for Relationship-Aware File Operations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional graphical user interfaces (GUIs) are inadequate for navigating and manipulating data in graph-organized file systems (GOFS) due to their inability to represent complex relationships between files, making it impractical to perform operations like deletion and search functions effectively.

Innovation Solution

A graphical user interface (GOFS UI) is developed to visualize and manipulate data in GOFS by depicting files as nodes and relationships as edges, enabling user-friendly navigation, operations, and search functionality, with manual and automatic graph readjustment to prevent orphan nodes during deletions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a traditional file system GUI is used to access GOFS, then the interface is familiar and easy to learn, but it cannot represent complex relationships between files

Engineering Contradiction:
Improveease of useVSAvoidability to represent complex relationships
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent transitions from a two-dimensional hierarchical tree structure to a multi-dimensional graph structure that can represent complex relationships between files. The graph structure allows nodes (files) to be connected through multiple types of edges (relationships) in a non-hierarchical manner, enabling representation of many-to-many relationships, cycles, and complex dependencies that cannot be expressed in traditional hierarchical file systems.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If a graph structure is implemented to represent complex relationships, then relationship representation capability is improved, but the complexity of the interface increases

Engineering Contradiction:
Improveability to represent complex relationshipsVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the complex graph interface into manageable components: nodes representing files, edges representing relationships, and different view modes for navigation. This segmentation allows the complex information to be presented in a structured, organized manner that reduces cognitive load while maintaining the full representational power of the graph structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic visualization where the graph structure can be interactively explored, zoomed, and filtered based on user needs. The interface adapts its complexity level dynamically, allowing users to view high-level overviews or drill down into specific relationship details, thus managing interface complexity while maintaining full functionality.

Inventive Principle:
Principle #15Dynamics

3Productivity

If file deletion is performed in GOFS, then space is freed, but orphan nodes may be created disrupting graph integrity

Engineering Contradiction:
Improvedeletion efficiencyVSAvoidgraph integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms that monitor the graph structure during deletion operations. When a file is deleted, the system automatically detects and identifies orphan nodes (nodes that have become disconnected from the main graph), and provides feedback to the user or automatically performs actions to restore graph integrity, such as reassigning parent directories or notifying the user of the deletion's impact.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary checks before executing deletion operations to identify potential orphan nodes and assess the impact on graph integrity. This preliminary action allows the system to prepare appropriate remediation strategies in advance, such as suggesting alternative parent directories or warning users about potential graph disruption, thereby maintaining reliability while enabling efficient deletion.

Inventive Principle:
Principle #10Preliminary action

4Difficulty of detecting and measuring

If search functionality is added to GOFS, then file location capability is improved, but the complexity of search operations increases

Engineering Contradiction:
Improvefile location capabilityVSAvoidsearch operation complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent implements a universal search mechanism that works across the entire graph structure regardless of the complexity of relationships. The search function can traverse any type of edge and any depth of the graph using a unified approach, allowing users to search for files based on various criteria (name, content, relationship type, etc.) without needing to learn different search methods for different relationship structures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20260064773A1Interface to organize and administer graph-oriented file system
Publication Date: 2026.03.05 ORACLE INT CORP
  • US20260064773A1 patent drawing
  • US20260064773A1 patent drawing
  • US20260064773A1 patent drawing

AI summary

Disclosed herein are various approaches for visualizing a graph-organized file system (GOFS) using a graphical user interface. A GOFS may represent a graph comprising a plurality of nodes and one or more edges representing one or more relationships between the plurality of nodes. A user interface comprising a representation of at least a portion of the graph may be rendered in a display accessible to one or more computing devices. A file system command for the GOFS may be received via the user interface, and the user interface may be modified based at least in part on executing the file system command.