Structured records
Capture definitions, notes, examples, source evidence, ownership, and review state.
Feature
Concept development
Move from raw terms to reviewed concepts with definitions, examples, relationships, and usage rules.
Build the idea before choosing the word.
Many translation mistakes begin when a term is treated as a standalone word. Concept development starts with the underlying idea: what it means, where it appears, which terms compete with it, and how it changes by domain or audience.
Idanium helps teams shape concepts collaboratively before assigning equivalents across languages, registers, reading levels, and document types.
Relationship mapping
Connect broader, narrower, related, deprecated, competing, and historical concepts.
Language separation
Keep the concept stable while terms vary by language, register, script, and audience.
Review maturity
Move concepts from candidate to reviewed, approved, deprecated, or disputed.
What this adds
Concepts become reusable building blocks.
When a concept is well modeled, many downstream tasks become easier: translation, simplification, search, QA, and training material.
Definition first
Document the meaning before deciding which word should be used in each language.
Evidence-backed
Attach examples, source citations, usage notes, and domain labels to support decisions.
Change-aware
Record when a concept changes, when a term is deprecated, and when older translations need review.
Connected records
A concept record can connect many kinds of knowledge.
The more context a concept carries, the less likely a team is to make a shallow word-for-word decision.
Terms and synonyms
Store preferred, allowed, forbidden, informal, historical, and region-specific labels.
Examples
Show real sentences, document fragments, and approved translations where the concept appears.
Relations
Link parent concepts, subtypes, near equivalents, false friends, and jurisdiction-specific variants.
Owners
Assign subject-matter reviewers and terminology owners for accountability.