Data Object Freezing via Entity Relationship Registry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for freezing data in enterprise systems, such as archiving and flagging, are inefficient and prevent data reuse, as they either take too long or make data inaccessible, and are computationally costly.
Innovation Solution
A method that determines the frozen status of data objects based on relationships between entities in a registry, using path information and timestamps to assess whether data objects are frozen, allowing for real-time determination and maintenance of frozen status without archiving or flagging.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is archived after sign-off, then data is frozen and compliance is maintained, but data access time increases and system becomes inaccessible
Solution Approach 1:
The patent segments the data freeze mechanism by introducing version control. Instead of freezing all data globally, it creates separate versions (current version and archived version). The current version remains accessible for operations while archived versions are frozen for compliance. This segmentation allows simultaneous data access and freeze compliance without mutual interference.
Solution Approach 2:
The patent implements preliminary action by creating and freezing archived versions of data before they are needed for historical reference or compliance auditing. This allows the system to prepare frozen data copies in advance, so when compliance checks occur, the data is already in its frozen state without requiring real-time archiving operations that would block access.
2Reliability
If data is archived, then data is frozen, but data processing intensity and time consumption increase
Solution Approach 1:
The patent uses copying to create archived versions of data objects. Instead of moving or duplicating large amounts of data through complex archiving processes, it creates reference copies with version identifiers. The system maintains pointers to these versions rather than physically managing archived data, dramatically reducing processing intensity while maintaining freeze compliance.
Solution Approach 2:
The system performs preliminary version creation and freezing operations when data objects are first created or modified. By establishing the versioning structure and freezing archived versions at these preliminary stages, the system avoids heavy processing during compliance checks or data access operations.
3Reliability
If data is flagged as frozen, then data freeze is implemented, but computational efficiency decreases and data reuse becomes difficult
Solution Approach 1:
The patent segments the freeze status management by applying it selectively to archived versions rather than all data objects. Each version of a data object carries its own freeze status independently. This segmentation allows the system to maintain simple, fast checks for current versions while enforcing freeze compliance only on archived versions, reducing overall computational overhead.
Solution Approach 2:
The patent introduces version identifiers as intermediaries between data objects and freeze status. Instead of directly flagging data objects as frozen, the system uses version metadata to indicate freeze status. This intermediary layer simplifies the freeze mechanism to a metadata check rather than complex computational validation, improving efficiency while maintaining reliability.
4Reliability
If data is archived or flagged, then data is frozen, but data reuse for other purposes is prevented
Solution Approach 1:
The patent segments data into multiple versions, where archived versions are frozen for compliance and current versions remain accessible for reuse. This segmentation enables different versions to serve different purposes simultaneously - frozen archived versions for auditing and current versions for operational reuse - thereby maintaining both compliance and adaptability.
Solution Approach 2:
The patent implements a version lifecycle where archived versions are 'discarded' from active use but 'recovered' for compliance purposes. The system maintains archived versions in a frozen state that prevents operational changes while allowing historical analysis and auditing. This enables data reuse in appropriate contexts without compromising freeze compliance.
Data Source
AI summary
In one embodiment the present invention includes a computer-implemented for determining whether or not a data object is frozen. The method comprises accessing, by a user on a computer, a first data object of a plurality of data objects in one or more computer software applications. The plurality of data objects are assigned to a plurality of entities, where each entity specifies a category, and each of the plurality of data objects belong to a specific entity. The method determines if the first data object is frozen based on a relationship between the first entity and a second entity.