Metadata Element Name Segmentation and Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in maintaining metadata consistency and context when metadata elements are renamed, imported, or used across different systems with varying naming conventions and restrictions.
Innovation Solution
The proposed solution involves creating an association between a metadata element and its original name, even if the element is renamed, allowing for the retention of original names across different systems and formats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If metadata elements are renamed to adapt to different system naming conventions and restrictions, then adaptability to different systems is improved, but loss of original name information occurs
Solution Approach 1:
The metadata element name is segmented into two separate components: the current name used by the system and the original name from the source system. This segmentation allows each name to serve its specific purpose independently, resolving the contradiction between adapting to system constraints and preserving original information.
Solution Approach 2:
An intermediary mapping relationship is introduced between the current name and the original name. This mapping structure acts as a mediator that enables systems to use their own naming conventions while maintaining the ability to reference and understand the original metadata element names from source systems.
2Ease of operation
If metadata is imported and renamed to fit local system constraints, then ease of operation in the target system is improved, but traceability to the source metadata is reduced
Solution Approach 1:
The name information is segmented into current operational name and original source name, allowing the target system to operate with its own naming conventions while maintaining a separate record of the original name for traceability purposes.
Solution Approach 2:
The mapping between current names and original names provides a feedback mechanism that enables traceability. By maintaining this mapping relationship, the system can trace back from the renamed metadata element to its source, ensuring reliability and auditability while preserving ease of operation.
3Adaptability or versatility
If different naming conventions are used across systems, then adaptability to various formats is improved, but consistency of metadata identification is worsened
Solution Approach 1:
Metadata identification is segmented into two layers: the current name layer that adapts to different system formats and conventions, and the original name layer that provides consistent identification across all systems. This segmentation allows each layer to fulfill its specific function without compromising the other.
Solution Approach 2:
A mapping relationship serves as an intermediary between different naming conventions. This intermediary structure enables systems to use their preferred formats and conventions while maintaining consistent identification through the original name, resolving the contradiction between adaptability and consistency.
Data Source
AI summary
Techniques and solutions are described for retaining names for metadata elements, such as when metadata is imported, converted to a different format, or used with a system that may have restrictions on naming different than a system on which the metadata is created. Metadata includes a plurality of metadata elements, including a first metadata element associated with a first name. A second name is received for the first metadata element. The second name is assigned to the first metadata element. An association is created between the renamed first metadata element and the first name.