Hierarchical Data Retrieval Using Dual Date Fields
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for managing and retrieving data in hierarchical structures fail to distinguish between the date of data creation and the date of data usage, limiting the ability to retrieve data based on both viewpoints effectively.
Innovation Solution
A system that includes input, storage, and retrieval mechanisms for hierarchical structure data, which stores and updates data with separate fields for 'efficient date' and 'data change date', allowing retrieval based on these specific dates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data is managed based on a single date (date when data is used), then the management system is simple, but it is impossible to distinguish between data creation date and data usage date, limiting retrieval flexibility
Solution Approach 1:
The patent segments the single date field into two distinct date fields: one for recording when data is created/changed and another for recording when data is used. This segmentation allows independent tracking of both temporal aspects, enabling flexible retrieval based on either date type while maintaining clear data provenance.
2Adaptability or versatility
If separate fields for efficient date and data change date are added, then retrieval flexibility is improved, but data structure complexity increases
Solution Approach 1:
The patent designs the data structure with universal date fields that serve multiple functions: tracking data creation, modification, and usage timelines. These multi-functional date fields reduce the need for multiple specialized fields, achieving retrieval flexibility without proportionally increasing structural complexity.
Solution Approach 2:
The patent changes the parameter structure by introducing distinct date parameters (data change date and efficient date) with specific semantic meanings. This parameter differentiation enables precise retrieval operations while maintaining a relatively simple data structure through clear parameter definition and usage rules.
3Quantity of substance
If only one date field is used, then data storage is simple, but the ability to compare and analyze data changes over time is limited
Solution Approach 1:
The patent adds a temporal dimension to data storage by introducing separate date fields for different temporal aspects (creation/change date and usage date). This dimensional expansion preserves comprehensive temporal information while maintaining straightforward data storage through structured field organization.
Data Source
AI summary
A data retrieving apparatus having: an input apparatus for inputting the hierarchical structure data showing the hierarchical structure and operation instruction data; a data storing apparatus for storing the inputted hierarchical structure data; a retrieving apparatus for retrieving data which satisfies conditions from the hierarchical structure data stored in the data storing apparatus on the basis of the operation instruction data which is inputted by the input apparatus; and an output apparatus for outputting the retrieved data. Each data which is stored in the data storing apparatus has items regarding an efficient date and items regarding a data change date. The retrieving apparatus has an apparatus for retrieving the data on the basis of the efficient date and the data change date.