Data Exchange System for Composite Attributes
Solution Overview
Problem
Existing data exchange systems face difficulties in flexible data exchange between databases with composite attributes due to differences in code systems, leading to obstacles in data exchange, especially when standard codes are not universally applicable.
Innovation Solution
A data exchange system that includes a base database, an item mapping unit, a code mapping unit, a standard data conversion unit, and a conversion unit, which separates composite attributes, maps them to standard data, and converts data between different databases using a base code system, enabling flexible and stable data exchange.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standard codes are used for data exchange between databases, then data compatibility is improved, but the system cannot handle composite attributes with different attribute combinations across databases
Solution Approach 1:
The patent segments composite attributes into individual attribute components (e.g., item attribute, standard attribute, and other attributes). Each attribute is mapped separately to standard codes, allowing the system to handle complex composite structures while maintaining compatibility with standard code systems. This segmentation enables flexible recombination of standardized attributes to match different database schemas.
Solution Approach 2:
The patent introduces an intermediary conversion system that acts as a mediator between databases with different composite attribute structures. This intermediary maps composite attributes from source databases to standard codes and then to target database structures, enabling data exchange without requiring direct compatibility between source and target databases.
2Adaptability or versatility
If composite attributes are managed with unique code systems in each database, then database-specific requirements are met, but data exchange between databases becomes difficult
Solution Approach 1:
The patent creates a universal conversion system that can handle multiple database-specific composite attribute structures through a single standardized interface. The system maintains multi-functionality by supporting various attribute combinations (item+standard, item+production area, etc.) while converting them all to a common standard code format for interoperable data exchange.
3Measurement precision
If individual conversion tables are created for each database pair, then accurate conversion is achieved, but the system complexity increases significantly
Solution Approach 1:
The patent merges multiple individual conversion tables into a single comprehensive conversion system based on standard codes. Instead of maintaining separate conversion tables for each database pair, the system uses a unified set of standard code mappings that can serve any conversion scenario, dramatically reducing system complexity while maintaining conversion accuracy.
4Ease of operation
If standard codes are applied to all databases, then data standardization is improved, but existing databases with composite attributes cannot be integrated
Solution Approach 1:
The patent performs preliminary mapping of composite attributes to standard codes during the data exchange process, rather than requiring pre-standardization of existing databases. This preliminary action allows existing databases to maintain their original composite attribute structures while enabling standardization during conversion, facilitating integration without disrupting existing systems.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
Provided are a data exchange system, a data exchange method, and a data exchange program capable of realizing flexible information exchange by reliably and stably realizing data exchange between databases having code systems including composite attributes. A data exchange system 1 includes a base database 12; an item mapping unit 14 for associating an input-side external attribute item with an attribute item corresponding to the input-side external attribute item and associating an output-side external attribute item with an attribute item corresponding to the output-side external attribute item; a code mapping unit 16 for associating input-side external attribute data with base codes identified by attribute items and associating output-side external attribute data with base codes identified by attribute items; a standard data conversion unit 18 for converting input-side external data into standard data; and a conversion unit 20 for converting the input-side external data into output data for an output-side external database.