Categories
DH Project Update Research Projects

Reading Speech: Virginia Woolf, Machine Learning, and the Quotation Mark

[Cross-posted on the my personal blog as well as the Scholars’ Blog. What follows is a slightly more fleshed out version of what I presented this past week at HASTAC 2016 (complete with my memory-inflected transcript of the Q&A). I gave a bit more context for the project at the event than I do here, so it might be helpful to read my past two posts on the project here and here before going forward. This talk continues that conversation.]

This year in the Scholar’s Lab I have been working with Eric on a machine learning project that studies speech in Virginia Woolf’s fiction. I have written elsewhere about the background for the project and initial thoughts towards its implications. For the purposes of this blog post, I will just present a single example to provide context. Consider the famous first line of Mrs. Dalloway:

Mrs Dalloway said, “I will buy the flowers myself.”

Nothing to remark on here, except for the fact that this is not how the sentence actually comes down to us. I have modified it from the original:

Mrs Dalloway said she would buy the flowers herself.

My project concerns moments like these, where Woolf implies the presence of speech without marking it as such with punctuation. I have been working with Eric to lift such moments to the surface using computational methods so that I can study them more closely.

I came to the project by first tagging such moments myself as I read through the text, but I quickly found myself approaching upwards of a hundred instances in a single novel-far too many for me to keep track of in any systematic way. What’s more, the practice made me aware of just how subjective my interpretation could be. Some moments, like this one, parse fairly well as speech. Others complicate distinctions between speech, narrative, and thought and are more difficult to identify. I became interested in the features of such moments. What is it about speech in a text that helps us to recognize it as such, if not for the quotation marks themselves? What could we learn about sound in a text from the ways in which it structures such sound moments?

These interests led me towards a particular kind of machine learning, supervised classification, as an alternate means of discovering similar moments. For those unfamiliar with the concept, an analogy might be helpful. As I am writing this post on a flight to HASTAC and just finished watching a romantic comedy, these are the tools that I will work with. Think about the genre of the romantic comedy. I only know what this genre is by virtue of having seen my fair share of them over the course of my life. Over time I picked up a sense of the features associated with these films: a serendipitous meeting leads to infatuation, things often seem resolved before they really are, and the films often focus on romantic entanglements more than any other details. You might have other features in mind, and not all romantic comedies will conform to this list. That’s fine: no one’s assumptions about genre hold all of the time. But we can reasonably say that, the more romantic comedies I watch, the better my sense of what a romantic comedy is. My chances of being able to watch a movie and successfully identify it as conforming to this genre will improve with further viewing. Over time, I might also be able to develop a sense of how little or how much a film departs from these conventions.

Supervised classification works on a similar principle. By using the proper tools, we can feed a computer program examples of something in order to have it later identify similar objects. For this project, this process means training the computer to recognize and read for speech by giving it examples to work from. By providing examples of speech occurring within quotation marks, we can teach the program when quotation marks are likely to occur. By giving it examples of what I am calling ‘implied speech,’ it can learn how to identify those as well.

For this machine learning project, I analyzed Woolf texts downloaded from Project Gutenberg. Eric and I put together scripts in Python 3 that used a package known as the Natural Language Toolkit] for classifying. All of this work can be found at the project’s GitHub repository.

The project is still ongoing, and we are still working out some difficulties in our Python scripts. But I find the complications of the process to be compelling in their own right. For one, when working in this way we have to tell the computer what features we want it to pay attention to: a computer does not intuitively know how to make sense of the examples that we want to train it on. In the example of romantic comedies, I might say something along the lines of “while watching these films, watch out for the scenes and dialogue that use the word ‘love.'” We break down the larger genre into concrete features that can be pulled out so that the program knows what to watch out for.

To return to Woolf, punctuation marks are an obvious feature of interest: the author suggests that we have shifted into the realm of speech by inserting these grammatical markings. Find a quotation mark-you are likely to be looking at speech. But I am interested in just those moments where we lose those marks, so it helps to develop a sense of how they might work. We can then begin to extrapolate those same features to places where the punctuation marks might be missing. We have developed two models for understanding speech in this way: an external and an internal model. To illustrate, I have taken a single sentence and bolded what the model takes to be meaningful features according to each model. Each represents a different way of thinking about how we recognize something as speech.

External Model for Speech:

“I love walking in London,” said Mrs. Dalloway.  “Really it’s better than walking in the country.”

The external model was our initial attempt to model speech. In it, we take an interest in the narrative context around quotation marks. In any text, we can say that there exist a certain range of keywords that signal a shift into speech: said, recalled, exclaimed, shouted, whispered, etc. Words like these help the narrative attribute speech to a character and are good indicators that speech is taking place. Given a list of words like this, we could reasonably build a sense of the locations around which speech is likely to be happening. So when training the program on this model, we had the classifier first identify locations of quotation marks. Around each quotation mark, the program took note of the diction and parts of speech that occurred within a given distance from the marking. We build up a sense of the context around speech.

