HIST 303 Syllabus

University of Waterloo
Department of History
HIST 303
History Gone Digital: An Introduction
WINTER 2017
8:30-9:20am Mondays and Wednesday, HH 1102

Instructor Information
Instructor: Dr. Ian Milligan
Office: Hagey Hall 114
Office Phone: (519) 888-4567 x32775
Office Hours: Monday 3:00-4:00pm or by appointment
E-Maili2milligan@uwaterloo.ca
 
Course Description
Digital history, the application of new and emerging technologies to the study of history, is an exciting new field. In this course, we are going to explore the literature on digital history, and then put theory into practice by digitally collecting, evaluating, and producing historical knowledge. Some critical topics for this course include: 

  • What is digital history?
  • How new technology can transform historical work, through introductory data mining, textual analysis, spatial analysis, and data visualization
  • How to put history online: making websites, blogs, and engaging with the public (public history)
  • How digital archives are changing how we preserve history
  • How gaming can shake up the historical landscape

This course aims to be different than other history courses you’ve taken. While I will lecture a bit throughout the class, much of it will be hands-on: playing with tools, experimenting with various software packages, getting out of the classroom from time to time, with an eye to active and engaged learning.

You will notice that the reading load is a bit lighter for this course. To make up for this, I will occasionally ask you to do some short ‘homework’ assignments: be it a blog post, asking you to pre-install a piece of software before you come to class on your laptop if you have one, and asking you to spend a decent amount of time on your assignment.

 
Course Goals and Learning Objectives
We have three goals for this course:

  1. The development of a digital portfolio, which showcases your work with several digital platforms, tools, and languages (including WordPress, Omeka, SketchUp, basic GIS, and basic Python).
  2. Through regular short writing, work on your written communication skills.
  3. Have fun and engaged learning through hands-on work.
 
Required Texts
There are two free textbooks that we use in this course:

Dan Cohen and Roy Rosenzweig, Digital History: A Guide to Gathering, Preserving, and Presenting the Past on the Web. University of Pennsylvania Press, 2005.Available online at http://chnm.gmu.edu/digitalhistory/

Shawn Graham, Ian Milligan, and Scott Weingart. Big Digital History: Exploring Big Data Through a Historian’s Macroscope. Imperial College Press, 2016. Available online in parts at http://www.themacroscope.org/.

Assessment in a Nutshell
Assessment Date of Evaluation Weighting
Participation Ongoing 15%
Ongoing Course Blog Ongoing, See Below 30%
Final Project Proposal 1 February 2017 10%
Final Project 3 April 2017 35%
Final Project Lightning Talk 13 March or 15 March 2017 10%
 
Assignment Breakdown

Assessment #1: Tutorial and Course Participation (15%)

Students are expected to be actively involved in lecture and tutorial discussions. Remember: this is not a straight-up lecture course, so it will be a bit more active in terms of participating. I expect you to:

  • Attend class regularly with the readings completed
  • Make a conscientious effort to learn and explore course themes and concepts
  • If you ever have a question, feel struck, or if anything arises – don’t hesitate to contact me.

Assessment #2: Ongoing Course Blog (30%)

Rather than short assignments, we will write a series of short blog posts on the course blog. There are six required blog posts, each of which can be between 500 to 800 words. Blog posts are not essays – they are simply there to show that you’re playing with the material and showing off some of your results.

BLOG POSTS ARE DUE BY THE END OF THE WEEK LISTED BELOW (Friday @ 11:59pm).

They are listed below, but for your reference they are:

  • Week of January 9th: Write an initial post just saying hi and why you are interested in the course. This is more just to make sure that we’ve all got blogs set up!
    • I would also like you to set up an ‘about‘ page describing who are you, including a picture of yourself (or an avatar), and 250 words of personal description.
  • Week of January 16th: Write a post about the three sites listed in the syllabus: what are they? What do they offer? Are they valuable? Representative?
  • Week of January 30th: Write a short blog post on the Science article, the N-Gram viewer, and the Mining the Dispatch site. What do you think? Play with the N-Gram Viewer and tell me about some interesting things you find.
  • Week of February 6th: Write a short blog post on your project. What are you hoping to do?
  • Week of March 6th: Write a shot blog post on your early encounters with Python. How far did you get? Do you think this is a valuable approach for historians? Why or why not? 
  • Final week: Write a short blog post revisiting your first post: do you still agree? What do you think of digital history?

Each blog post will be evaluated on the following criteria:

  • Clarity: Is it well written? Does the blog post follow proper spelling, grammar, and stylistic conventions?
  • Engagement: Does the post engage with the assignment? Does it demonstrate that you have used the tool?
  • Description: What is the tool?
  • Analysis: Be critical. If you are frustrated, if you do not think something makes sense, or if a tool does not seem useful, this is OK. If you think it is the best thing since sliced bread, this is OK as well!

