Multilingual Metadata Structure for Locale-Aware Search

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional content management systems lack flexibility and intelligence in handling multilingual metadata, requiring separate fields for each language and often failing to recognize language context, leading to inefficient and inaccurate translation and search capabilities.

Innovation Solution

Implement a multilingual metadata feature that allows metadata to be represented in multiple languages, with locale metadata tables and localization code embedded in the system, enabling users to view metadata in their preferred language and supporting multilingual search capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate metadata fields are created for each language (e.g., name_english, name_french), then the system can store multilingual metadata, but the system complexity increases and the system loses the intelligence to recognize language context

Engineering Contradiction:
Improvemultilingual metadata supportVSAvoidmetadata field structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple language-specific metadata fields into a single unified metadata field that can store multilingual content. Instead of maintaining separate fields like name_english, name_french, etc., the system consolidates them into one field that intelligently handles multiple languages, reducing structural complexity while preserving multilingual capability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified metadata field is designed to serve multiple language functions simultaneously. A single field structure can store and retrieve metadata in different languages based on context, making the field universal rather than language-specific. This multi-functional design eliminates the need for language-duplicated field structures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If the system stores metadata in multiple languages with separate fields, then translation capability is provided, but the translation accuracy and language context recognition deteriorate

Engineering Contradiction:
Improvelanguage representationVSAvoidlanguage context recognition
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent introduces an intermediary language tag or locale identifier that acts as a mediator between the unified metadata field and the display layer. This intermediary carries language context information that enables accurate language recognition and appropriate translation, bridging the gap between stored multilingual data and user-specific language requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the parameter structure of the metadata field to include language identification parameters alongside the multilingual content. By embedding language context parameters within the field structure, the system gains the intelligence to recognize and differentiate between languages, improving translation accuracy without requiring separate fields for each language.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If translation is performed ahead of time or in real-time, then multilingual display is achieved, but the processing time and system resource consumption increase

Engineering Contradiction:
Improvemultilingual display capabilityVSAvoidtranslation processing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent applies preliminary action by storing metadata in a unified field with embedded language tags during the initial data entry phase. Instead of translating at display time, the language context is prepared and tagged in advance during data ingestion, allowing for rapid retrieval and display without real-time translation overhead.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The unified metadata field structure is designed to be self-service by automatically carrying language identification information with the content. When metadata is retrieved, the embedded language tags enable the system to automatically determine the appropriate language without requiring external translation services or real-time processing, reducing time and resource consumption.

Inventive Principle:
Principle #25Self-service

4Device complexity

If the system uses a unified metadata field for multiple languages, then the system complexity is reduced, but the ability to accurately distinguish and manage different language versions deteriorates

Engineering Contradiction:
Improvemetadata field structureVSAvoidlanguage distinction accuracy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements a nested structure where language identification tags are embedded within the unified metadata field. The unified field contains both the multilingual content and the language context information in a nested manner, allowing the system to maintain simplicity at the field level while preserving detailed language distinction capability through the nested language tags.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS12475101B2Systems and methods for multilingual metadata
Publication Date: 2025.11.18 OPEN TEXT SA ULC
  • US12475101B2 patent drawing
  • US12475101B2 patent drawing
  • US12475101B2 patent drawing

AI summary

A content management system provides a mechanism for representing a particular piece of metadata in multiple languages. The multilingual metadata system provides a user with an ability to visualize a single translation in a language of the user's preference or based on the user's locale. The system receives an indication that at least one metadata field associated with a managed object contains multilingual metadata. A locale metadata table and a new metadata table for the managed object are created using information from an original metadata table for the managed object. Two or more metadata field values representing at least two languages are received by the system. The metadata fields are tagged with locale information and stored in the locale metadata table in association with the at least one metadata field in the new metadata table.