CSEP 546

Data Mining
Instructor: Pedro Domingos

Todays Program

Logistics and introduction

Data warehousing and OLAP

Logistics

Instructor: Pedro Domingos

Email: pedrod@cs
Office: CSE 648
Office hours: Tuesdays 5:30-6:20
TA: Parag
Email: parag@cs
Office: TBA
Office hours: Tuesdays 5:30-6:20
Web: www.cs.washington.edu/p546
Mailing list: csep546@cs
3

Assignments

Two projects
Individual
First project: Clickstream mining (20%)
Second project: Text classification
(20%)
Three homeworks
Individual
20% each
4

Source Materials

Jiawei Han & Micheline Kamber, Data

Mining: Concepts and Techniques, Morgan
Kaufmann, 2001.
Tom Mitchell, Machine Learning, McGrawHill, 1997.
Papers

What is Data Mining?

Data mining is the process of identifying

valid, novel, useful and understandable
patterns in data.
Also known as KDD (Knowledge
Discovery in Databases).
Were drowning in information, but
starving for knowledge. (John Naisbett)

Related Disciplines

Machine learning
Databases
Statistics
Information retrieval
Visualization
High-performance computing
Etc.

Applications of Data Mining

E-commerce
Marketing and retail
Finance
Telecoms
Drug design
Process control
Space and earth sensing
Etc.
8

The Data Mining Process

Understanding domain, prior knowledge,

and goals
Data integration and selection
Data cleaning and pre-processing
Modeling and searching for patterns
Interpreting results
Consolidating and deploying discovered
knowledge
Loop
9

Data Mining Tasks

Classification
Regression
Probability estimation
Clustering
Association detection
Summarization
Trend and deviation detection
Etc.
10

Inductive Learning

Inductive learning or Prediction:

Given examples of a function (X, F(X))
Predict function F(X) for new
examples X
Discrete F(X): Classification
Continuous F(X): Regression
F(X) = Probability(X): Probability
estimation
11

Widely-used Approaches

Decision trees
Rule induction
Bayesian learning
Neural networks
Genetic algorithms
Instance-based learning
Etc.

12

Requirements for a Data Mining

System

Data mining systems should be

Computationally sound
Statistically sound
Ergonomically sound

13

Components of a Data Mining

System

Representation
Evaluation
Search
Data management
User interface

14

Topics for this Quarter (Slide 1 of

2)

Data warehousing and OLAP

Decision trees
Rule induction
Bayesian learning
Neural networks
Genetic algorithms

15

Topics for this Quarter (Slide 2 of

2)

Model ensembles
Instance-based learning
Learning theory
Association rules
Clustering

16

Data Warehousing and OLAP

What is a data warehouse?

A multi-dimensional data model

Data warehouse architecture

Data warehouse implementation

Extensions of data cubes

From data warehousing to data mining

17

What is a Data Warehouse?

Defined in many different ways, but not rigorously.

A decision support database that is maintained
separately from the organizations operational
database
Support information processing by providing a
solid platform of consolidated, historical data for
analysis.
A data warehouse is a subject-oriented, integrated,
time-variant, and nonvolatile collection of data in
support of managements decision-making
process.W. H. Inmon
Data warehousing:
The process of constructing and using data
warehouses
18

Data WarehouseSubjectOriented

Organized around major subjects, such as

customer, product, sales.

Focusing on the modeling and analysis of data for

decision makers, not on daily operations or
transaction processing.

Provide a simple and concise view around

particular subject issues by excluding data that
are not useful in the decision support process.
19

Data WarehouseIntegrated

Constructed by integrating multiple,

heterogeneous data sources
relational databases, flat files, on-line
transaction records
Data cleaning and data integration techniques
are applied.
Ensure consistency in naming conventions,
encoding structures, attribute measures, etc.
among different data sources

E.g., Hotel price: currency, tax, breakfast covered,

etc.

When data is moved to the warehouse, it is

converted.
20

Data WarehouseTime Variant

The time horizon for the data warehouse is

significantly longer than that of operational systems.

Operational database: current value data.