Internal Model for Speech:

“I love walking in London,” said Mrs. Dalloway. “Really it’s better than walking in the country.”

The second model we have been working with works in an inverse direction: instead of taking an interest in the surrounding context of speech, an internal model assumes that there are meaningful characteristics within the quotation itself. In this example, we might notice that the shift to the first-person ‘I’ is a notable feature in a text that is otherwise largely written in the third person. This word suggests a shift in register. Each time this model encounters a quotation mark it continues until it finds a second quotation mark. The model then records the diction and parts of speech inside the pair of markings.

Each model suggests a distinct but related understanding for how sound works in the text. When I set out on this project, I had aimed to use the scripts to give me quantifiable evidence for moments of implied speech in Woolf’s work. The final step in this process, after all, is to actually use these models to identify speech: looking at texts they haven’t seen before, the scripts insert a caret marker every time they believe that a quotation mark should occur. But it quickly became apparent that the construction of the algorithms to describe such moments would be at least as interesting as any results that the project could produce. In the course of constructing them, I have had to think about the relationships among sound, text, and narrative in new ways.

The algorithms are each interpretative in the sense that they reflect my own assumptions about my object of study. The models also reflect assumptions about the process of reading, how it takes place, and about how a reader converts graphic markers into representations of sound. In this sense, the process of preparing for and executing text analysis reflects a certain phenomenology of reading as much as it does a methodology of digital study. The scripting itself is an object of inquiry in its own right and reflects my own interpretation of what speech can be. These assumptions are worked and reworked as I craft algorithms and python scripts, all of which are as shot through with humanistic inquiry and interpretive assumptions as any close readings.

For me, such revelations are the real reasons for pursuing digital study: attempting to describe complex humanities concepts computationally helps me to rethink basic assumptions about them that I had taken for granted. In the end, the pursuit of an algorithm to describe textual speech is nothing more or less than the pursuit of deeper and enriched theories of text and speech themselves.

Postscript

I managed to take note of the questions I got when I presented this work at HASTAC, so what follows are paraphrases of my memory of them as well as some brief remarks that roughly reflect what I said in the moment. There may have been one other that I cannot quite recall, but alas such is the fallibility of the human condition.

Q: You distinguish between speech and implied speech, but do you account at all for the other types of speech in Woolf’s novels? What about speech that is remembered speech that happened in earlier timelines not reflected in the present tense of the narrative’s events?

A: I definitely encountered this during my first pass at tagging speech and implied speech in the text by hand. Instead of binaries like quoted speech/implied speech, I found myself wanting to mark for a range of speech types: present, actual; remembered, might not have happened; remembered incorrectly; remembered, implied; etc. I decided that a binary was more feasible for the machine learning problems that I was interested in, but the whole process just reinforced how subjective any reading process is: another reader might mark things differently. If these processes shape the construction of the theories that inform the project, then they necessarily also affect the algorithms themselves as well as the results they can produce. And it quickly becomes apparent that these decisions reflect a kind of phenomenology of reading as much as anything: they illlustrate my understanding of how a complicated set of markers and linguistic phenomenon contribute to our understanding that a passage is speech or not.

Q: Did you encounter any variations in the particular markings that Woolf was using to punctuate speech? Single quotes, etc., and how did you account for them?

A: Yes – the version of Orlando that I am working with used single quotes to notate speech. So I was forced to account for such edge cases. But the question points at two larger issues: one authorial and one bibliographical. As I worked on Woolf I was drawn to the idea of being able to run such a script against a wider corpus. Since the project seemed to impinging on how we also understand psychologized speech, it would be fascinating to be able to search for implied speech in other authors. But, if you are familiar with, say, Joyce, you might remember that he hated quotation marks and used dashes to denote speech. The question is how much can you account for such edge cases, and, if not, the study becomes only one of a single author’s idiosyncrasies (which still has value). But from there the question spirals outwards. At least one of my models (the internal one) relies on quotation marks themselves as boundary markers. The model assumes that quotation marks will come in pairs, and this is not always the case. Sometimes authors, intentionally or accidentally, omit a closing quotation mark. I had to massage the data in at least half a dozen places where there was no quotation mark in the text and where its lack was causing my program to fail entirely. As textual criticism has taught us, punctuation marks are the single most likely things to be modified over time during the process of textual transmission by scribes, typesetters, editors, and authors. So in that sense, I am not doing a study of Woolf’s punctuation so much as a study of Woolf’s punctuation in these particular versions of the texts. One can imagine an exhaustive study that works on all versions of all Woolf’s texts as a study that might approach some semblance of a correct and thorough reading. For this project, however, I elected to take the lesser of two evils that would still allow me to work through the material. I worked with the texts that I had. I take all of this as proof that you have to know your corpus and your own shortcomings in order to responsibly work on the materials – such knowledge helps you to validate your responses, question your results, and reframe your approaches.

