DashboardProductBook Demo

Business Glossary

Review and approve semantic matches between business terms and physical data

The Business Glossary is where AI-suggested matches between Logical Data Elements (business terms) and Physical Data Elements (database columns) are reviewed. Approve or reject each match to build your verified glossary.

Semantic MatchingHuman ApprovalConflict DetectionMatch Scoring
Try in DashboardGlobal Glossary
216LDEs
67matched
23pending

Business Glossary

Pending review

23 pending

Customer ID

lde-001

Unique identifier assigned to each customer in the system

CRM Systemcustomers3 matches
Physical Matches:
CUST_ID(94%)customer_identifier(87%)cid(72%)

Physical Implementations

CUST_IDPerfect Match
94%
CRM Systemcustomers
customer_identifiersemantic
87%
CRM Systemcustomers
cidfuzzy
72%
CRM Systemcustomers

Account Balance

lde-002

Current monetary balance of the account

ERP Platformaccounts2 matches
Physical Matches:
ACCT_BAL(91%)balance_amount(85%)

Transaction Date

lde-003

Date when the transaction was processed

Payment Gatewaytransactions2 matches
Physical Matches:
TXN_DATE(96%)trans_dt(78%)
Human in the Loop
The Process

How Semantic Matching Works

IDA uses sentence transformer models to find potential matches between business terms and database columns

1

Extract

LDEs and PDEs extracted from documents to inventories

2

Embed

Sentence transformers generate semantic embeddings

3

Match

AI finds top 3 candidate matches per LDE with confidence scores

4

Approve

Humans review and approve or reject each suggestion

Match Quality

Match Types & Scoring

IDA detects different types of matches based on how the terms relate to each other. Perfect matches occur when definitions are semantically identical.

Perfect Match (95%+)

Definition contains exact business term

Semantic Match (85-94%)

High semantic similarity between terms

Fuzzy Match (70-84%)

Partial similarity, needs human review

Conflict Detection

When a Physical Data Element is matched to multiple Logical Data Elements, IDA detects the conflict and prompts you to resolve it.

Conflict Detected

Physical element CUST_ID is already mapped to Customer Identifier. Approving this will decline the conflicting mapping.

Interface Features

Powerful Review Tools

Search & Filter

Find terms by name, definition, system, or match status

Group By

Organize terms by system, table, or flat list

Bulk Actions

Approve or reject multiple matches at once

Conflict Alerts

Automatic detection of conflicting mappings

Audit Trail

Full history of who approved what and when

Re-process

Re-run matching after adding new documents

Ready to build your verified glossary?

Start reviewing AI-suggested matches and build your single source of truth for business terms.

Open Dashboard