Terminology Mapping
Goal
Normalize vocabulary across docs, code, and AI-generated answers so retrieval is stable even when users use slang, acronyms, or alternate product names.
Canonical Mapping Rules
- Use a canonical term in headings and first mention.
- Keep common aliases in body text for retrievability.
- Record deprecated names to support historical queries.
- Avoid mixing unrelated concepts under one shorthand term.
Synonym and Alias Map
| Canonical Term | Accepted Aliases | Notes |
|---|---|---|
| Salesforce | SF | Use “Salesforce” in docs; SF acceptable in conversation. |
| Lightning Web Components | LWC | Use both in first mention for search. |
| CRM Analytics | Tableau CRM, CRMA | Tableau CRM is older naming. |
| Salesforce DX | SFDX | Keep both forms in developer docs. |
| Org-Wide Defaults | OWD | Security docs should include both. |
| Field-Level Security | FLS | Security docs should include both. |
| Object-Level Security | OLS | Often paired with FLS and sharing. |
| Change Data Capture | CDC | Integration docs should include event durability caveats. |
| Platform Event | PE | Clarify vs CDC when both are present. |
| Named Credential | NC | Expand to full term in architecture docs. |
Deprecated and Historical Name Handling
- Include historical terms in glossary pages with “formerly” notes.
- Keep product rename lineage explicit (e.g., Tableau CRM -> CRM Analytics).
- Avoid using deprecated names as canonical headings.
Retrieval Guidance
- Query normalization should expand high-signal acronyms (
lwc,owd,fls,cdc,sfdx,crma). - Index-time and query-time normalization should stay in sync.
- Evaluations should include acronym-only and expanded-form queries.
Governance
- Update this file whenever a new acronym appears in 3+ docs.
- Add new term mappings during PR review, not post-merge cleanup.
- Keep mappings specific; avoid overly broad expansions that add noise.