Q: You talked a lot about text approaching sound, but what about the other way around – how do things like implied speech get reflected in audiobooks, for example? Is there anything in recordings of Woolf that imply a kind of punctuation that you can hear?

A: I wrote about this extensively in my dissertation, but for here I will just say that I think the textual phenomenon the questioner is referencing occurs on a continuum. Some graphic markings, like pictures, shapes, punctuation marks, do not clearly translate to sound. And the reverse is true: the sounded quality of a recording can only ever be remediated by a print text. There are no perfect analogues between different media forms. Audiobook performers might attempt to convey things like punctuation or implied speech (in the audiobook of *Ulysses*, for example, Jim Norton throws his voice and lowers his volume to suggest free indirect discourse). In the end, I think such moments are playing with an idea of what my dissertation calls audiotextuality, the idea that all texts recordings of texts, to varying degrees, contain both sound and print elements. The two spheres may work in harmony or against each other as a kind of productive friction. The idea is a slippery one, but I think it speaks to moments like the implied punctuation mark that come through in a particularly powerful audiobook recording.

Categories
Announcement DH Project Update Publication Research Projects

In Case You Missed the News

We’re caught up in the craziness of our four week spring term here at W&L, but we wanted to make sure you were caught up on some recent news from our DH community.

Ancient Graffiti Project wins NEH Digital Humanities Start-Up Grant

Heralded as the “epitome of liberal arts,” the Ancient Graffiti Project was recently awarded $75,000 to continue work on their database for textual and figural graffiti. Learn more from the W&L press release or the Atlantic Monthly article. Congrats to Sara Sprenkle, Rebecca Benefiel, and the rest of their team!


Stephen P. McCormick wins Mednick Fellowship from the Virginia Foundation for Independent Colleges

Stephen P. McCormick, Assistant Professor of French, has been awarded the 2016 Menick Fellowship by VFIC for his work on the Huon d’Auvergne project. Learn more about McCormick’s work on one of the last unpublished Franco-Italian Romance Epics from this article or dig into the digital edition yourself.


Joel Blecher publishes chapter on Digital Humanities pedagogy

Joel Blecher, Assistant Professor of Religion, won a DH Incentive Grant in fall of 2014 for incorporating data visualization into a History of Islamic Civilization course. You can now read about this experience in a new title from De Grutyer, The Digital Humanities and Islamic & Middle East Studies. Blecher’s chapter is titled, “Pedagogy and the Digital Humanities: Undergraduate Exploration into the Transmitters of Early Islamic Law” which you can read in print or electronic form through Leyburn Library.


Look forward to reports on our summer activities coming soon. We have teams going to DHSI, ILiADS, the Oberlin Digital Scholarship Conference, and more!

Categories
DH Project Update Undergraduate Fellows

Lasso-ing the Laisses: A Digital Journey Through Annotations, Javascript, and More!

Guest post by Sarah Schaffer ’16

Introduction

Hi, my name is Sarah and I am a senior Business Administration major with a French minor. This past semester of independent study I worked with Professor McCormick on his current Huon d’Auvergne project. You may be wondering: “What is a business major doing here?” but in the spirit of a liberal arts college I’ve taken advantage of the wide variety of classes offered here. My journey with Digital Humanities began Winter 2015 when I registered for Professor McCormick’s class French 341: La Legende Arthurienne, which included a Digital Humanities lab. It was in this class that I became fascinated with TEI and how Digital Humanities have transformed our interactions with various works.

Before Digital Editions

The first step of research was to understand the importance of the work itself, before it becomes a digital edition. Through reading both the books Introduction to Manuscript Studies and On Editing Old French Texts, I began to better understand the work that Professor McCormick was doing. As someone without much background knowledge of historical manuscripts, it had never crossed my mind to consider even half the elements discussed. Each element, such as the writing support it’s written on, the manuscript errors, corrections made, and annotations, add to the way the document is understood and interpreted. Every new edition of the work needs to take into account the editor’s personality and what they chose to include or exclude. Each component plays such a huge role in editing and choosing what to display on the digital edition that is being presented. This makes choosing what to include even more important in the way that the text is being displayed and available for interpretation.

Theory of Digital Editions

As I moved from my readings about the physical documents themselves, Professor McCormick and I discussed Peter Robinson’s article “The Theory of Digital Editions.” Digital editions in their infancy tried to include everything, but quickly found that resources are limited which restricted what could be included. However, what digital editions can do is include a new level of involvement with the document between both the reader and the editor, something that is not possible with a printed document. Unlike a primary document or editorial text, a digital edition allows the reader “to see the text of the document construct itself, layer by layer, from blank page to fully written text” (Robinson 110). The article and discussion with Professor McCormick opened my eyes to the idea that the text-as-document is intimately linked to the text-as-work within the digital edition.

