Overview
Bureau Works utilizes Translation Memory (TM) Context to distinguish between standard matches and 101% matches (In-Context Exact matches). To provide more granular control over how these matches are calculated and applied, we have introduced three new settings at both the Account and Organizational Unit (OU) levels.
These features ensure that 101% matches are only awarded when specific context criteria—such as surrounding segments or metadata keys—are met, preventing "false" matches in ambiguous scenarios.
Access and Configuration
Account Level
To set these rules globally for your entire account, an Account Admin must navigate to:
Settings > Account Settings > Usage
Organizational Unit Level
To override account-wide defaults for a specific team or department, navigate to:
Organizational Unit > General > More Settings
Feature Breakdown
1. Require Context for 101% Matches
When this feature is enabled, a 101% match can only be achieved if at least one type of context is available for the segment.
Mechanism: The system checks for either a Previous/Next segment or a Context Key.
Impact (Enabled): If no context is present in the segment metadata or the surrounding document structure, the TM match will never be considered a 101% match, even if the text is identical.
Impact (Disabled): If disabled, all exact matches will be treated as 101% matches. The system will not take any type of context into consideration, relying solely on whether the TM record is identical to the source segment.
Default Status: Enabled.
2. Require Context for 101% Matches (Single Segment)
This rule specifically addresses files that contain only a single segment (e.g., a one-cell spreadsheet or a single UI string).
Mechanism: In a single-segment file, there is no "Previous" or "Next" segment to verify. If this setting is enabled, a 101% match is only possible if a Context Key is present.
Default Status: Disabled.
3. TM Context Priority
This setting allows you to define which type of context the system should prioritize when determining a match. You can choose from three configuration modes:
Mode | Description |
Context Key First | The system first checks if the segment has a Context Key. If a key exists and matches, it takes priority. If not, the system falls back to checking the Previous/Next segments. |
Prev/Next Segment Only | The system exclusively checks if the surrounding segments match. Any existing Context Keys are ignored for the purpose of the 101% calculation. |
No Priority | The system checks both Context Keys and Previous/Next segments with equal weight. If either condition matches, the segment is considered a 101% match. |
Note: If the selected priority mode cannot be satisfied (for example, if "Context Key First" is selected but the segment lacks a key), the system will fall back to the default context priority order to ensure the most accurate match is still identified.