Week 1

May 28

Things to do for/on May 28

  • If you have a smartphone, download the SCVNGR (you will be using this on the afternoon of the 28th)
  • If you haven’t, complete the 3 required Codecademy tracks
  • If you want, sign up for a Twitter account (if you don’t have one already) – remember to use the #msuchi hashtag when tweeting about fieldschool related stuff.
  • Sign up for a Gravatar account (if you don’t already have one)
  • Activate your course blog account (you will receive an email by Tuesday)
  • Introduce yourself to the world on the blog. Tell us a little about your background and your interests. Be sure talk about why you are taking the fieldschool – why is cultural heritage informatics important to you? This should be done by the end of the week (Friday).
  • Have a look at the Creative Commons Licenses. For each thing you post to the fieldschool blog, you will need to choose the license that best works for you – which means you need to have at least a passing familiarity with what the licenses actually mean. several years ago, the incomparable Bethany Nowviskie (Director of Digital Research & Scholarship at the University of Virginia Library and Associate Director of the Scholarly Communication Institute) wrote a thoughtful piece about why she was switching the license on her blog and Flickr stream from CC-BY-NC to CC-BY. It is definitely worth a read.

Morning Schedule

  • Intro to the fieldschool
  • Student Intros
  • How the schedule works
  • Assignments, etc
  • Final Project
  • Tools and infrastructure we’ll use
  • Expectations
  • What is Cultural Heritage Informatics (what is informatics)
  • born digital heritage vs. digitized heritage
  • Why a fieldschool?
  • What is visualization?
  • Why visualization?
  • Current state of heritage visualization
  • Visualization tools

Afternoon Schedule

  • SCVNGR trek

May 29

Things to do for/on May 29

  • Download WAMP (if you are on a windows machine) or MAMP (if you are on a mac)
  • Download WordPress

Morning Schedule

  • Project Management
  • Building Partnerships
  • Developing an Idea
  • Drafting a vision document
  • Writing a Spec
  • Recruiting/Building a Team
  • Managing expectations and being clear about responsibilities
  • Develop a workplan

Afternoon Schedule

May 30

To be Done for/on May 30

Morning Schedule

  • Tools for managing a project
  • Version Control (distributed vs. centralized vs. social)
  • Issue tracking/bug tracking
  • Task and milestone management
  • Documentation
  • Introduction to GitHub
  • Launching a project
  • Promotion & Sustainability
  • Building a Community
  • Letting a project die (gracefully)
  • Reporting (the the power’s that be, to the community, to partners, to funders)

Afternoon Schedule

  • Github Challenge

May 31

  • Project Document challenge
  • Morning: envision the project with your team, collaboratively write the vision document
  • Afternoon: Present the project, modify project if needed, discuss resources/needs/staff/etc. Write workplan, design design visual prototypes.
  • Project Vision Document Template

Leave a Reply