Difference between revisions of "CS382:Unit-mashup"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
== Background reading, one or more pointers/documents and a brief synopsis of what's covered in them == | == Background reading, one or more pointers/documents and a brief synopsis of what's covered in them == | ||
| − | * | + | * [http://davidhuynh.net/media/papers/2007/iswc2007-potluck.pdf web tool for non-programmers for making mashups] |
== Lecture notes - outline form == | == Lecture notes - outline form == | ||
* what data do i need? | * what data do i need? | ||
Revision as of 20:32, 17 February 2009
Contents
- 1 Data Visualization with Mashups
- 1.1 Background reading, one or more pointers/documents and a brief synopsis of what's covered in them
- 1.2 Lecture notes - outline form
- 1.3 Classroom response questions - at least three
- 1.4 Lab activity - materials, process and software
- 1.5 Scheduling - early, late, dependencies on other units, length of unit
- 1.6 Archived stuff
Data Visualization with Mashups
Background reading, one or more pointers/documents and a brief synopsis of what's covered in them
Lecture notes - outline form
- what data do i need?
- where do i find data?
- coordinating multiple data sources
- how do i encode that data to be useful?
- what can i discover through visualization?
- how much data do i need to be useful?
- examples
Classroom response questions - at least three
Lab activity - materials, process and software
- Quaker meetings, <metric X> mashed up on map ( database; we own it )
Scheduling - early, late, dependencies on other units, length of unit
Timing
Doesn't matter
Length
One week; but if we find enough material it could be (and would serve well as) two
