Consolidating Metadata Changes in Base Repositories
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing patching processes for metadata in base repositories are inefficient, time-consuming, and costly, often resulting in loss of information due to conflicts and the need for repeated customer-specific customizations with each new version of the factory-packaged metadata repository.
Innovation Solution
A method for customizing, consolidating, and transforming metadata changes into a consolidated customization file, which is then applied to a new version of the base repository, ensuring compatibility and preserving customer-specific customizations by updating names, unique IDs, and removing references to deleted content.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If pre-defined conflict resolution rules are used to resolve metadata patching issues, then patching can be automated, but information loss occurs and customizations may be incorrect
Solution Approach 1:
The system performs preliminary actions by capturing and storing customization information in a consolidation file before patching occurs. This allows the customizations to be preserved and reapplied after the base repository is updated, preventing information loss while maintaining automation.
Solution Approach 2:
A consolidation file acts as an intermediary between the customizations and the base repository. It stores the customization information in a structured format that can be transported and applied independently from the base repository updates, preventing direct conflict and information loss.
2Manufacturing precision
If manual customization is performed on each new version of the base repository, then customization accuracy is maintained, but time and cost increase significantly
Solution Approach 1:
The system creates a copy of the customization information in a consolidation file that can be transported and applied to new base repository versions. This copying mechanism preserves the exact customization details without requiring manual re-entry, maintaining accuracy while reducing time and effort.
Solution Approach 2:
Customization information is captured and stored in advance in a consolidation file, so when a new base repository version is received, the customizations can be automatically reapplied without manual intervention, significantly reducing patching time while maintaining accuracy.
3Adaptability or versatility
If repeated customizations are applied to each new base repository version, then customer needs are met, but productivity decreases due to repetitive work
Solution Approach 1:
The consolidation file serves as an intermediary that stores customer customization capabilities in a portable, structured format. This allows customizations to be automatically transferred and applied to new base repository versions, maintaining customer adaptability while eliminating repetitive manual work and improving productivity.
Solution Approach 2:
The system enables self-service by automatically capturing, storing, and reapplying customization information through the consolidation file mechanism. This eliminates the need for manual repetitive customization work while preserving customer-specific adaptations, significantly improving productivity.
4Reliability
If corrections are made to metadata after patching, then conflicts are resolved, but information loss occurs and additional time is required
Solution Approach 1:
The system performs preliminary capture and storage of customization information in a consolidation file before patching operations. This ensures that even if corrections are needed during patching, the original customization data is preserved and can be reapplied, preventing information loss while maintaining metadata consistency.
Solution Approach 2:
The consolidation file acts as an intermediary backup that preserves customization information independent of the base repository state. This allows corrections to be made during patching without risking permanent loss of customization data, as it can be recovered from the consolidation file and reapplied to ensure reliability.
Data Source
AI summary
Techniques for patching metadata content in a base repository are disclosed. Techniques can include customizing, by a computer including a processor and a memory, metadata content in an existing base repository, consolidating the metadata content customized in the existing base repository into a consolidated customization file, obtaining a new version of a base repository, transforming the metadata content in the consolidated customization file in accordance with the new version of the base repository and applying the transformed metadata content to the new version of the base repository. Transformation can be performed in response to metadata content being renamed, recreated and deleted.