Skip to content
Data Literacy: Dimensions, Measures, and Information Marts

31 May 2026

Data Literacy: Dimensions, Measures, and Information Marts

Key data literacy concepts every data professional should know — dimensions vs measures, information marts, and data modeling vocabulary.

Data
Data Literacy BI Data Modeling

Data literacy is the ability to read, understand, and communicate with data. These are the fundamental concepts.

Dimensions vs Measures

The most important distinction in data analytics:

ConceptWhat It IsExamples
DimensionDescriptive attribute (the “by what”)Date, Region, Product, Category
MeasureQuantitative value (the “what”)Revenue, Quantity, Count, Average
-- "Total revenue BY region BY year"
--   measure          dimensions
SELECT
    region,           -- dimension
    year,             -- dimension
    SUM(revenue)      -- measure
FROM sales
GROUP BY region, year;

Types of Dimensions

TypeDescriptionExample
DescriptiveStatic attributesProduct name, color
TimeDate/time periodsYear, quarter, month, day
GeographicLocation-basedCountry, region, city
HierarchicalNested levelsCountry → Region → City
Slowly Changing (SCD)Changes over timeCustomer address history

Types of Measures

TypeDescriptionExample
AdditiveCan be summed across all dimensionsRevenue, quantity
Semi-additiveCan be summed across some dimensionsAccount balance (sum across accounts, not time)
Non-additiveCannot be summedRatios, percentages, averages

Information Marts (Data Marts)

A data mart is a subset of a data warehouse focused on a specific business area.

Data Warehouse
├── Marketing Data Mart    ← campaign metrics, conversions
├── Finance Data Mart      ← revenue, costs, budgets
├── Sales Data Mart        ← orders, pipeline, quotas
└── HR Data Mart           ← headcount, turnover, hiring

Benefits:

  • Faster queries (smaller dataset)
  • Tailored to department needs
  • Easier access control
  • Simplified data models

Key Data Concepts

Grain

The level of detail in a fact table. Defined by the question: “What does one row represent?”

GrainExample
TransactionOne sale
DailyTotal sales per day per store
MonthlyMonthly revenue per product

Rule: Define the grain first, then build the table.

ETL vs ELT

ETL: Extract → Transform → Load
     (source)   (staging)   (warehouse)

ELT: Extract → Load → Transform
     (source)   (lake)  (in the warehouse)
ApproachWhen to Use
ETLTransform before loading (traditional)
ELTLoad raw data, transform in warehouse (modern, cloud)

Slowly Changing Dimensions (SCD)

How to handle dimension changes over time:

TypeStrategyExample
SCD 1OverwriteUpdate current address (lose history)
SCD 2Add new rowNew row with start/end dates (keep history)
SCD 3Add columncurrent_address + previous_address

Data Quality Dimensions

DimensionQuestion
AccuracyIs the data correct?
CompletenessIs all data present?
ConsistencyDoes the same data agree across systems?
TimelinessIs the data fresh enough?
UniquenessAre there duplicates?
ValidityDoes the data match expected formats?

KPIs and Metrics

TermMeaning
MetricA quantifiable measure (page views, revenue)
KPIA metric tied to a business goal (conversion rate > 3%)
Leading indicatorPredicts future (website traffic)
Lagging indicatorConfirms past (quarterly revenue)

Summary

ConceptKey Idea
DimensionThe “by what” — categories for grouping
MeasureThe “what” — numbers to aggregate
Data MartSubset of warehouse for one department
GrainLevel of detail (what does one row mean)
SCDHow to handle changes over time
ETL/ELTPipeline for moving and transforming data