Putting Ideas Together

While learning about digital editions, I researched the different ways other digital editions included annotations, the platforms they used, and the way their works were displayed. I spent a large amount of time looking through various digital editions and searching through DIRT for tools we could use for the final website. We looked into using Hypothes.is as an annotation tool, but it didn’t quite provide the functionality that we were looking for. Eventually after researching and working with various different platforms, we decided to build our own system, using Ruby on Rails. Instead of trying to tailor an already made platform to the project’s needs, creating a new system allowed for the upmost customization.

Prototyping

If I could look at different examples of digital editions and click through them all day, I would, but at some point I needed to come up with some ideas on my own. Based off of various other editions, understanding the history and theory of digital editions, and being aware of what Professor McCormick was looking for I got to work. The best way to begin prototyping is just sitting down with some blank sheets of paper and a pencil and draw out what to design. So, I got to work sketching out several ways the website could be organized. Once I had one or two ideas down, I found more ways to organize the various laisses and show functionality as well. A laisse is best defined as a narrative unit, similar to a stanza but varies in length. Each version of Huon d’Auvergne has a large number of laisses, which makes the organization and display of them even more important. Below you’ll see some basic prototypes created for the display of different versions of Huon d’Auvergne laisses and the annotations.
Screen Shot 2016-04-11 at 9.56.27 AM

Coding

The final step of my project was to begin building the prototypes that I had created. Luckily, I’ve had some experience coding in Professor McCormick’s class before, as well as during some business classes so the task didn’t seem too daunting. I got to work on learning javascript and jQuery through the courses on Codecademy – a website I highly recommend if you’re trying to learn a new coding skill. Once I learned the basics, I did a quick review of HTML and CSS to prep myself for creating a mock-up website. I forgot how intimidating it is to stare at a blank text editor, but once I got started it didn’t seem nearly as daunting.

Gif of frustrated woman staring at laptop

I worked with basic text generated from Lorem Ipsum in order to more easily put my new coding skills to work. After setting up basic structural parts of the website to work with, I added some CSS styling. I then continued with the javascript portion of the website and worked through hiding and revealing the different laisses. I struggled with this part the most because it was such a new skill. Much like learning a foreign language, every new programming language takes time and effort to work through figuring out a solution.

Reflecting on the Semester

Overall, this past semester has been a great learning experience. Beyond the new skills that I learned, this opportunity allowed me to take my liberal arts education beyond the classroom and apply it to a really unique project It was an honor to work with Professor McCormick’s team and be a part of such an incredible project.

Work Cited:

Robinson, Peter. “Towards a Theory of Digital Editions.” The European Society for Textual Scholarship 10 (2013): 105-31. Web.

Categories
DH Undergraduate Fellows

Construction, Digitization, and Future Plans

A lot has happened since my last blog post. All of it progress, though some of it slow.

So far I have a developed a general appearance for my website, a semi-completed home page, a completely digitized diary, and a digitized photo album.

Before experimenting with the CSS, I drew sketches of how I wanted certain pages to look. In general, I wanted the website to follow a minimalist design that was also functional. I wanted the homepage to have a floating navigation bar with the title underneath in bold letters, a banner image, a short description of the project, and then boxes lining the bottom of the page which would take you to central parts of the website. The idea of the boxes was partially inspired by the Prism website developed by the Praxis team at the University of Virginia’s Scholars’ Lab.

Currently, I am using a simple black and white color scheme with shades of gray and navy. I think this structure sets up the color scheme for the photo albums and ensures viewability. Yet, as I continued to edit, I realized that while I got my colors right, other pieces of the puzzle were not quite falling into place. The specific layout I wanted for my homepage hindered the user experience of the rest of the website. Part of this is because I want a banner image on the top of the page that gives the user a sample of the collection. But when navigating the rest of the website, this image often gets in the way.

We fixed this problem by creating a separate HTML page that would house the homepage while the rest of the website would work with the same Omeka appearance, sans banner. Here is what the top of the page looks like so far.

 

Screen Shot 2016-03-03 at 3.21.48 AM

Our next goal is to add an efficient navigation bar that lines the top of the page throughout the entire website.

Regarding the collection materials, I have scanned all 50 pages of the mother’s diary and cropped the photos. I have also scanned, straightened, and cropped the first photo album which consists of 96 black and white images.

The next step is to begin uploading the materials as items to Omeka. The individual photos will fall into their own collection and the same goes for the diary pages. However, thanks to a plugin called Scripto, the website will also give users the option to interact by transcribing the pages.

