Data Hierarchy Copying with Dependency Mapping and New Object IDs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in efficiently copying data, particularly hierarchies of data objects with object dependencies, across different computer systems, leading to potential version conflicts.
Innovation Solution
A method involving the creation of a dependencies map to iteratively copy data hierarchies, assigning new object IDs, and sorting dependencies to ensure accurate recreation of data hierarchies across systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data hierarchies with object dependencies are copied between systems, then data sharing capability is improved, but version conflicts and copying accuracy deteriorate
Solution Approach 1:
The system performs preliminary actions by creating a dependencies map before copying data hierarchies. This map identifies all object dependencies and their relationships in advance, allowing the system to plan the copying sequence and avoid version conflicts during the actual copy operation.
Solution Approach 2:
The copying process is segmented into distinct phases: first creating a dependencies map to identify relationships, then copying objects in the correct sequence based on that map. This segmentation allows complex data hierarchies to be copied systematically rather than as a single undifferentiated operation.
2Reliability
If object dependencies are maintained during copying, then data integrity is improved, but copying complexity and time increase
Solution Approach 1:
A dependencies map serves as an intermediary data structure between the source and target systems. This map captures all object relationships and serves as a blueprint for the copying process, simplifying the complexity by providing a clear intermediate representation of dependencies rather than directly managing complex object relationships during copying.
Solution Approach 2:
The system changes the state of objects by assigning new unique identifiers to copied objects while maintaining their dependency relationships. This parameter change (object ID transformation) allows data integrity to be maintained through the dependencies map while enabling the copied objects to exist independently in the target system.
3Adaptability or versatility
If multiple copies of data hierarchies are created, then data sharing flexibility is improved, but version control and conflict management worsen
Solution Approach 1:
The system creates true copies of data hierarchies by generating new unique object identifiers for each copied object. Each copy is independent and can be modified without affecting other copies or the original, eliminating version conflicts while maintaining data sharing flexibility.
Solution Approach 2:
By creating a dependencies map before copying, the system preliminarily identifies all relationships that need to be preserved. This preliminary action ensures that when multiple copies are created, each copy maintains its integrity and relationships without creating version control issues.
Data Source
AI summary
Embodiments of the present disclosure include techniques for copying data between computer systems. In one embodiment, a content management system stores a hierarchy of objects. A backend server may receive information about the hierarchy of objects. A dependencies may be generated to define links between the objects in the hierarchy. A copy of the hierarchy of objects may be created on a backend system. In some embodiments, the copy may have a unique set of object IDs.