Tutorial Demo and Final Project

Agenda:

Final Project Work in breakouts to continue work and start Presentation

Final Project — Data Visualization (due Sunday)

Your final projects should contain at least one interactive data visualization or interface to your data. These will usually be built in a platform outside of your final project website and embedded within it.

Specs: for this lab, embed at least one of your group’s visualizations in a brief post in which you describe

  • what the data are (based on what sources, cleaned/filtered how)
  • what tool or technique you used to visualize it
  • what the data viz is doing (exploratory or explanatory, showing what patterns of interest, etc.)
  • what you have done to style the visualization to increase its clarity

This need not go into all the detail of the goal of the project, sources and methods (save that for the final website!), but should show how are using digital tools to interpret the sources you gathered for your project.


LOOKING AHEAD:

Final Project — Publication and Presentation (Week 10)

Projects will be published IN SOME FORM by the final day of class, but do not need to be finalized.

On the last day of class each group will give a Pecha Kucha style presentation on their completed and published project.  The rules of such a presentation are below, with credits for the format going to Ryan Cordell, via Jim Spickard.

After getting feedback on the presentation in class, the FINAL WEBSITE OF YOUR PROJECT IS DUE BY the end of our exam time.

  • One member of each group should write a blog post giving a brief introduction and providing a link to the final project, which all team members should submit via moodle.

Final Project Presentations: Pecha Kucha 1/1/5 (due in class Tuesday)

In this presentation, you will have exactly 6 minutes and 40 seconds to present your material: 20 slides that auto-advance every 20 seconds. These presentations will follow the Pecha Kucha presentation format. Here are the rules:

  • You will have exactly 6 minutes and 40 seconds.
  • Your presentation will use PowerPoint (or Keynote or Google Presentations), but you’ll be restricted to 20 slides. No more, no less. Period.
  • Each slide must be set to auto-advance after 20 seconds. No clickers, no exceptions.
  • Your presentation must also follow the 1/1/5 rule. You must have at least one image per slide, you can use each exact image only once, and you should add no more than five words per slide.
  • You may trade off between your members however you see fit, but the presentation should be rehearsed and polished.

You should not attempt tell us everything that you might say in a written paper nor explain every nuance of your argument. Instead, you should be looking to give us an overview of the project and highlighting its particular strengths. When designing the presentation, think SHORT, INFORMAL, and CREATIVE. Perhaps surprisingly, the Pecha Kucha form’s restriction (paradoxically) promotes this creativity.

Example Presentation

Below is an example of how this might work based on a previous class project. To set Google Slides to autoadvanced, you have to publish to the web and change the “delayms” parameter to 20000 milliseconds. (View source below to see the embed code.)

css.php