Contextual search
Search distinguishes a legal term from a medical term, a historical title from a modern office, and a literal translation from accepted professional usage.
Platform
Context before translation.
Idanium is designed as a multilingual workspace where terms are not isolated entries, but connected decisions shaped by domain, source, audience, review history, and usage.
Translator workflows
Workflows support saved terminology, reviewer notes, preferred equivalents, quality checks, project-specific glossaries, and publication readiness.
Source trails
Every serious term benefits from provenance: examples, citations, source categories, dates, and notes about when a translation should not be used.
Workspace model
A shared place for translators, reviewers, and experts.
Idanium is not only a lookup page. It is a working environment where terminology decisions can be proposed, discussed, approved, reused, monitored, and improved over time.
Terminology managers
Create controlled glossaries, approve preferred equivalents, deprecate outdated terms, and maintain source evidence.
Translators
Search terms with domain context, reuse memory, see guardrails, and ask reviewers without leaving the translation record.
Domain experts
Review sensitive concepts, explain why a term is acceptable, and create rules for future projects.
Project owners
Track assignments, blockers, deadlines, approvals, publication readiness, and source-change impact.
Core objects
The platform stores more than translated words.
Each record can carry operational and linguistic context, so teams can understand why a decision is valid.
Term record
Preferred equivalent, forbidden alternatives, language, register, domain, source, examples, owner, and approval state.
Concept record
Definition, related concepts, broader and narrower terms, jurisdiction, period, audience, and review notes.
Memory segment
Source sentence, target sentence, document type, language pair, reviewer confidence, and freshness state.
Source record
Document, citation, URL, version, date, authority level, and change-monitoring status.
Guardrail
Rule that protects terminology, tone, audience level, compliance, or expert review requirements.
Workflow task
Assignment, due date, risk level, review stage, blocker, decision, and publication state.
Outputs
What teams can produce from the same knowledge base.
Because the system connects concepts, sources, and review history, the same knowledge can support multiple language products.
Specialist translations
Precise translations with source trails and domain-specific reviewer confidence.
Plain-language versions
Accessible explanations for residents, patients, students, service users, and non-specialists.
Glossaries and termbases
Exportable terminology resources with definitions, equivalents, status, and notes.
Quality reports
Lists of unresolved terms, guardrail violations, outdated memory, and source changes.