Moving forward, we plan to edit the webpage’s layout for the diary pages because the default Scripto structure is confusing. The ultimate goal is to produce a set-up similar to that of DIY History.
Furthermore, I am halfway done scanning the photos in the second album and should be able to upload those photos very soon.

Categories
Conference DH Event off campus

Apps, Maps, & Models: A New View

[Crossposted on my personal blog.]

Last Monday several of us here at WLUDH traveled down to Duke University for their symposium on Apps, Maps & Models: Digital Pedagogy in Art History, Archaeology & Visual Studies. I found the trip to be enlightening and invigorating. If you are interested in the event, you can find videos of the talks here and here as well as a storify of the Twitter action here. That the event was so well documented is a testimony to how well organized it was by the Wired! Lab.

Many speakers at the event considered how the tools they were using might relate to more “traditional” modes for carrying out their research. They considered and responded to tough questions with and about their work. Are digital methods for tracing the topography of a surface, for example, fundamentally different in kind from analog means of doing so? If so, are they meant to displace those old tools? Why should we spend the time to learn the new technologies? A related question that comes up at almost every digital humanities presentation (though not at any of these): can digital humanities methods show us anything that we do not already know?

Such questions can be particularly troubling when we are investing such time and energy on the work they directly critique, but we nonetheless need to have answers for them that demonstrate the value of digital humanities work, in and out of the classroom. Numerous well-known scholars have offered justifications of digital work in a variety of venues, and, to my mind, the symposium offered many answers of its own, in part by showcasing amazing work that spanned a variety of fields related to preservation, public humanities, and academic scholarship. Presenters were using digital technology to rebuild the past, using digital modeling to piece together the fragments of a ruined church that have since been incorporated into other structures. They were using these tools to engage the present, to draw the attention of museum patrons to overlooked artifacts. The work on display at the symposium struck me, at its core, as engaging with questions and values that cut across disciplines, digital or otherwise.

Most compelling to me, the symposium drew attention to how the tools we use to examine the objects of our study change our relationship to them. The presenters acknowledged that such an idea does hold dangers – after all, we want museum-goers to consider the objects in a collection, not just spend time perusing an iPad application meant to enrich them. But just as new tools offer new complications, changes in medium also offer changes in perspective. As was illustrated repeatedly at the symposium, drone photography, for all its deeply problematic political and personal valences, can offer you a new way of seeing the world, a new way of looking that is more comprehensive than the one we see from the ground. Even as we hold new methodologies and tools up to critique we can still consider how they might cause us to consider an object, a project, or a classroom differently.

Seeing from a different angle allows us to ask new questions and re-evaluate old ones, an idea that speaks directly to my experience at the symposium. I work at the intersections of digital humanities, literary studies, and sound studies. So my participation in the symposium was as something of an outsider, someone ready to learn about an adjacent and overlapping field but, ultimately, not a home discipline. Thinking through my work from an outsider perspective made me want to ask many questions of my own work. The presenters here were deeply engaged in preserving and increasing access to the cultural record. How might I do the same through text analysis or through my work with audio artifacts? What questions and goals are common to all academic disciplines? How might I more thoroughly engage students in public humanities work?

Obviously, the event left me with more questions than answers, but I think that is ultimately the sign of a successful symposium. I would encourage you to check out the videos of the conference, as this short note is necessarily reductive of such a productive event. The talks will offer you new thoughts on old questions and new ways of thinking about digital scholarship no matter your discipline.

 

 

Categories
DH Project Update Tools

Embedding COinS Metadata on a Page Using the Zotero API

[Cross-posted on my personal blog]

This year I am working with Mackenzie, Steve McCormick, and his students on the Huon d’Auvergne project, a digital edition of a Franco-Italian romance epic. Last term we finished TEI-encoding of two of the manuscripts and put them online, and there is still much left to do. Making the digital editions of each manuscript online is a valuable scholarly endeavor in its own right, but we’ve also been spending a lot of time considering other ways in which we can enrich this scholarly production using the digital environment.

All of which brings me to the bibliography for our site. At first, our bibliography page was just a transcription of a text file that Steve would send along with regular updates. This collection of materials is great to have in its own right, but a better solution would be to leverage the many digital humanities approaches to citation management to produce something a bit more dynamic.

Steve already had everything in a Zotero, so my first step was to integrate the site’s bibliography with the Zotero collection that Steve was using to populate the list. I found a python 2 library called zot_bib_web that could do all this quite nicely with a bit of modification. Now, by running the script from my computer, the site’s bibliography will automatically pull in an updated Zotero collection for the project. Not only is it now easier to update our site (no more copying and pasting from a word document), but now others can contribute new resources to the same bibliography on Zotero by requesting to join the group and uploading citations. The project’s bibliography can continue to grow beyond us, and we will capture these additions as well.