Assessment #3: Final Project PROPOSAL

400-500 words (roughly two pages, double-spaced) – due February 1 (via LEARN). For this, you need to do the following:

  • What is your project going to be?
  • What sources will you be drawing on?

Assessment #4: Final Project

This is a major research project for this course, but will allow you to pursue one of the six tools that you have explored in depth. There is quite a bit of freedom in what you want to do. The project is due on our last day of class, on April 3rd and should be the rough workload equivalent of a 10-12 page paper in terms of workload.

For this assignment, YOU WILL PICK ONE OF THE FOLLOWING TO DO!

  • Research, establish, and write a historical website: Using Omeka or WordPress, create a small public history website. This could be of:
    • University of Waterloo topics: cataloguing public art, buildings, nature, and so forth on campus.
    • Local history: finding historical sites, plaques, etc.
    • Other (preferably something you love)
    • Here, you’ll be building on examples we discuss in class.

~ OR ~

  • Conduct large-scale textual analysis and share your analysis: In consultation with me, we can find a corpus that you could then explore using tools such as topic modeling, n-grams, voyant tools, and so forth.
    • I can also provide ready made corpuses, including historical plaques, historical books, and so forth.
    • The end result can be a historical paper (8-10 pages) or can be a website explaining your findings (similar to Mining the Dispatch).

~ OR ~

  • Carry out spatial research: With maps, in consultation with the library, me, or city resources, come up with a question. Can we map historical maps onto current grids? Can you make an interactive historical document using Neatline? You could do one of UW, one of the local community, or elsewhere.

~ OR ~

  • Create a tool with Python: Building on our introductory Programming Historian 2 work, you could find a corpus online, find a way to spider the sources, and program your own textual analysis tools. As with above, you could write a historical paper (8-10 pages) which would note your own experiences as well as findings, or put this on your website.

~ OR ~

Something else! Come talk to me in office hours.

Assessment #5: Final Project Lightning Talk (10%)

This will involve quickly showing off what you’ve done to the rest of the class.

 
Week-by-Week Breakdown
Week 1: January 4th, Introduction

Reading: “Introduction: Promises and Perils of Digital History,” in Digital History.

Week 2: January 9th and 11th, The History Web

Reading: “Exploring the History Web,” in Digital History.

Reading (for tutorial): “Interchange: The Promise of Digital History,” available online, http://www.journalofamericanhistory.org/issues/952/interchange/index.html

Lara Putnam, “The Transnational and the Text-Searchable: Digitized sources and the Shadows They cast,” American Historical Review, Vol. 121, No. 2 (April 2016): 377-402. Available online via LEARN.

Homework: Set up a WordPress.com blog, and say hi in your first post! Who are you, why are you in the course, what is your background?

Week 3: January 16th and 18th, Citizen Histories and Web Histories

Reading: “Designing for the History Web,” in Digital History.

Toni Appelbaum, “How the Professor Who Fooled Wikipedia Got Caught by Reddit,” 15 May 2012, available online, http://www.theatlantic.com/technology/archive/2012/05/how-the-professor-who-fooled-wikipedia-got-caught-by-reddit/257134/.

Explore the following websites:

9/11 Digital Archive: http://911digitalarchive.org

Hurricane Katrina Archive: http://hurricanearchive.org

Occupy Archive: http://occupyarchive.org

Homework: Write a short blog post on the three websites listed above. What are they? What do they offer? Are they valuable? Representative? (500-800 words)

Week 4: January 23rd and 25th, Podcasting and Sketchup 

Reading: “Building an Audience,” in Digital History.

Devon Elliott, Robert MacDougall, and William J. Turkel, “New Old Things: Fabrication, Physical Computing, and Experiment in Historical Practice,” Canadian Journal of Communication, 37 (2012): 121-128. http://www.cjc-online.ca/index.php/journal/article/view/2506.

Homework: Play with Sketchup Make. Make a simple object and we will look into 3D printing it.

Week 5: January 30th and Februrary 1st, Textual Analysis: From Word Clouds to Topic Modeling

Reading: Jean-Baptiste Michel et al, “Quantitative Analysis of Culture Using Millions of Digitized Books,” Science. Michel et al – Quantiative Analysis of Culture.pdf

Graham, Milligan, and Weingart. “Basic Text Mining,” at http://www.themacroscope.org/?page_id=362.

Graham, Milligan, and Weingart. “Topic Modeling by Hand,” at http://www.themacroscope.org/?page_id=47.

Read the following websites and explore the projects:

– Mining the Dispatch: http://dsl.richmond.edu/dispatch/

– Google N-Gram: http://books.google.com/ngrams

Homework: Write a short blog post on the Science article, the N-Gram viewer, and the Mining the Dispatch website. Play with them! Have fun! What do you think?

Week 6: February 6th and 8th, Digitizing Primary Documents

Reading: “Collecting History Online” and “Preserving Digital History,” in Digital History.

