Final Project Work Session

Taking Stock of Assignments

First, congrats on completing your midterm mini-projects! They look great so far and I’ll be giving you detailed feedback ASAP, posted in Moodle.

Second, I’ve thrown a lot at you this term, in a different format than you’re probably used to, so let’s take stock of what we’ve done. Here are the assignments that you should have completed so far:

Blog Posts (A = 6-7)Lab Posts (A = 6)
Defining DHFusion 360
Reverse engineer a projectCoding with Html/CSS
Exploratory data vizPersonal Site Setup
Network analysis reflectionArchives photos and Omeka entry
3D model process (free credit)3D model (free credit)
Georeferencing historical mapsCampus Map
Tutorial Assignment (due next Friday)

Final Project Work

Today is dedicated to work on our final projects, which we began brainstorming last week. The final project consists of five graded components, with details on the Final Project Prompt.

Today we will:

  1. Form groups and finalize project ideas
  2. Complete the Project Pitch and Team Charter
  3. Set up a project subdomain
  4. Begin Source Documentation

Before diving in, check out the annual DH Awards for inspiration. These are annual community awards (with a prize of nothing but bragging rights). They don’t seem to have 2023 nominations open yet, but you can check out past winners through 2022. There should be good inspiration as we work towards our own final projects.

Also, I completed processing a selection of your 3D photogrammetry objects and created a small digital exhibit on our class Omeka page. Check it out to see what you might do!

In Class: Register a subdomain

Consult with your teammates and fill out the following form to request a subdomain of hhfinals.dgah.sites.carleton.edu to host your project

FINAL PROJECT SUBDOMAIN REGISTRATION FORM

Component 1: Project Pitch and Team Charter (Due Friday)

Form a group of 3-5 and choose or invent a project (drawing on the brainstorming document). Collectively write a blog post the lays out your project pitch and group charter.

Project Pitch

  • Members of the group
  • The project topic and objectives for what you plan to produce
  • The proposed methodology:
    • Sources: What data do you hope to use and how do you hope to find it?
    • Processes: What tools and techniques will you use to gather sources and store your data?
      • What analyses or transformations will you conduct on those data?
    • Presentation: How will you present the results and integrate the digital assets you create as an interactive final product?
  • A link to one or more DH projects that you think might make a good model for what you plan to do.
  • Create a unique tag for your group to tag all your posts going forward.

Group Charter

Good collaboration doesn’t just happen! It takes open and sometimes difficult communication. One way to take the trouble out of group work is to lay out issues using a “project charter” (see examples from the Praxis Program at Scholars’ Lab). Determine the following about your group:

  • What are your shared values? Shared goals?  Expectations for each other?
  • How will you communicate and handle disagreements?
  • Assign group role. Who will be responsible for calling meetings or posting to WordPress? Cleaning data? Creating Visualizations? Setting up and editing the project website?
    • Consider each of your strengths and weaknesses, as well as schedules in terms of workflow.

Specs:

  • Post to WordPress by Friday Week 8
  • Tag with your final project
  • Submit link on Moodle
  • No word count, but address all the above questions for both Pitch and Charter

Component 2: Project Update and Source Documentation (due Sunday)

The thing that makes archival materials so captivating is also what makes them challenging to work with in a computational way. Most of you will not be working with perfect data sets. They will require cleaning – or tidying – to get them in a state that can be used by digital tools. Sometimes you need to add data (like coordinates) or remove data (like personal information).

This project component asks you to collectively write a blog post on the course blog that fully documents the sources you’ll be using.

I recommend writing this out on a shared Google Doc and appointing one person to post by Sunday.

Specs: 

  • Post to WordPress and submit the link on Moodle.
  • Tag with your final project consistent tag
  • No word count, but the longer the better. 
  • A list of the sources you plan to use with full citations and links. Each source should include a brief annotation (bullets are fine) that addresses the following:
    • Format – what format is this source in? What format does it need to be in? What do you need to do to get it there?
    • Rights – who owns this material? What are you allowed to use? How do you know?
    • Privacy/ethics – Who is depicted in this data? How? Is there sensitive information that needs to be removed? Any other ethical considerations?
  • A brief update on the progress of your project:
    • What have you done so far, what have you gathered, and what have you built?
    • What applications/languages/frameworks have you selected and how are you going to implement them?
    • What issues have you run into? Have they forced you to change your initial plan?
  • A brief statement from each group member on their contribution thus far to the project

A few ideas based on your topics

Resources from Sarah Calhoun (Digital Humanities Librarian)

css.php