Data warehouse data: provide information from a

historical perspective (e.g., past 5-10 years)

Every key structure in the data warehouse

Contains an element of time, explicitly or implicitly

But the key of operational data may or may not

contain time element.

21

Data WarehouseNon-Volatile

A physically separate store of data transformed from

the operational environment.

Operational update of data does not occur in the

data warehouse environment.

Does not require transaction processing, recovery,

and concurrency control mechanisms

Requires only two operations in data accessing:

initial loading of data and access of data.

22

Data Warehouse vs. Heterogeneous

DBMS

Traditional heterogeneous DB integration:

Build wrappers/mediators on top of heterogeneous databases

Query driven approach

When a query is posed to a client site, a meta-dictionary is

used to translate the query into queries appropriate for
individual heterogeneous sites involved, and the results are
integrated into a global answer set
Complex information filtering, compete for resources

Data warehouse: update-driven, high performance

Information from heterogeneous sources is integrated in

advance and stored in warehouses for direct query and analysis

23

Data Warehouse vs. Operational

DBMS

OLTP (on-line transaction processing)

Major task of traditional relational DBMS

Day-to-day operations: purchasing, inventory, banking,

manufacturing, payroll, registration, accounting, etc.

OLAP (on-line analytical processing)

Major task of data warehouse system

Data analysis and decision making

Distinct features (OLTP vs. OLAP):

User and system orientation: customer vs. market

Data contents: current, detailed vs. historical, consolidated

Database design: ER + application vs. star + subject

View: current, local vs. evolutionary, integrated

Access patterns: update vs. read-only but complex queries

24

OLTP vs. OLAP

OLTP

OLAP

users

clerk, IT professional

knowledge worker

function

day to day operations

decision support

DB design

application-oriented

subject-oriented

data

current, up-to-date
detailed, flat relational
isolated
repetitive

historical,
summarized, multidimensional
integrated, consolidated
ad-hoc
lots of scans

unit of work

read/write
index/hash on prim. key
short, simple transaction

# records accessed

tens

millions

#users

thousands

hundreds

DB size

100MB-GB

100GB-TB

metric

transaction throughput

query throughput, response

usage
access

complex query

25

Why Separate Data Warehouse?

High performance for both systems

DBMS tuned for OLTP: access methods, indexing,
concurrency control, recovery
Warehousetuned for OLAP: complex OLAP queries,
multidimensional view, consolidation.
Different functions and different data:
missing data: Decision support requires historical
data which operational DBs do not typically maintain
data consolidation: DS requires consolidation
(aggregation, summarization) of data from
heterogeneous sources
data quality: different sources typically use
inconsistent data representations, codes and
formats which have to be reconciled
26

Data Warehousing and OLAP

What is a data warehouse?

A multi-dimensional data model

Data warehouse architecture

Data warehouse implementation

Extensions of data cubes

From data warehousing to data mining

27

From Tables and

Spreadsheets to Data
Cubes
A data warehouse is based on a multidimensional data
model which views data in the form of a data cube

A data cube, such as sales, allows data to be modeled and

viewed in multiple dimensions

Dimension tables, such as item (item_name, brand,

type), or time(day, week, month, quarter, year)

Fact table contains measures (such as dollars_sold) and

keys to each of the related dimension tables

In data warehousing literature, an n-D base cube is called a

base cuboid. The topmost 0-D cuboid, which holds the
highest-level of summarization, is called the apex cuboid.
The lattice of cuboids forms a data cube.
28

Cube: A Lattice of
Cuboids
all
time

time,item

0-D(apex) cuboid

item

time,location

location

item,location

time,supplier
time,item,location

supplier

location,supplier

item,supplier

time,location,supplier

time,item,supplier

1-D cuboids

2-D cuboids
3-D cuboids

item,location,supplier

4-D(base) cuboid
time, item, location, supplier
29

Conceptual Modeling
of Data Warehouses

Modeling data warehouses: dimensions & measures

Star schema: A fact table in the middle connected

to a set of dimension tables

Snowflake schema: A refinement of star schema

