18072581. CONSOLIDATING CHANGE REQUESTS IN DATA HIERARCHIES simplified abstract (Oracle International Corporation)
Contents
- 1 CONSOLIDATING CHANGE REQUESTS IN DATA HIERARCHIES
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 CONSOLIDATING CHANGE REQUESTS IN DATA HIERARCHIES - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
CONSOLIDATING CHANGE REQUESTS IN DATA HIERARCHIES
Organization Name
Oracle International Corporation
Inventor(s)
Anurag Garg of Cupertino CA (US)
Douglas Cosby of Austin TX (US)
CONSOLIDATING CHANGE REQUESTS IN DATA HIERARCHIES - A simplified explanation of the abstract
This abstract first appeared for US patent application 18072581 titled 'CONSOLIDATING CHANGE REQUESTS IN DATA HIERARCHIES
Simplified Explanation
A data hierarchy with consolidated change requests
- Data hierarchy with individual data nodes
- Consolidation of change requests into a single request
- Display of consolidated request showing cumulative effect of changes
- Maintenance of links and updates to underlying data objects
- Record of actions related to the consolidated request
Potential Applications
The technology could be applied in various industries such as data management, software development, and project management.
Problems Solved
1. Streamlining the process of managing change requests in a data hierarchy 2. Providing a comprehensive view of the cumulative effect of multiple change requests
Benefits
1. Increased efficiency in handling change requests 2. Improved decision-making based on a consolidated view of changes 3. Enhanced record-keeping and traceability of actions
Potential Commercial Applications
Optimizing data management systems for businesses
Possible Prior Art
One possible prior art could be the use of version control systems in software development to track changes and maintain a history of modifications.
Unanswered Questions
How does the interface handle conflicting change requests?
The abstract does not specify how conflicting change requests are resolved within the consolidated request.
What security measures are in place to protect the integrity of the data hierarchy?
The abstract does not mention any security features or protocols implemented to safeguard the data hierarchy from unauthorized access or tampering.
Original Abstract Submitted
A data hierarchy including individual data nodes may be used to represent a wide variety of data collections. Requests to change or add nodes in the data hierarchy may be received from many different sources over time. Instead of considering these change requests individually, an interface allows a plurality of change requests to be consolidated together into a single consolidated request. The consolidated request may be displayed in an interface such that changes from each of the original requests may be displayed together in an interface so that a cumulative effect of each of the change requests may be considered before the data changes are committed to the underlying data structure. The consolidated request may maintain links and update underlying data objects representing each of the original requests to provide a record of actions related to the consolidated request.
