Digital Futures of History
Fall 2017 • HIST 300-018
This syllabus is a living document and changes frequently, depending on what’s going on in the course. If you print it out, you’ll need to keep your paper version up to date with the online version. I will always announce important changes in class.
1: Course and Digital History Introduction
Tuesday (Aug 22)
Today we’ll review the syllabus, course aims, assignments, and general plan for the semester. We’ll also figure out how to customize the course to best suit participants’ interests.
Thursday (Aug 24)
2: Archival Power
Tuesday (Aug 29)
- Joan M. Schwartz and Terry Cook, “Archives, Records and Power: The Making of Modern Memory,” 1–19.
- Margaret Hedstrom, “Archives, Memory, and Interfaces with the Past,” 21–43.
Thursday (Aug 31)
3: The Necessity of Critique
Tuesday (Sep 5)
Thursday (Sep 7)
DUE: First DH Project Critique
Bring to class a ~750-word critique for a site listed here, or any of the past projects (links near the top), or here.
- Fred Gibbs, “The Poetics of Digital Scholarship,” 101-122.
4: Historical Data and Algorithms
Tuesday (Sep 12)
DUE (for real): First Critiques
Critiques due (extended deadline from last time).
- Andrew Goldstone and Ted Underwood, “The Quiet Transformations of Literary Studies: What Thirteen Thousand Scholars Could Tell Us.”
Thursday (Sep 14)
5: What is History For?
Tuesday (Sep 19)
- Keith Jenkins, Rethinking History.
Thursday (Sep 21)
6: Text Analysis and Visualization
Tuesday (Sep 26)
DUE: GitHub Test
- Create an account at Github, and email me (email@example.com) your username
- Add a markdown file you create in Dillinger to our repository. Be sure you are logged into GitHub when you do this: Click on the ‘docs’ folder, then drag and drop your file onto your browser window. The content of your markdown file is irrelevant, but be sure your filename has no spaces and ends with .md
- If you are confused about Markdown, try this Markdown tutorial; if you need syntax help, see the cheat sheet
Thursday (Sep 28)
7: Visual and Spatial History
Tues (Oct 3)
Thurs (Oct 5)
- Dolores Hayden, “Place, Memory, and Urban Preservation,” in The Power of Place, 44-78.
- Chris Wilson, “Ethnic/Sexual Personas in Tricultural New Mexico,” 12-34.
- Find a project to critique from Humanities GIS Projects.
- Start thinking about your spatial history project (I’ve put together a few suggestions if you get stuck)
8: Critiquing Spatial History
Tuesday (Oct 10)
DUE: Mapping Project Critique
Post to GitHub your ~800-word critique (a visual essay in Markdown) of a GIS / map project. Be sure to review the guidelines!
- Instructions for our spatial history project
Thursday (Oct 12)
Relax, but not for too long (see below).
9: Spatial History Work Time
(Oct 17 and 19): NO CLASS
READ: Ellen Lupton, Thinking with Type (2nd edition).
No class: Research Break
Work on your Spatial History Projects, following the guidelines.
10: Public Art / Spatial History Project
Tuesday (Oct 24)
- Ellen Lupton, Thinking with Type.
- Discussion of Research Projects (check in to make sure everything is going well)
Thursday (Oct 26)
DUE: Public Art Essays
- All essays (written in Markdown) must be fully visible and functional on GitHub
11: Essays and Video Critiques
Tuesday (Oct 31)
DUE: Spatial History Revisions
- Review of existing JAH digital history reviews
Thursday (Nov 2)
12: Historical and Authorities of Knowledge
Tuesday (Nov 7)
DUE: Spatial History Updates
- All essays should look like the sample essay (copy code from the sample code essay)
- All spatial data should be uploaded to the Google Spreadsheet
- Your KML file created via Google Maps should be uploaded to the kml folder in the docs folder.
- HTML and CSS quiz (review the tutorial!) and questions we didn’t get to last time.
Thursday (Nov 9)
DUE: Essay Improvements
- Add essay header information following the sample on the Code Example Page.
- Add your custom CSS file to the css directory, with some CSS code in it that will change the typography of your essay (for instance, making the headers red as the gibbs.css file does). Add your CSS file the same way you’ve added all your other files (either drag and drop or use the ‘Create new file’ button).
- Start adding hyperlinks to your essays wherever appropriate.
- Start adding footnote references following the example on the Code Example Page
- REMEMBER 1: All the code you need on your page can be copied and pasted from the gray boxes on the Code Example Page.
- REMEMBER 2: You can always view the raw markdown for the Simms Essay to see a complete and live model of how your markdown code should look.
- Review HTML and CSS concepts via scratchpad
- Review existing essays; answer technical questions
- Screencasting basics
Tuesday (Nov 14)
DUE: Last Updates
- Make sure your essays looks and reads exactly as you want, and as I want. This will make peer review more useful for both authors and reviewers. Review the Peer Critique Guidelines!
- IMAGES: You may find that you want to resize, rotate, or crop your images to improve the layout of your essay. While you can control the width easily already, sometimes a bit more editing would go a long way. Use either Fotor or Pixlr. Both are online, free, and straightforward image editing tools that you can figure out with a few minutes of playing around. They both do color correction, filtering, and effects, but mostly you’ll just want to crop, rotate, or resize images—which are super easy to do—and then download a new version of your file. You can’t edit your image on GitHub directly; you’ll have to upload a new version.
Thursday (Nov 16)
14: Clean up and Eating
Tuesday (Nov 21)
Thursday (Nov 23)
15: Catch up
Tuesday (Nov 28)
DUE: First draft of video critique
- Follow the video critique guide
- Put links to your video on our video link page
- I will randomly select some videos to watch and critique in class (be prepared, please. this significantly reduces awkwardness for everyone.)
Thursday (Nov 30)
16: Loose ends
Today is optional; we’ll spend more time critiquing essays and videos for those who want extra feedback. While priority will be given to those who have not had their work critiqued in class thus far, everyone will leave with clearer ideas about how to revise their work before submitting final versions.
The last chance for me to convince you that everything we did was seriously worth it. Also, evaluations and final advice for the assignments.