where some dimensional hierarchy is normalized
into a set of smaller dimension tables, forming a
shape similar to snowflake

Fact constellations: Multiple fact tables share

dimension tables, viewed as a collection of stars,
therefore called galaxy schema or fact constellation
30

time

Example of Star Schema

item

time_key
day
day_of_the_week
month
quarter
year

Sales Fact Table

time_key
item_key
branch_key

branch
branch_key
branch_name
branch_type

location_key
units_sold
dollars_sold
avg_sales

item_key
item_name
brand
type
supplier_type

location
location_key
street
city
province_or_street
country

Measures
31

time

Example of Snowflake Schema

time_key
day
day_of_the_week
month
quarter
year

item
Sales Fact Table
time_key
item_key
branch_key

branch

location_key

branch_key
branch_name
branch_type

units_sold
dollars_sold
avg_sales

Measures

item_key
item_name
brand
type
supplier_key

supplier

supplier_key
supplier_type

location
location_key
street
city_key

city

city_key
city
province_or_street
country
32

Example of Fact
Constellation

time

time_key
day
day_of_the_week
month
quarter
year

item
Sales Fact Table
time_key
item_key

item_key
item_name
brand
type
supplier_type

Shipping Fact Table

time_key
item_key
shipper_key
from_location

branch_key
location_key

branch
branch_key
branch_name
branch_type

units_sold
dollars_sold
avg_sales

Measures

location

to_location

location_key
street
city
province_or_street
country

dollars_cost
units_shipped
shipper
shipper_key
shipper_name
location_key
shipper_type 33

Measures: Three
Categories

distributive: if the result derived by applying the function

to n aggregate values is the same as that derived by
applying the function on all the data without partitioning.

algebraic: if it can be computed by an algebraic function

with M arguments (where M is a bounded integer), each
of which is obtained by applying a distributive aggregate
function.

E.g., count(), sum(), min(), max().

E.g., avg(), min_N(), standard_deviation().

holistic: if there is no constant bound on the storage size

needed to describe a subaggregate.

E.g., median(), mode(), rank().

34

A Concept Hierarchy: Dimension

(location)
all

all
Europe

region
country
city
office

Germany

Frankfurt

...

...

...

Spain

North_America
Canada

Vancouver ...
L. Chan

...

...

Mexico

Toronto

M. Wind
35

Specification of Hierarchies

Schema hierarchy
day < {month < quarter; week} < year

Set_grouping hierarchy
{1..10} < inexpensive

36

Multidimensional Data
Sales volume as a function of product,
month, and region

Dimensions: Product, Location, Time

Hierarchical summarization paths

Re
gi
on

Industry Region

Year

Product

Category Country Quarter

Product

City
Office

Month Week
Day

Month
37

Pr
od
u

TV
PC
VCR
sum

1Qtr

2Qtr

Date

3Qtr

4Qtr

sum

Total annual sales

of TV in U.S.A.
U.S.A
Canada
Mexico

Country

ct

A Sample Data Cube

sum

38

Cuboids Corresponding to the

Cube
all
0-D(apex) cuboid
product
product,date

date

country

product,country

1-D cuboids
date, country

2-D cuboids

product, date, country

3-D(base) cuboid

39

Browsing a Data Cube

Visualization
OLAP capabilities
Interactive manipulation
40

Typical OLAP Operations

Roll up (drill-up): summarize data

Drill down (roll down): reverse of roll-up

project and select

Pivot (rotate):

from higher level summary to lower level summary or

detailed data, or introducing new dimensions

Slice and dice:

by climbing up hierarchy or by dimension reduction

reorient the cube, visualization, 3D to series of 2D planes.

Other operations

drill across: involving (across) more than one fact table

drill through: through the bottom level of the cube to its

back-end relational tables (using SQL)
41

A Starnet Query Model

Customer Orders

Shipping Method

Customer
CONTRACTS

AIR-EXPRESS

ORDER

TRUCK
Time

PRODUCT LINE
ANNUALY QTRLY

DAILY

CITY

PRODUCT ITEM

Product

PRODUCT GROUP

SALES PERSON

