Terminology
The Terminology Explorer is the Concepts view of the Brand hub: concept-oriented term management for maintaining consistent vocabulary across locales. Each concept represents a single meaning with terms in multiple languages, lifecycle statuses, and domain classification.
Terminology and content memory are kept on the server, shared across every project — one governed source of the team's approved wording.
A concept is more than its terms. In the Brand hub each concept also carries typed relations to other concepts (what replaced it, what to use instead, which competitor it stands against), per-market validity, observations, comments, and a story of how it came to be. This page covers the everyday term-management surface; see Brand for the richer concept model with relations and governance around it.
The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.
Accessing the Terminology Explorer
There are two ways to open the Terminology Explorer:
- From a project — click the Terminology button in the project view header. This opens the explorer with the project name displayed and source/target locales available for filtering.
- From the sidebar — click Brand in the main sidebar, then Concepts, to reach the workspace-scoped explorer.
Browsing Concepts
The explorer displays concepts in a paginated table with these columns:
| Column | Description |
|---|---|
| Source Term | The term in the source language |
| Target Term | The translated term |
| Domain | Subject area classification (e.g., "legal", "medical", "UI") |
| Status | Lifecycle status badge |
| Updated | Date the concept was last modified |
Clicking a concept opens its dashboard — the per-concept page that gathers its terms, geography, constraints, direct relations, and timeline. The concept count badge in the header shows the total number of concepts matching current filters.
Term Lifecycle Statuses
Each term carries a lifecycle status that communicates its approval level:
| Status | Meaning |
|---|---|
| Preferred | The recommended term — translators should use this |
| Approved | Accepted for use |
| Admitted | Acceptable but not preferred |
| Deprecated | Was once approved but should no longer be used |
| Proposed | Under review, not yet approved |
| Forbidden | Must not be used in translations |
Searching
Type in the search box to filter concepts by source or target term text. The search uses debounced input (300ms delay) and results update automatically.
Filtering
Use the filter controls to narrow the concept list:
- Source locale filter — show only concepts with a term in the specified source language
- Target locale filter — show only concepts with a term in the specified target language
- Status filter — show only concepts with a specific lifecycle status
Filters can be combined with text search. Changing a filter resets to page 1.
Adding concepts
Click Add Concept in the header to create a concept — the unit of meaning
that terms attach to. A new concept starts with a first term and a proposed
status. To round it out — terms in other languages, a domain, relations, and
per-market constraints — open its dashboard and edit
it there.
Editing concepts
Clicking a concept opens its dashboard: the per-concept page that gathers its terms, geography, constraints, a local relations widget, and a timeline. Terms and their metadata are edited on the dashboard rather than inline in the table.
How an edit applies depends on whether it is governed:
- Ordinary edits — adding or correcting a translation, adjusting a domain, or moving a term to a non-governed status — apply directly.
- Governed edits — setting or clearing a term's
forbiddenorpreferredstatus, recording areplaced_byrelation, or deleting a concept — are bundled into a reviewable change-set whose blast radius is measured before anyone approves it.
Deleting concepts
Deleting a concept is a governed action. From the concept dashboard, the delete is added to a change-set and removes the concept only once that change-set is approved and merged, so a concept other content still references cannot disappear unreviewed.
Import and Export
Import from CSV
Click Import CSV and select a CSV file. The expected format:
source_term,target_term,source_locale,target_locale,domain,status
login,connexion,en,fr,UI,approved
password,mot de passe,en,fr,UI,preferred
Import from JSON
Click Import JSON and select a JSON file containing an array of concept objects:
[
{
"source_term": "login",
"target_term": "connexion",
"source_locale": "en",
"target_locale": "fr",
"domain": "UI",
"status": "approved"
}
]
Export to JSON
Click Export JSON to download the whole terms store as a JSON file. This is useful for backup, sharing with other workspaces, or importing into external tools.
Pagination
When there are more than 50 concepts, pagination controls appear below the table:
- Previous / Next buttons to navigate pages
- Page X of Y indicator showing current position
Terminology in the Translation Editor
Terminology is also used within the translation editor:
- Context panel — shows per-block term matches with source terms, target suggestions, status badges, and domain labels
- Term enforcement — validates that target translations use the correct terminology
When a block is selected in the editor, the context panel automatically looks up matching terms and displays them alongside memory matches.
See Translation Editor for details on the context panel.
Concept Model
The terminology system is concept-oriented, inspired by the TBX (TermBase eXchange) standard:
- A concept represents a single meaning or notion
- Each concept has terms in one or more languages
- Terms have metadata: lifecycle status, domain, and notes
- Concepts are scoped to the workspace and shared across all projects
The framework owns this concept and term model; for its architecture, see the framework terminology reference.
On the platform, the same concepts are the nodes of the Brand knowledge graph — with typed relations, per-market validity, observations, comments, and governed change-sets layered on top. When you are ready to model how concepts relate rather than just curate terms, start at Brand.