Digital Scholarship is often collaborative and the final product is inherently different than a thesis, dissertation, journal, or book. How should digital scholarship be evaluated? Is it only the content or does the interface and user experience need to be evaluated as well? Who are the peer viewers? How should credit be shared or “counted” if you are a student, faculty member, librarian or technologist? And of course the larger question- does Digital Scholarship count, full stop?

This is a companion “play” session to the “talk” on crowdsourcing in the digital humanities. In this session we would visit various sites and contribute by reviewing menus, tagging photos, transcribing letters, etc.

We could share our thoughts informally during the process and more formally in a “debriefing” after our group crowdsourcing session. This is seen as a companion to the talk on crowd sourcing, but the two sessions could be compressed into one if necessary.

Possible sites on which to “play”:

• wardepartmentpapers.org
• diyhistory.lib.uiowa.edu/
• www.archives.gov/citizen-archivist/
• menus.nypl.org/
• www.brooklynmuseum.org/opencollection/tag_game/start.php
• www.brooklynmuseum.org/opencollection/freeze_tag/start.php

Crowdsourcing is becoming more and more common in the digital humanities. Here is a sampling of projects which currently include crowdsourcing features:

• wardepartmentpapers.org
• diyhistory.lib.uiowa.edu/
• www.flickr.com/photos/library_of_congress/
• www.pepysdiary.com/
• www.ucl.ac.uk/Bentham-Project
• www.archives.gov/citizen-archivist/
• menus.nypl.org/
• www.brooklynmuseum.org/opencollection/tag_game/start.php
• www.brooklynmuseum.org/opencollection/freeze_tag/start.php
• swem.wm.edu/news/fights-rights/transcription-project
• www.medici.org/

I would be interested in a discussion of how crowdsourcing can be used in digital humanities projects. Topics of discussion could include:

• How to  implement crowdsourcing
• Successes / Failures
• Strengths / Weaknesses
• Issues / Barriers

See also the proposal for a “play” crowdsourcing session.

There is a necessary tension between University IT departments and the curious digital humanist, computer scientist, and librarian.  IT departments pride themselves on building and supporting things that don’t ever break and that are always secure — we love them for that!   So, getting approval for a new, untested, open source project can be dicey.  On the right occasion, it’s really fun AND necessary to play fast and loose and forget about all that other stuff and just build something.  Sometimes, you just gotta have root access, right?

There is a GREAT solution to this quandary.  For the price of a textbook, you can sudo, script, and savor the best that the open source community has to offer.  Or build something without concern for impacts on your campus IT environment.

Linode.com is a VPS (virtual private server) hosting company that provides any Linux distribution your heart desires and they make it ridiculously easy to set up.  It also boasts great tech support, and a pretty impressive community of other hobbyists and hackers who know a lot and are happy to help you when you get stuck.

Lastly, and most importantly for our purposes, they offer what are called ‘StackScripts’ — a customized set of instructions that permits the deployment of a specialized ‘stack’ of servers and applications — such as Linux/Apache/MySQL/PHP (LAMP) + Omeka.  Or Linux + the language R + text mining packages.  Or Linux + Python + geospatial stuff like geonode (geonode.github.com).  Or Python + Django haystack + Solr + jetty …. I’m sure you get the idea.  StackScripts can help you bring up the thing you WANT to have, without your needing to know all that stuff you DON’T WANT to mess with.  Like server administration and configuration.

So here’s the really cool part.  A StackScript is basically a set of commands issued in a shell, all strung together.  You can even build user defined fields into a StackScript (stuff like, “Enter the name of your project here: ____”.  Someone with the necessary know-how can write and provide StackScripts to other folks to use on their own linodes.  We (at THATCamp Lehigh Valley) can compose a StackScript to bring up, say, Omeka.  Once done, others can use it to reduce the time and effort required to bring up their Omeka to as little as an hour.  No kidding!

And here is the other really cool part.  Using github [http://github.com] we can share, adapt, and update StackScripts for all sorts of projects.

In this StackScripted world I imagine, Campus IT is happy because they don’t need to worry about anyone breaking anything.  You’re happy because, if need be, you CAN break stuff.  More importantly, you can spend your time on your awesome new project instead of struggling on Stack Overflow or reading old Linux manuals!  If your project matures, moving it to campus hardware is so easy, you’ll weep with joy.

In summary, over only a couple of hours, I’d like to MAKE something where we:

* talk about Ubuntu as a Linux distro kind to the unfamiliar (5 minutes)

* bring up a new shiny linode (5 minutes)

* back up and fork our shiny linode just in case we break it (10 minutes)

* mess around a little in the Bash shell, particularly with the .bash_history file that is so useful when writing bash scripts (10 minutes)

* write a StackScript that utilizes User Defined Fields for interactive customization during setup.  Perhaps even demonstrate how you can reference other StackScripts in your StackScript, such that you can string them together (60 minutes)

* play with our new creation!  Maybe do it all again!

Any takers?

For anyone who is local or getting in on Thursday, this lecture may be of interest to you:

Andrea A. Lunsford is the Louise Hewlett Nixon Professor of English and Director of the Program in Writing and Rhetoric at Stanford University.  She will present a lecture entitled “Teaching in the Digital Age: What’s Collaboration Got To Do With It? on Thursday, February 28 at 4:10pm in the Scheler Humanities Forum, Linderman Library, Room 200.  This talk is sponsored by a Humanities Center Collaborative Research Grant which was awarded to Suzanne Edwards, Assistant Professor of English.