COUNTRY
DISTRICT
REGION
Location

Each circle is
called a
footprint

DIVISION
Promotion

Organization
42

Data Warehousing and OLAP

What is a data warehouse?

A multi-dimensional data model

Data warehouse architecture

Data warehouse implementation

Extensions of data cubes

From data warehousing to data mining

43

Data Warehouse Design

Process

Choose the grain (atomic level of data) of the

business process
Choose a business process to model, e.g., orders,
invoices, etc.
Choose the dimensions that will apply to each
fact table record
Choose the measure that will populate each fact
table record

44

Multi-Tiered Architecture
other

Metadata

source
s
Operational

DBs

Extract
Transform
Load
Refresh

Monitor
&
Integrator

Data
Warehouse

OLAP Server

Serve

Analysis
Query
Reports
Data mining

Data Marts

Data Sources

Data Storage

OLAP Engine Front-End Tools

45

Three Data Warehouse

Models

Enterprise warehouse
collects all of the information about subjects spanning
the entire organization
Data Mart
a subset of corporate-wide data that is of value to a
specific groups of users. Its scope is confined to
specific, selected groups, such as marketing data mart

Independent vs. dependent (directly from warehouse) data mart

Virtual warehouse
A set of views over operational databases
Only some of the possible summary views may be
materialized

46

Data Warehouse
Development: A
Recommended Approach
Multi-Tier Data
Warehouse

Distributed
Data Marts

Data
Mart

Data
Mart

Model refinement

Enterprise
Data
Warehouse

Model refinement

Define a high-level corporate data model

47

OLAP Server Architectures

Relational OLAP (ROLAP)

Use relational or extended-relational DBMS to store and manage
warehouse data and OLAP middle ware to support missing
pieces
Include optimization of DBMS backend, implementation of
aggregation navigation logic, and additional tools and services
greater scalability
Multidimensional OLAP (MOLAP)
Array-based multidimensional storage engine (sparse matrix
techniques)
fast indexing to pre-computed summarized data
Hybrid OLAP (HOLAP)
User flexibility, e.g., low level: relational, high-level: array
Specialized SQL servers
specialized support for SQL queries over star/snowflake schemas
48

Data Warehousing and OLAP

What is a data warehouse?

A multi-dimensional data model

Data warehouse architecture

Data warehouse implementation

Extensions of data cubes

From data warehousing to data mining

49

Efficient Data Cube Computation

Data cube can be viewed as a lattice of cuboids

The bottom-most cuboid is the base cuboid

The top-most cuboid (apex) contains only one cell

How many cuboids in an n-dimensional cube with L

levels?
n
T ( Li 1)
i 1

Materialization of data cube

Materialize every (cuboid) (full materialization), none

(no materialization), or some (partial materialization)

Selection of which cuboids to materialize

Based on size, sharing, access frequency, etc.

50

Cube Operation

Transform it into SQL-like language (with new

operator cube by, introduced by Gray et al.96)
SELECT item, city, year, SUM (amount)
FROM SALES

()

CUBE BY item, city, year

Need compute the following Group-Bys
(city)
(item)
(item, city, year),
(item, city), (item, year), (city, year),
(city, item)
(city, year)
(item), (city), (year)
()

(year)

(item, year)

(city, item, year)

51

Efficient Processing of OLAP

Queries
Determine which operations should be performed
on the available cuboids:

transform drill, roll, etc. into corresponding SQL

and/or OLAP operations, e.g, dice = selection +
projection

Determine to which materialized cuboid(s) the

relevant operations should be applied.

Exploring indexing structures and compressed vs.

dense array structures in MOLAP
52

Metadata Repository

Meta data is the data defining warehouse objects. It has the

following kinds
Description of the structure of the warehouse

Operational meta-data

schema, view, dimensions, hierarchies, derived data defn, data

mart locations and contents
data lineage (history of migrated data and transformation path),
currency of data (active, archived, or purged), monitoring
information (warehouse usage statistics, error reports, audit trails)

The algorithms used for summarization

The mapping from operational environment to the data
warehouse
Data related to system performance
Business data