Mackenzie suggested that we take things a bit further by including COiNS metadata in the bibliography so that someone coming to our bibliography could export our information into the citation manager of their choosing. Zotero’s API can also do this, and I used a piece of the pyzotero Python library to do so. The first step was to add this piece to the zot_bib_web code:

zot = zotero.Zotero(library_id, library_type, api_key)
coins = zot.collection_items(collection_id, content='coins')
coin_strings = [str(coin) for coin in coins]
for coin in coin_strings:

fullhtml += coin

Now, before the program outputs html for the bibliography, it goes out to the Zotero API and gets COinS metadata for all the citations, converts them into a format that will work for the embedding, and then attaches each returned span to the HTML for the bibliography.

Now that I had the data that I needed, I wanted to make it work a bit more cleanly in our workflow. Initially, the program returned each bibliographic entry in its own page and meant for the whole bibliography to also be a stand-alone page on the website. I got rid of all that and, instead, wanted to embed them within the website as I already had it. I have the python program exporting the bibliography and COinS data into a small HTML file that I then attach to a <div id="includedContent"> inserted in the bibliography page. I use some jQuery to do so:

<script type="text/javascript">

$(function(){
$("#includedContent").load("/zotero-bib.html");
});
</script>

Instead of distributing content across several different pages, I mark a placeholder area on the main site where all the bibliographic data and metadata will be dumped. All of the relevant data gets saved in a file ‘zot-bib.html’ that gets automatically included inside the shell of the bibliography.html page. From there, I just modified the style so that it would fit into the aesthetic of the site.

Now anyone going to our bibliography page with a Zotero extension will see this in the right of the address bar:

Screen Shot 2016-02-08 at 1.07.04 PM

Clicking on the folder icon will bring up the Zotero interface for downloading any of the items in our collection.

Screen Shot 2016-02-08 at 1.13.09 PM

And to update this information we only need to run a single python script from the terminal to re-generate everything.

The code is not live on the Huon site just yet, but you can download and manipulate these pieces from an example file I uploaded to the Huon GitHub repository. You’ll probably want to start by installing zot_bib_web first to familiarize yourself with the configuration, and you’ll have a few settings to update before it will work for you: the library id, library type, api key, and collection ID will all need to be updated for your particular case, and the jQuery excerpt above will need to point to wherever you output the bibliography file.

These steps have strengthened the way in which we handle bibliographic metadata so that it can be more useful for everyone, and we were really only able to do it because of the many great open source libraries that allow others to build on them. It’s a great thing – not having to reinvent the wheel.

Categories
DH Event on campus Speaker Series

Day of DH @ Winter Academy 2015 featuring Amanda French

It’s that time again! This year’s Day of DH will be December 16, 2015. Don’t forget to register. All events will be held in Hillel 101.

9:15-10:15am How Did They Do That?: Team Teaching and Telling Stories

Journalism Professor Toni Locy and Librarian Jeff Barry will discuss their approach in teaching a course on multimedia storytelling design that attracted journalism, politics, history, English and mass communications majors who wanted to learn how to use HTML, CSS, and JavaScript to tell compelling, interactive stories that are on the cutting edge of news and communications today. Students utilized basic web design and programming skills to envision and execute online narratives through the interplay of words, images, sound and video that they gathered in reporting the story of W&L’s decision to move juniors back on campus.
11am-12pm DH Medley: Entry-Level Digital Pedagogy Panel
Were you inspired by Quinn Warnick’s charge to try “one new thing” during Fall Academy? A panel of three faculty members will share their experiences adding a taste of DH to their courses. Mikki Brock, Assistant Professor of History, will discuss her use of TimelineJS to inform a traditional writing assignment. Caleb Dance, Assistant Professor of Classics, will discuss the annotation tool “nb” and its success in his Latin prose class. Stephanie Stillo, Mellon Junior Faculty Fellow, will discuss her incorporation of a UVa graduate student to introduce DH to a first-year seminar.
12:15-1:45pm Annotating and Writing about Online Text, Images, Audio, and Video: Introduction to Hypothes.is and Scalar led by Amanda French
This workshop will be led by Amanda French, Director of Digital Research Services at Virginia Tech University Libraries.
amanda_jacket_crop-300x300
The web is full of content that scholars would like to comment on, write about, and incorporate into multimedia-rich online essays. Rather than trying to describe what happens in a particular video with words only in a print-only essay, wouldn’t it be better to incorporate comments into an existing film clip, then embed that film clip into a longer essay where it can be compared to other clips, audio snippets, images, and even scholarly articles? Hypothesis is a free annotation tool that lets you highlight and comment on any web page: your annotations and highlights can be private to just yourself, shared to a select group, or entirely public. Scalar is a free multimedia authoring tool that allows you easily to create media-rich online books that can themselves have Hypothes.is annotations enabled by default. Both tools have been created by and for humanities scholars who are particularly interested in challenging subordination, hierarchy, and linearity on the web by enabling interpretive commentary on existing web content. This workshop will show some examples of Hypothes.is and Scalar uses in teaching and research, will define terms and demonstrate key features of both tools, and will give you hands-on in-class exercises that will let you practice working with both tools to create useful and interesting digital scholarship.

