Consolidated Change Requests for Data Hierarchy Commit Review
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in managing and evaluating the cumulative effects of multiple change requests to a data hierarchy, leading to undesirable ripple effects, database rollbacks, and inefficient use of computing resources due to individual evaluation of changes.
Innovation Solution
A system that consolidates multiple change requests into a single consolidated request, allowing for holistic evaluation of cumulative effects before committing changes to the data hierarchy, including validation rules and data survivorship rules to handle collisions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple change requests are processed individually, then each request can be evaluated separately, but the cumulative effect of multiple requests is not detected leading to undesirable commits and increased rollbacks
Solution Approach 1:
The patent consolidates multiple individual change requests into a single consolidated change request object. This merging allows the system to evaluate the cumulative effect of all changes together before committing, preventing undesirable commits that would occur if changes were processed individually. The consolidated request maintains links to original requests and applies data survivorship rules to resolve collisions.
2Reliability
If change requests are consolidated into a single request, then cumulative effects can be evaluated before commitment, but the complexity of managing and processing the consolidated request increases
Solution Approach 1:
The consolidated change request object is segmented into distinct components including links to original requests, individual changes from each request, and an attachment file for tracking applied/rejected changes. This segmentation allows the system to manage complexity by organizing the consolidated request into manageable parts while still evaluating cumulative effects.
Solution Approach 2:
The consolidated change request acts as an intermediary object between individual change requests and the final commit operation. It mediates the evaluation process by holding all changes in a structured format, applying validation rules, and coordinating the commit or rollback action for all underlying requests together.
3Productivity
If individual change requests are committed without consolidation, then processing is simpler, but database rollbacks are more frequent consuming computing resources
Solution Approach 1:
The system performs preliminary evaluation of the cumulative effect of multiple change requests by consolidating them before commitment. This preliminary action allows validation rules to be applied to the combined changes, detecting potential conflicts or violations that would cause rollbacks, thereby preventing wasted computing resources on unsuccessful commits.
4Reliability
If multiple change requests are evaluated together, then cumulative effects are detected, but the time required to process and approve changes increases
Solution Approach 1:
The consolidated change request creates a copy of the underlying data from individual requests into a unified structure. This copying allows the system to evaluate cumulative effects on a copy before committing changes to the actual database, improving evaluation accuracy without significantly impacting processing time since the expensive operations are performed on the consolidated view rather than repeatedly on individual requests.
Data Source
AI summary
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.