business terms and definitions, ownership of data, charging policies

53

Data Warehouse Back-End Tools and

Utilities

Data extraction:

Data cleaning:

convert data from legacy or host format to

warehouse format

Load:

detect errors in the data and rectify them when

possible

Data transformation:

get data from multiple, heterogeneous, and external

sources

sort, summarize, consolidate, compute views, check

integrity, and build indicies and partitions

Refresh

propagate the updates from the data sources to the

warehouse
54

Data Warehousing and OLAP

What is a data warehouse?

A multi-dimensional data model

Data warehouse architecture

Data warehouse implementation

Extensions of data cubes

From data warehousing to data mining

55

Discovery-Driven Exploration of
Data Cubes

Hypothesis-driven: exploration by user, huge search space

Discovery-driven (Sarawagi et al.98)

pre-compute measures indicating exceptions, guide user

in the data analysis, at all levels of aggregation

Exception: significantly different from the value

anticipated, based on a statistical model

Visual cues such as background color are used to reflect

the degree of exception of each cell

Computation of exception indicator (modeling fitting and

computing SelfExp, InExp, and PathExp values) can be
overlapped with cube construction
56

Examples: Discovery-Driven Data

Cubes

57

Complex Aggregation at Multiple

Granularities: Multi-Feature Cubes

Multi-feature cubes (Ross, et al. 1998): Compute complex queries

involving multiple dependent aggregates at multiple granularities

Ex. Grouping by all subsets of {item, region, month}, find the

maximum price in 1997 for each group, and the total sales
among all maximum price tuples
select item, region, month, max(price), sum(R.sales)
from purchases
where year = 1997
cube by item, region, month: R
such that R.price = max(price)

Continuing the last example, among the max price tuples, find
the min and max shelf life, and find the fraction of the total sales
due to tuple that have min shelf life within the set of all max price
tuples
58

Data Warehousing and OLAP

What is a data warehouse?

A multi-dimensional data model

Data warehouse architecture

Data warehouse implementation

Extensions of data cubes

From data warehousing to data mining

59

Data Warehouse Usage

Three kinds of data warehouse applications

Information processing

Analytical processing

multidimensional analysis of data warehouse data

supports basic OLAP operations, slice-dice, drilling, pivoting

Data mining

supports querying, basic statistical analysis, and reporting

using crosstabs, tables, charts and graphs

knowledge discovery from hidden patterns

supports associations, constructing analytical models,
performing classification and prediction, and presenting the
mining results using visualization tools.

Differences among the three tasks

60

From Online Analytical

Processing to Online Analytical
Mining (OLAM)

Why online analytical mining?

High quality of data in data warehouses

DW contains integrated, consistent, cleaned data
Available information processing structure surrounding
data warehouses

ODBC, OLEDB, Web accessing, service facilities,

reporting and OLAP tools
OLAP-based exploratory data analysis

mining with drilling, dicing, pivoting, etc.

On-line selection of data mining functions

integration and swapping of multiple mining

functions, algorithms, and tasks.

Architecture of OLAM
61

An OLAM Architecture
Mining query

Mining result

Layer4
User Interface

User GUI API

OLAM
Engine

OLAP
Engine

Layer3
OLAP/OLAM

Data Cube API

Layer2

MDDB

Filtering&Integration

Database API

MDDB
Meta
Data
Filtering

Layer1
Databases

Data cleaning

Data
Data integration Warehouse

Data
Repository

62

Summary

Data warehouse

A multi-dimensional model of a data warehouse

Star schema, snowflake schema, fact constellations

A data cube consists of dimensions & measures

OLAP operations: drilling, rolling, slicing, dicing and pivoting

OLAP servers: ROLAP, MOLAP, HOLAP
Efficient computation of data cubes

A subject-oriented, integrated, time-variant, and nonvolatile

collection of data in support of managements decision-making
process

Partial vs. full vs. no materialization

Multiway array aggregation
Bitmap index and join index implementations

Extensions of data cubes

Discovery-drive and multi-feature cubes

From OLAP to OLAM (on-line analytical mining)
63