Reading: Explore the Internet Archive at http://archive.org.

Week 7: February 13th and 15th, Spatial Histories

Reading: “What is Spatial History?” http://www.stanford.edu/group/spatialhistory/cgi-bin/site/pub.php?id=29

Jo Guldi, “What is the Spatial Turn?” Click around, but specifically focus on “The Spatial Turn in History.” http://spatial.scholarslab.org/spatial-turn/

Trading Consequences Project – read the blog at http://tradingconsequences.blogs.edina.ac.uk/, the linked White Paper, and play with the visualizations.

Homework: Play with Neatline and Google Earth.

One-on-one meetings with Professor Milligan re: your project begin.

Week 8: February 27th and March 1st, Humanities Programming

Readings: The Programming Historian, available online, http://programminghistorian.org.

We will focus primarily on:

– Data Manipulation (Introduction to the Bash command line);

– Setting up Python;

– And the pathway towards interacting with the Old Bailey Online with Python.

Those of you with past programming experience will get some other fun stuff to do.

ONE-ON-ONE MEETINGS WITH PROFESSOR MILLIGAN RE: YOUR PROJECT CONTINUE.

Week 9: March 6th and 8th, Humanities Programming

Readings: The Programming Historian, available online, http://programminghistorian.org. Continuing our work from last week. The Monday class will be largely the same, and Wednesday will have some options to branch out to explore areas that interest you.

Homework: After our introductory classes, begin to work through the lessons. Write up a short blog post on your encounters with Python. How far did you get? Do you think this is a valuable approach for historians? Why or why not?

Note that I do not expect you to become the best Python programmer in the world. Instead, these readings are to help you start thinking about programming and whether we think it matters for Arts students. At the end of the day, if you hated it and got nowhere, that’s fine!

Week 10: March 13th and 15th, Lightning Talks

Each student will present a short lightning talk on their research in progress, with time for questions.

Refreshments will be provided, conference style.

Week 11: March 20th and 23rd, Video Games

Readings will be provided.

These will be the last readings for the course, giving you time to focus on your project.

Week 12: March 27th and 29th, No class, but we will schedule final meetings with Professor Milligan.

Week 13: April 3rd, Course Conclusion

 
Course Policies

Late Work

Late work is generally penalized at five percent a day, unless you are in touch with me beforehand and we work something out. If you are submitting a late assignment, e-mail it to me and bring a hard copy (if applicable) to the next class. I will ‘stop the clock’ based on when your e-mail is stamped.

Electronic Device Policy

You are encouraged to bring and use laptops, smartphones, tablets, etc. to class, although I do expect that you will use it responsibly and not distract your classmates.

Institutional-required statements for undergraduate course outlines approved by Senate Undergraduate Council, April 14, 2009

Academic Integrity

In order to maintain a culture of academic integrity, members of the University of Waterloo community are expected to promote honesty, trust, fairness, respect and responsibility.  See the UWaterloo Academic Integritity Webpage (https://uwaterloo.ca/academic-integrity/) and the Arts Academic Integrity Office Webpage (http://arts.uwaterloo.ca/current-undergraduates/academic-responsibility) for more information.

Discipline

A student is expected to know what constitutes academic integrity to avoid committing academic offenses and to take responsibility for his/her actions. A student who is unsure whether an action constitutes an offense, or who needs help in learning how to avoid offenses (e.g., plagiarism, cheating) or about “rules” for group work/collaboration should seek guidance from the course professor, academic advisor, or the undergraduate associate dean. For information on categories of offenses and types of penalties, students should refer to Policy 71, Student Discipline (http://www.adm.uwaterloo.ca/infosec/Policies/policy71.htm). For typical penalties check Guidelines for the Assessment of Penalties (http://www.adm.uwaterloo.ca/infosec/guidelines/penaltyguidelines.htm).

Grievance

A student who believes that a decision affecting some aspect of his/her university life has been unfair or unreasonable may have grounds for initiating a grievance. Read Policy 70, Student Petitions and Grievances, Section 4 (https://uwaterloo.ca/secretariat/policies-procedures-guidelines/policy-70). When in doubt please be certain to contact the department’s administrative assistant who will provide further assistance.

Appeals

A decision made or penalty imposed under Policy 70, Student Petitions and Grievances (other than a petition) or Policy 71, Student Discipline may be appealed if there is a ground. A student who believes he/she has a ground for an appeal should refer to Policy 72, Student Appeals (http://www.adm.uwaterloo.ca/infosec/Policies/policy72.htm).

Note for Students with Disabilities

The Office for Persons with Disabilities (OPD), located in Needles Hall, Room 1132, collaborates with all academic departments to arrange appropriate accommodations for students with disabilities without compromising the academic integrity of the curriculum. If you require academic accommodations to lessen the impact of your disability, please register with the OPD at the beginning of each academic term.