Hybrid File System Metadata Path Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional file systems face inefficiencies when users need to access the same files across different projects or workflows, leading to difficulties in file retrieval and synchronization issues due to the one-to-one directory correspondence, resulting in multiple out-of-sync file copies.
Innovation Solution
A hybrid file system that utilizes metadata-defined paths and user-defined paths to organize and access files, allowing multiple users to access the same files through customized paths related to their projects or workflows, while maintaining file consistency and avoiding replication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If files are stored in a one-to-one directory correspondence structure, then file storage and access are simplified, but users cannot efficiently access the same files from different projects or workflows
Solution Approach 1:
The patent segments the file access path into two independent parts: a workflow-defined path component and a user-defined path component. The workflow path is determined by metadata (project name, workflow type), while the user path can be customized individually. This segmentation allows the same file to be accessed through different paths for different users/projects without replication, resolving the contradiction between simple storage structure and flexible access capability.
Solution Approach 2:
The patent introduces an intermediary mapping mechanism that connects workflow metadata to user-accessible paths. This intermediary layer (the path mapping system) translates between the standardized workflow metadata and individual user needs, enabling flexible file access without changing the underlying storage structure or requiring file replication.
2Adaptability or versatility
If files are replicated in different directories for different workflows, then users can access files from their respective workflows, but multiple copies become out of sync
Solution Approach 1:
The patent extracts the file copy operation from the workflow execution process. Instead of creating multiple file copies when a workflow starts, the system extracts only the necessary path information and metadata, and generates virtual paths dynamically. This eliminates the need for physical file replication while maintaining the ability for users to access files through workflow-specific paths, thus avoiding synchronization issues.
Solution Approach 2:
The patent uses virtual path copying rather than physical file copying. Multiple users can access the same physical file through different virtual paths constructed from workflow metadata and user-defined paths. This virtual copying approach maintains file consistency across all workflows while providing workflow-specific access capabilities.
3Device complexity
If a traditional directory hierarchy is used, then file storage is organized, but the path structure becomes complex and difficult to navigate across different projects
Solution Approach 1:
The patent makes the file access path dynamic rather than static. Instead of using a fixed directory hierarchy, the path is constructed dynamically based on workflow metadata and user-defined preferences. This dynamic path generation simplifies navigation by presenting users with relevant paths based on their current workflow context, while the underlying storage structure remains organized.
Data Source
AI summary
A hybrid file system provides access to files based on metadata-defined paths, user-defined paths, and/or hybrid metadata-defined paths. A metadata-defined path may be defined based on file metadata, and may provide access to files that are tagged with the same metadata that is used to specify the metadata-defined path. Some of the same files may be alternatively accessed using user-defined paths that provide access to the directories where the files are stored. Some of the same files may be alternatively accessed using a hybrid metadata-user-defined path that appends a directory structure to the metadata-defined path in order to provide direct access to a subset of files from the metadata-defined path that are placed into the metadata-user-defined path without accessing other files from the metadata-defined path.