COURSE SCHEDULE

WEEK 1 JANUARY 25 ♦ Slides

  • Introduction: A Very Brief History

  • Overview of Course: logistics, structure, enrollment

  • Interactive Data Visualization for the Web by Scott Murray, Chapter 1 & 2 Introductions
  • Interactive Data Visualization for the Web by Scott Murray, Skim Chapter 3 Technology Fundamentals

WEEK 2 FEBRUARY 1 ♦ Slides

  • All About Data: models, structures, and data in your field
  • Technology Fundamentals
  • Introduction to programming (taught with Javascript)

  • Project 1 Assignment ♦ Project Description

  • Interactive Data Visualization for the Web by Scott Murray, Chapter 4 & 5 Setup and Data

WEEK 3 FEBRUARY 8 ♦ Slides

  • Visual Encoding and Graphical Perception:
  • How do we make design choices when it comes to dataviz?
  • Intro to Javascript

  • Project 1 Discussion ♦ Dear Data Worksheets for inspo

  • Interactive Data Visualization for the Web by Scott Murray, Chapter 6 Drawing with Data

WEEK 4 FEBRUARY 15 ♦ Slides

  • Narrative structure and storytelling in the context of visualization and interactivity
  • Drawing with data Demo
  • Interactivity Demo

  • Project 1 Checkin

  • Interactive Data Visualization for the Web by Scott Murray, Chapter 6 Drawing with Data (Repeat with additional HW)

WEEK 5: FEBRUARY 22 ♦ Slides

  • Power of Representation (and misrepresentation)
  • Project 1 Due
  • Project 2 Assignment ♦ Project Description
  • Data loading and manipulation Demo

  • Scales and Axes Demo

  • Interactive Data Visualization for the Web by Scott Murray, Chapter 7 & 8 Scales and Axes

WEEK 6: MARCH 1 ♦ Slides

  • UX/UI Guest Lightning Talk
  • Forms + Stories + Interactivity: Bringing things together
  • Interactivity Demo 1

  • Project 2 Checkin and Discussion

  • Interactive Data Visualization for the Web by Scott Murray, Chapter 9 Updates, Transitions, Motion

WEEK 7: MARCH 8 ♦ Slides

  • Review: graphical perception, narratives, interactivity
  • Interactivity Demo 2

  • Special chart types: D3 Pie and Line Demo and Tutorial

  • Interactive Data Visualization for the Web by Scott Murray, Chapter 10 Interactivity

WEEK 8: MARCH 15 (MIDTERM) ♦ Slides

  • Introduction to special topics
  • Visualizations in the wild - dissecting examples
  • Project 2 Due - New due date Monday of Week 10
  • D3 review Chapters 1 - 10

WEEK 9: MARCH 22 SPRING BREAK

WEEK 10: MARCH 29

  • Project 2 wrap-up
  • Special Topic 1 APIs and Web
  • Planning your final project, discussions, ideas, groups

WEEK 11: APRIL 5

  • Special Topic 2 Web and Mobile Maps
  • Final Project Pitch
  • Troubleshooting Clinic 1

WEEK 12: APRIL 12

  • Special Topic 3 Text
  • Final Project Iteration 1
  • Troubleshooting Clinic 2

WEEK 13: APRIL 19

  • Troubleshooting Clinic 3
  • Project demos tour

WEEK 14: APRIL 26

  • Final Presentations - Guests Review

WEEK 15: MAY 3

  • Discussion on what’s next - where do you go from here?
  • Visit each other’s projects, chat about next steps, have a good time.
  • Final Assignment: Publish your final project and all the documentation.
  • Complete exit survey

EVALUATION

  • Participation 10%
  • Tutorials: 30%
  • Short Projects: 30%
  • Final Project: 30%

COURSE POLICIES

Students in this course will work in accordance to the student honor code and the statement of academic integrity for Columbia University. Please refer to the Faculty Statement of Academic Integrity for all submissions of your work, and contact the instructor if you have any questions about a specific case related to the contents of this course.

HOMEWORK

  • Tutorials are assigned every 1-2 weeks and are designed to take no more than 1.5 hours to complete. They allows hands on experience with code that is addressed in class. They are cumulative and should be completed in sequence. Please contact the TA or Instructor when you encounter issues.
  • Submission Deadlines - Take home assignments are to be submitted before noon on Thursday via student’s individual websites. The TA and instructor will start reviewing submissions at that time.
  • Completeness - Sometimes your code will have bugs that you cannot fix on your own. In those cases, please get in touch with your TA or instructor well ahead of the due date to address the issues together.
  • Code - Commenting your code and attributing code you use are required as part of every programming assignment. Writing comments inline with the code helps you to think through how to best complete particular programming tasks and also helps the instructor troubleshoot with you when there are issues.
  • Extra Credit - Throughout the semester, there will be opportunities to make presentations based on optional readings or completing code projects(demos) on special topics for extra credit throughout the term.

Plagiarism in Coding - Plagiarism can be a serious issue in programming courses. In the context of this course, it is permissible to use pieces of code you find in the wild that suits your project under these circumstances:You have checked the author’s permissions and their work is under either a creative commons, MIT, or similar license in which noncommercial use is permitted.

AND

That you include clear attributions of the code you incorporate from others as comments directly within your work. This includes to the extent available, the author’s name, the URL of the work, and a sentence explaining the function of the code.