Before the workshop, if you can, please create an account for Hypothes.is at http://hypothes.is and install the bookmarklet in your browser of choice, then create an create an account for Scalar at http://scalar.usc.edu. Please do bring a laptop (NOT a tablet).

Categories
DH Pedagogy Research Projects

Reflections on a Year of DH Mentoring

[Cross-posted on the Scholars’ Lab blog]

This year I am working with Eric Rochester in the Scholars’ Lab on a fellowship project that has me learning natural language processing (NLP), the application of computational methods to human languages. We’re adapting these techniques to study quotation marks in the novels of Virginia Woolf (read more about the project here). We actually started several months before this academic year began, and, as we close out another semester, I have been spending time thinking about just what has made it such an effective learning experience for me. I already had a technical background from my time in the Scholars’ Lab at the beginning of the process, but I had no experience with Python or NLP. Now I feel most comfortable with the former of any other programming language and familiar enough with the latter to experiment with it in my own work.

The general mode of proceeding has been this: depending on schedules and deadlines, we meet once or twice every two weeks. Between our meetings I would work as far and as much as I could, and the sessions would offer a space for Eric and me to talk about what I had done. The following are a handful of things we have done that, I think, have helped to create such an effective environment for learning new technical skills. Though they are particular to this study, I think they can be usefully extrapolated to apply to many other project-based courses of study in digital humanities. They are primarily written from the perspective of a student but with an eye to how and why the methods Eric used proved so effective for me.

Let the Wheel Be Reinvented Before Sharing Shortcuts

I came to Eric with a very small program adapted from Matt Jockers’s book on Text Analysis with R for Students of Literature that did little beyond count quotation marks and give some basic statistics. I was learning as I built the thing, so I was unaware that I was reinventing the wheel in many cases, rebuilding many protocols for dealing with commonly recognized problems that come from working with natural language. After working on my program and my approach to a degree of satisfaction, Eric pulled back the curtain to reveal that a commonly used python module, the Natural Language ToolKit (NLTK), could address many of my issues and more. NLTK came as something of a revelation, and working inductively in this way gave me a great sense of the underlying problems the tools could address. By inventing my own way to read in a text, clean it to make its text uniformly readable by the computer, and breaking the whole piece into a series of words that could be analyzed, I understood the magic behind a couple lines of NLTK code that could do all that for me. The experience also helped me to recognize ways in which we would have to adapt NLTK for our own purposes as I worked through the book.

Have a Plan, but Be Flexible

After discussing NLTK and how it offered an easier way of doing the things that I wanted, Eric had me systematically work through the NLTK book for a few months. Our meetings took on the character of an independent study: the book set the syllabus, and I went through the first seven chapters at my own pace. Working from a book gave our meetings structure, but we were careful not to hew too closely to the material. Not all chapters were relevant to the project, and we cut sections of the book accordingly. We shaped the course of study to the intellectual questions rather than the other way around.

Move from Theory to Practice / Textbook to Project

As I worked through the book, I was able to recognize certain sections that felt most relevant to the Woolf work. Once I felt as though I had reached a critical mass, we switched from the book to the project itself and started working. I tend to learn from doing best, so the shift from theory to execution was a natural one. The quick and satisfying transition helped the work to feel productive right away: I was applying my new skills as I was still learning to feel comfortable with them. Where the initial months had more the feel of a traditional student-teacher interaction, the project-based approach we took up at this point felt more like a real and true collaboration. Eric and I would develop to-do items together, we would work alongside each other, and we would talk over the project together.

Document Everything

Between our meetings I would work as far and as much as I could, carefully noting places at which I encountered problems. In some cases, these were conceptual problems that needed clarifying, and these larger questions frequently found their way into separate notes. But my questions were frequently about what a particular line of code, a particular command or function, might be doing. In that case, I made comments directly in the code describing my confusion. I quickly found that these notes were as much for me as for Eric–I needed to get back in the frame of mind that led to the confusion in the first place, and copious notes helped remind me what the problem was. These notes offered a point of departure for our meetings: we always had a place to start, and we did so based on the work that I had done.

Communicate in as Many Ways as Possible

We met in person as much as possible, but we also used a variety of other platforms to keep things moving. Eric and I had all of our code on GitHub so that we could share everything that we had each been working on and discuss things from a distance if necessary. Email, obviously, can do a lot, but I found the chat capabilities of the Scholars’ Lab’s IRC channel to be far better for this sort of work. If I hit a particular snag that would only require a couple minutes for Eric to answer, we could quickly work things out through a web chat. With Skype and Google Hangouts we could even share the code on the other person’s computer even from hundreds of miles away. All of these things meant that we could keep working around whatever life events happened to call us away.

