CETL Faculty Forum: “Developing Digital Project Assignments” Notes and Resources

Thanks to those who attended yesterday’s CETL Faculty Forum. If you are interested in learning about different tools and platforms, see this DH Toychest maintained by Professor Alan Liu at UC Santa Barbara. I often use Scalar and Omeka for long-term student projects.

Feel free to adapt my Timeline JS activity to suit your needs.

To see what the students in my DH course Spring 2016 got up to including their reviews of DH journals and how to use certain tools and platforms, see their blog.

For a wide selection of readings that may help you think about digital pedagogy and research ideas, browse through Debates in the Digital Humanities edited by Matthew K. Gold of the CUNY Graduate Center. I always incorporate readings on DH into my longer-term projects to get students to engage with the conversation, and I encourage them to read The Collaborators’ Bill of Rights.

Remember that creating digital projects should be mostly fun, not mostly frustrating. Treat tools and platforms as little discovery playgrounds. Give yourself and your students time to learn how to build your digital products and give them space to teach each other.

Do comment with assignment ideas and links to platforms and tools you’ve used and liked.

Advertisements

“Collaboration on the Digital Humanities Playground” Workshop (Part Two #LANS2016)

In the Digital Humanities, collaboration is key! The following workshop will give you experience with collaborating to create a group timeline using the tool TimelineJS. Below, you’ll find instructions for your collaborative mini-project, links to the tools and tutorials you’ll need, and tips for healthy team-work. Feel free to tweet about your project using the hashtag #LANS2016 and @secornish. HAVE FUN!

Building a Timeline for Your Generation

As a team, you’re going to build a timeline using the tool TimelineJS. It’s a free, open-source tool that works with Google.

Objectives: 
1) Discovering what skills in collaboration come naturally, what you might need to work on more, what frustrates you, and what works well.
2) Learning about how you feel under pressure, and with a new, and probably very foreign task before you.
3) Acknowledging what questions emerge out of your projects that you might want to pursue.

Your project manager should have emailed you a share link to the Google sheets template that you’ll be using for your timeline. Open that sheet in Google Drive.

Part I: Discussing and Planning (10-15 minutes)

What are the moments that define your generation? Are they historical? Political? Social? Cultural? Are there products that you’ll always think of fondly? Books you know you’ll want to share with your children, nieces, and nephews? Movies to which you know all the lines? Political figures who inspire you? Social movements in which you participate? Celebrities who serve as role models? Events that have shaped your perceptions of the world in which you live?

As a group, spend about 10-15 minutes talking about some of the defining events/phenomena/moments that you believe are significant to shaping your identities and, more broadly, your generation.

Part II: Researching and Making (20-25 minutes)

Once you have a good list, each of you will choose one of these items to research. Feel free to use the web as widely as you like.

  1. Learn a few key facts about your chosen item such as a date of occurrence or a general period of popularity or interest.
  2. Find a media item to include in your entry. TimelineJS supports media from YouTube, Wikipedia, Vimeo, Flickr, Twitter, Soundcloud, Google images and maps, screenshots, photos from your hard drive, as well as URLs from many other sites.
  3. Write text to describe your item (just a sentence or two).
  4. Write a media caption for the media you’ve chosen to include.

You can collect all of this information in a Word doc or Stickies note and transfer it to your team’s spreadsheet when you’re ready.

Each person will be responsible for developing a timeline entry. You’ll each need to determine what line number on the spreadsheet is yours so that you don’t accidentally enter information into someone else’s space. If you have time, you can do a second and third entry.

As you work on populating your sheet, help each other out. Spreadsheets can be a bit intimidating.

Your team’s first entry (the blue row) can be used as a title page for your timeline. This might be the last thing you do as a team once you figure out what your overarching narrative wants to be based on everyone’s choices. You might include everyone’s names on this title page. Also, be sure to name your Google sheet something that signals what your timeline is all about.

Part III: Publishing and Sharing (10 minutes)

Once the Google sheet is populated with at least one entry per person on your team, publish it to the web and grab the link, using the instructions here or on the TimelineJS homepage. Paste the link into the field on the TimelineJS homepage to test your timeline. Look carefully at each entry and discuss what looks great and what might need more information. Help each other correct your spreadsheet so that your timeline works the way you want it to work.

When you feel that your timeline is ready to embed into a webpage, you can copy the code and paste it into your own blogs to test it, or send it to me, and I’ll post it on my blog. Remember, the code is different from the link.

You may also share your timeline link via Twitter, Facebook, Google+, and Gmail.

(Note: If you and your team are feeling ambitious and want to continue to build your timeline after this workshop, feel free to send me your code to embed on my blog or a link to your site. I’d love to see how your projects evolve.)

If time permits, we’ll spend a last few minutes talking about your collaborative processes.