Centralized Label Database for Multi-Language Software
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business solution software systems face challenges in efficiently reusing labels across modules due to proprietary resource files, leading to increased development costs and complexity, especially when handling multiple languages and vendors, as they do not utilize generic resource files or database metadata stores effectively.
Innovation Solution
Implementing a common resource file system where each module accesses a shared label database with unique identifiers, allowing for efficient language management and label reuse through a label dialog tool that searches and duplicates existing label texts, reducing the need for redundant translations and development efforts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If proprietary resource files are used for labels in each module, then each module can maintain its own labels independently, but the development cost and complexity increase due to inability to reuse labels across modules
Solution Approach 1:
The patent merges label management from multiple proprietary module-specific resource files into a single centralized database. This allows labels to be stored once and reused across multiple modules, eliminating redundant label definitions and reducing development complexity while maintaining the ability for each module to access and use labels as needed.
Solution Approach 2:
The centralized label database serves as a universal resource that can be accessed by any module in the system. Instead of each module having its own dedicated label resource file, the single database provides label services to all modules, enabling label reuse across different contexts and reducing overall system complexity.
2Adaptability or versatility
If each module has its own resource file with labels, then module independence is maintained, but translation costs increase when multi-language support is needed
Solution Approach 1:
The patent combines all label translations from multiple modules into a single centralized database. Instead of each module maintaining separate translation resources, the unified database stores all label texts and their translations in one place, allowing translations to be created once and reused across all modules, thereby reducing translation costs.
3Ease of manufacture
If labels are stored in separate resource files per module, then module-specific label customization is possible, but the time to develop and maintain labels increases
Solution Approach 1:
The patent merges label development into a centralized process where labels are created and maintained in a single database rather than in separate resource files for each module. This allows developers to create labels once and have them automatically available to all modules that need them, significantly reducing the time required for label development and maintenance.
4Adaptability or versatility
If proprietary resource files are used, then module-specific label properties are preserved, but label search and reuse functionality is unavailable
Solution Approach 1:
The patent introduces a centralized label database as an intermediary between modules and label resources. This database provides search functionality and label reuse capabilities while maintaining the label properties needed by each module. The database acts as a mediator that allows modules to access and reuse labels without directly managing resource files.
Data Source
AI summary
A method stores and uses labels in a business solution software program having multiple languages. Instead of having a single resource file for each language, the information related to the labels is stored in a database. Each label is assigned its own unique identifier in a label ID structure, that also contains information related to how the label is used in the system. The text for the label is stored in a separate label text structure. The label text structure contains the text of the label in all of the available languages. When a new label is written the developer can search the current labels to find a label that matches the intended use. If a match is found for the desired text the label is duplicated to the new label. If no match is found a new label must be generated.