Immutable Record Change Management via Standalone Objects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data storage systems face challenges in maintaining data immutability while allowing for changes and deletions as required by regulatory compliance, as existing methods either break the chain of assurance or complicate storage efficiency and integrity.
Innovation Solution
A method that captures changes to record objects as standalone objects with metadata, applies these changes upon retrieval or restore, and modifies previous versions' metadata to include pointers to change objects, ensuring immutability and regulatory compliance without compromising data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored in an immutable manner to ensure regulatory compliance, then data integrity and reliability are improved, but the ability to make changes or corrections to the data is lost
Solution Approach 1:
The system segments data storage into immutable original records and separate change objects. Each change is stored as an independent object that references the original record through metadata pointers, allowing the original data to remain immutable while enabling changes through the application of change objects during retrieval.
Solution Approach 2:
Change objects serve as intermediaries between the immutable original records and the need for data modifications. These change objects contain instructions and metadata that reference original records without directly modifying them, acting as a mediator that preserves immutability while enabling change management.
2Adaptability or versatility
If changes are made directly to stored records, then data adaptability is improved, but the immutability assurance and chain of custody are broken
Solution Approach 1:
The system performs preliminary action by capturing and storing change requests as change objects before they are applied to the original records. The change objects are created and validated in advance, containing all necessary instructions and metadata, so that when changes are applied during retrieval, the immutability of the original records is preserved while the changes are still effected.
Solution Approach 2:
Instead of modifying the original immutable records, the system creates change objects that are copies containing the modification instructions. These change objects reference the original records through metadata pointers, allowing changes to be applied by combining the original record with its associated change objects during retrieval, thus preserving the original while enabling modification.
3Loss of information
If standalone change objects are created for each modification, then data traceability is improved, but storage complexity and device complexity increase
Solution Approach 1:
The system merges the original record and its associated change objects during retrieval operations. The metadata pointers in the change objects link to the original record, and the change application process combines them to produce the final data set, reducing the apparent complexity by merging operations rather than maintaining separate complex structures.
Solution Approach 2:
The change object structure serves multiple functions: it stores modification instructions, maintains references to original records through metadata pointers, provides audit trails, and enables change application during retrieval. This multi-functionality reduces the need for separate systems for each function, thereby reducing overall complexity despite the detailed traceability provided.
Data Source
AI summary
Aspects of the present invention disclose a method, computer program product, and system for recording changes to records whilst preserving record availability. The method includes one or more processors capturing a change to a record object. The changes include details of the record object to be changed and a change method instruction by which the object is to be changed. The method further includes one or more processors storing a change object as a standalone object and storing the change method instruction and metadata pointing to the record object. The method further includes one or more processors modifying metadata of previous versions of the record object to include a pointer to the change object. The method further includes one or more processors applying the change method instruction to the record object when responding to a retrieve or restore request for the record object.