Editor Engine Subsetting Large Data Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data handling techniques fail to support access to large data files, resulting in error messages that block user access even to subsets of the file content, preventing users from accessing any part of the file.
Innovation Solution
A computer system with an engine interposed between the user and the editor that communicates with the user to determine if they want to access a subset of the file, requests input for the subset size, and sends a message to the editor to produce the specified subset, utilizing either data retrieval or data recovery functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If the editor attempts to access a large data file, then the user would be able to access the complete file content, but the editor displays an error message blocking access entirely
Solution Approach 1:
The patent divides the large data file into smaller manageable subsets that the editor can process. Instead of attempting to load the entire large file at once, the system segments it into multiple smaller portions, each within the editor's capacity limits, allowing users to access subsets of the data without encountering the file size error.
Solution Approach 2:
The patent implements partial action by allowing users to access only the portion of the file they need rather than requiring access to the entire file. The system enables partial file loading where users can specify they want to access a subset of the data, and the editor will load only that portion, avoiding the need to load the complete large file.
2Loss of information
If the editor loads the complete file content, then the user can access all data, but the system consumes excessive memory resources
Solution Approach 1:
The patent extracts only the necessary data from the large file that the user actually needs to access. Instead of loading the complete file content into memory, the system identifies and extracts only the relevant subsets, leaving the rest of the data on storage. This extraction approach maintains data accessibility for needed portions while dramatically reducing memory consumption.
Solution Approach 2:
The system performs partial loading by loading only the necessary portion of the file into memory rather than the complete content. Users can access the data they need through the loaded subset, while the majority of the file remains on storage media, thus maintaining information accessibility for required data while minimizing memory resource consumption.
3Reliability
If the editor blocks access to large files, then system stability is maintained, but user productivity is reduced
Solution Approach 1:
The patent segments the large file access process into multiple manageable operations. Instead of a single blocking operation that fails for large files, the system divides access into multiple smaller operations on file subsets, each within stability limits. This segmentation maintains system stability while enabling continued user productivity through incremental data access.
Solution Approach 2:
The system enables partial file access that maintains stability by loading only manageable portions rather than blocking complete access. Users can achieve their productivity goals by accessing the necessary data subsets without overloading the system, thus maintaining both system stability and user productivity simultaneously.
Data Source
AI summary
An engine is interposed between a user and an editor. The engine is configured to receive messages from the editor denying user access to large data files. In response, the engine is configured to communicate a first message to the user asking whether the user desires to open a subset of the file contents using the editor. Upon receipt of an affirmative from the user, the engine is configured to communicate a second message to the user seeking input on a size of the file subset that is to be accessed. The engine then communicates to the editor, a third message specifying a size of the subset of data that is to be provided. In response to receiving the third message, the editor produces the requested subset of the stored data corresponding to the size indicated by the user.