Recognize Spinning Wheels

These multiple avenues of communication are especially important when teaching technical skills. Not all questions or problems are the same: students can work through some on their own, but others can take them days to troubleshoot. Some amount of frustration is a necessary part of learning, and I do think it’s necessary that students learn to confront technical problems on their own. But not all frustration is pedagogically productive. There comes a point when you have tried a dozen potential solutions and you feel as though you have hit a wall. An extra set of eyes can (and should) help. Eric and I talked constantly about how to recognize when it was time for me to ask for help, and low-impact channels of communication like IRC could allow him to give me quick fixes to what, to me at least, seemed like impossible problems. Software development is a collaborative process, and asking for help is an important skill for humanists to develop.

In-person Meetings Can Take Many Forms

When we met, Eric and I did a lot of different things. First, we would talk through my questions from the previous week. If I felt a particular section of code was clunky or poorly done, he would talk and walk me through rewriting the same piece in a more elegant form. We would often pair program, where Eric would write code while I watched, carefully stopping him each time I had a question about something he was doing. And we often took time to reflect on where the collaboration was going – what my end goal was as well as what my tasks before the next meeting would be. Any project has many pieces that could be dealt with at any time, and Eric was careful to give me solo tasks that he felt I could handle on my own, reserving more difficult tasks for times in which we would be able to work together. All of this is to say that any single hour we spent together was very different from the last. We constantly reinvented what the meetings looked like, which kept them fresh and pedagogically effective.

This is my best attempt to recreate my experience of working in such a close mentoring relationship with Eric. Obviously, the collaboration relies on an extremely low student-to-teacher ratio: I can imagine this same approach working very well for a handful of students, but this work required a lot of individual attention that would be hard to sustain for larger classes. One idea for scaling the process up might be to divide a course into groups, being training one, and then have students later in the process begin to mentor those who are just beginning. Doing so would preserve what I see as the main advantage of this approach: it helps to collapse the hierarchy between student and teacher and engage both in a common project. Learning takes place, but it does so in the context of common effort. I’d have to think more about how this mentorship model could be adapted to fit different scenarios. The work with Eric is ongoing, but it’s already been one of the most valuable learning experiences I have had.

Categories
DH Event on campus

Digital Ruckus on October 22

DIGITAL RUCKUS
We’re throwing a party to announce upcoming DH courses for Winter 2016. Come see what the Digital Humanities are all about at this interactive event in the IQ Center. We’ll have pizza, video installations of student work, and a digital scavenger hunt. All are welcome – bring your friends!

October 22, 2015
7pm
IQ Center

RSVP on Facebook // Printable poster

Categories
DH Incentive Grants

Announcing Incentive Grant Recipients 2015-2016

We’re excited to announce the DH Mellon Incentive Grant recipients for the 2015-2016 academic year.

Claudette Artwick, Associate Professor of Journalism & Mass Communications
Student teams in JOUR 232: Communication Research Methods will design and conduct content analysis projects to explore the portrayal of social groups and issues in media content. Students will use digital tools, such as quickQuote and Twxplorer, to research and analyze larger-scale data sets as well as present them in an interactive, multimedia format.

Michelle Brock, Assistant Professor of History
HIST 229: The Age of the Witch-hunts will culminate in a Digital Humanities project that asks the students to imagine, write, present, and play a “Choose Your Own Witch-trial” game, modeled after the “choose your own adventure” books.

Laura Brodie, Visiting Associate Professor of English
ENGL 203: Fiction Writing will feature experimentation with new narrative techniques will encourage students to integrate digital media into the process of creative writing.

Owen Collins, Associate Professor of Theater
THTR 238: 3d Printing and Desktop Manufacturing for the Theater will feature a large scale group project in which the students will work collaboratively on creating a large scale puppet for a given play.

Holly Pickett, Associate Professor of English
ENGL 380: The (Digital) Crux in King Lear will explore Shakespeare’s King Lear from a variety of angles: its textual history and variants, sources, performance history, and legacy in film and literature. The goal for this course will be for students to explore new digital methodologies for literary analysis using tools such as Juxta Commons and Voyant.

Summer Renault-Steele, Visiting Instructor of Writing
The overall learning objective of WRIT 100: The Philosophy of New Media is to illuminate and connect up philosophical inquiry rooted in the Frankfurt School to present-day student experiences of digital culture. This course will feature “philosophy labs” in which students will apply the philosophy they read to their own reception—and production—of short digital media experiences.

This program is made possible by a grant from the Andrew W. Mellon Foundation.