Article

Linked Open Data & Literary Networks

We had the first meeting today of what we’re calling our Linked Open Data Working Group. In addition to myself, group members are Mackenzie Brooks (Digital Humanities Librarian), Jeff Knudson (Senior Technology Architect/ITS), and Brandon Walsh (Mellon Digital Humanities Fellow).

What is it we want to accomplish through this group?

  • Develop a better understanding of Linked Open Data (LOD) and how it might apply to projects at W&L.

We want to think about LOD in the context of our specific DH projects in order to avoid talking about it in the abstract. But we also want to make sure that we clearly identify what we want to accomplish with those projects instead of having a solution (e.g., LOD) that is looking for a problem to solve. In other words, we’re going to develop the vision for the project and then work backwards.

We have several potential projects but the easiest to get started on is literary networks. This project evolved out of archival research relating to the Shenandoah literary magazine published by W&L. While Shenandoah is partially indexed in MLA, a full index of Shenandoah has never been produced. (Also, the contents are not in JSTOR.)  A student worker in the library has compiled an index as part of her job in Special Collections and Archives. Our DH Librarian (previously our Metadata Librarian) identified the necessary fields and created the spreadsheet for the data entry. The Shenandoah index has over 6,400 entries.

Our first task in this project doesn’t actually involve LOD: creating a web-based index to Shenandoah. But we want to keep LOD principles in mind as we develop the index. The Shenandoah data set provides research material that goes far beyond merely an index to a journal.

While the research agenda of the literary networks project is the topic of a future post, the essence is that I want to examine the relationships and connections among authors and editors.

 

Top-level functionality

Here are primary features involved in a LOD approach to this data set. Each feature is a different stage, or layer, of the project. A use case scenario describes functionality enabled by each stage.

  • a web-based index to Shenandoah

Use case: Queries based on editor. From these queries we can form network graphs based on relationships among authors and editors and issues.

  • expose the index/relationship data as LOD

Use case: Exposing this data set as a LOD triple store (with possibilities of generating query results in json & csv) allows for the data to be analyzed in a variety of tools such as Palladio, R, Gephi. Plus, it provides the ability for other projects to integrate this data.

  • the web index incorporates additional data about authors

Use case: the web interface shows brief biographical information and publishing history about each author. Instead of gathering this data manually and entering it directly into the data set, we want to explore creating a process that connects external information about these authors with this data by consuming LOD.

  • expanding the Shenandoah data set by including relationship information identified by archival research

Use case: literary networks are influenced by friendships and social contacts. Publishing decisions are often made by brokers (e.g., Ezra Pound), whose influence is not formally represented in the index data. There’s a complex challenge in figuring out how to represent this information.

  • expanding the data set with data of other literary journals in order to create a broader data set of authors publishing in the mid-century

Use case: While the data set starts with one specific literary journal (Shenandoah), it’s the connections among authors and editors publishing in a larger set of journals during the same time period that is more interesting. Authors do not simply write for one publication. Ultimately, the literary networks project will create a data set of authors (and editors) who published in mid-century literary journals.

From originating with the Shenandoah data set we gain experience with the process of utilizing LOD. What we learn through this initiative can be applied to other projects, particularly those with biographical data.

Process of the LOD working group

As a group we will meet once a month. We will use a Slack channel in the W&L DHAT team for communication.

Article

DH as a trojan horse for information literacy

The digital humanities (DH) represent an academic library’s greatest opportunity for strengthening its role in the curriculum and research. DH provides a frame for understanding the creative process of scholarship.

The methods and tools within DH are not unique to disciplines within the humanities. The core activities of DH reflect the fundamental hallmarks of information literacy as expressed in the ACRL Framework for Information Literacy. DH does not exist without information literacy. Yet, a separation exists within the profession of librarianship between DH and information literacy. Our academic libraries are organized so that information literacy is the domain of subject liaisons/instructional librarians and DH emerges from R&D-type efforts. In most libraries these are entirely separate departments. In some universities DH is entirely separated from the library, even when a DH center is physically located within the library building.

DH and information literacy are on a collision path fighting for resources. Yet, DH can be a vehicle for strengthening the reach of information literacy in the curriculum. Opportunities exist for collaborative initiatives bringing the two together rather than siloed within organizational boundaries. Librarians must advocate for integrating these practices instead of competing for resources. Here are some steps for moving forward:

First, increase the dialogue between instruction librarians and DH specialists in order to move beyond the barrier of the term DH and recognize its essence as applicable to all disciplines.

Second, redefine the role of the subject liaison/specialist to incorporate a range of digital practices so that all academic librarians are digital scholarship librarians.

Third, take action and demonstrate through example by jumping in with both feet to figure out what works at a particular institution.

DH has the power to enhance an information literacy program. Within the confluence of DH and information literacy, a university can find the capacity to sustain digital scholarship.

Article

First-year writing courses & DH

We’re half-a-year into our 4-year Mellon DH grant. On my way back from DLF in Vancouver at the end of October, I got stranded in the Chicago airport for most of the day. Those “opportunities” provide plenty of time to think. For a couple of years W&L has been issuing an open call to faculty to submit proposals for incentive grants in DH. As I was sitting in the airport, I started to reflect on how we could take a more systematic approach to ensuring that the grant money contributed to structural changes in the curriculum. In other words, what is it that we’re trying to incentivize?

One of our goals is to introduce more first-year students to DH.  Students encountering digital methods early in their academic careers are better equipped for handling DH assignments and projects appropriate for upper level courses.  Our students are challenged to grasp the implications of a world mediated through technology. The digital environment is not in opposition to the critical thinking nurtured through the processes of close reading and composition. Rather, through software we find tools that are suitable for enhancing our understanding of the world around us and to present new forms of expression.

Our students have the opportunity in their lifetimes to creatively define how technology impacts not only their future but also that of succeeding generations.

As their careers progress into the mid-century, our graduates’ entrepreneurial instincts and leadership will identify solutions that can only be met through their critical understanding of digital information and technology.

The foundations for that digital mindset of addressing humanistic concerns starts in the first-year of college.

Our initiative is to collaborate with faculty teaching the first-year writing courses and seminars to craft an introductory set of DH assignments that relates the core concepts of these courses with analytical and creative methods within DH that establishes a baseline of the critical understanding needed for thriving in a digital society.

What type of DH assignments are suitable for first-year writing courses? We’re not yet sure. It’s not appropriate for librarians and technologists to say, “This is what you should do.” Over the course of the coming year we want to define that with the faculty teaching those courses. We’re going to do that through a series of conversations. Plus, we’ll seek the advice of faculty at other institutions that have explored the concepts and are further along that path.

Article

Electronic Literature, Digital Humanities, & Creative Writing

This morning we met with a professor teaching Fiction Writing who wanted to incorporate a DH assignment into the course that required the students to tell a story through a new technology of their choice.

The students will start by completing a 3-page writing assignment with pen and paper. Then they will be asked to translate that story into a digital medium. The keyword here is translate. Is chopping a thousand words of prose into 50 tweets a translation of prose into digital medium? I would say not. As with any translation, how does the language of the digital medium impact the text? How does the language of the digital medium provide different capabilities (or affordances) that inspires new forms of creativity?

As an assignment, students will have to grapple with the technological platform (the language) that they have chosen for their translation. Students must learn that every platform choice comes with limitations and constraints that have significant impacts on determining the structure of their narrative. While these restrictions appear to be determined by the technology, students should grasp that the limitations are the functions of the underlying software. The code behind the platform reflects the dictates of software developers.

Many examples of electronic literature try to work within or around those constraints. That likely is a simple reflection of the coding limitations of the authors.

I would prefer that students start their translation process not with the choice of platform. But start with creativity. And again with pen and paper. Approach the digital with a blank slate and not with the limitations of an imposed piece of software. Sketch out in pencil what would be ways of representing this narrative if the choice of digital medium was wide open. Have the students describe the capabilities that the software would provide to tell the story. Have the students create a storyboard, a flow of the narrative, with the technologies of their imagination. These tools may not yet even exist. But if they can be imagined, then the algorithms  can be created.

What’s important is not that the students learn to tell a story in prezi or twitter, but that they learn that digital media is software that has capabilities and limitations defined by its creator. The process of software development is a creative act. While students in a fiction writing course will not become coders overnight, this exercise could inspire them to see the linkage between the creative process and the process of developing the tools that we all use to tell the stories in digital media.

Article

Remarks to VICULA on DH

The following is a draft of remarks I gave to a meeting of VICULA (Virginia Independent College and University Library Association) today at its meeting at Washington and Lee. I don’t read my talks directly from a script, so what I actually said varies but this represents the heart of it.

I’m going to give an overview of our digital humanities and some of the issues we’re facing. And my colleagues are going to go into more specifics about the aspects that they are working on.

First, about that term digital humanities: DH. It’s a problematic term in an undergraduate college. It’s very hard to define and is more often associated with graduate education and faculty research. I do like this definition: DH is a set of “convergent practices that explore a universe in which print is no longer the primary medium in which knowledge is produced and disseminated” (Burdick et al. 2012, 122) [pdf] But what does that really mean in practice? What does it mean for undergraduate teaching and learning?

Many liberal arts colleges have adopted different terms, such as the digital liberal arts or digital studies. DH is more than the humanities. These techniques can apply to many disciplines. There’s really little distinction between DH and digital scholarship. My advice is not to focus too much on trying to define the term because that can lead to a lot of non-productive conversations as you pull in people from different disciplines.

At W&L we have a very practical reason for using DH: the dean of our college. She likes the term DH. She started the conversation here about DH about 3 years ago and she is the champion for our DH initiatives. So, here at W&L the term DH has developed a certain brand, a recognition, that works here. I encourage you to find the term that works at your institution. But spend more time talking about what you do and not about a definition.

We do have a lot of momentum going about DH. If you’re interested in the background, a group of us wrote a case study. I’m going to talk about where we are now. Collaboration is the key to everything we’re doing. And we’re very fortunate in having strong leadership, not only from our dean but also our faculty. Again, the case study describes how our DH activities are organized.

As we were writing that case study, we started examining what many other liberal arts colleges were doing with DH. And we noticed that many of the colleges had large grants from the Mellon Foundation. And we started wondering: how can we get some of that funding? So one day I picked up the phone and called the grants officer in our development office. We are very fortunate in that we have a wonderful grants officer. And he told me the process for applying for a Mellon grant.

I want to talk about this process a  bit since some of you might be interested in pursuing this funding source. The Mellon Foundation has an unusual process. It does not accept unsolicited applications but there is a process. Even though Mellon has a reputation for being somewhat exclusive, there are clear indicators that Mellon is expanding the range of institutions that they fund. And it’s important to remember that Mellon is a humanities foundation. The process is simple. Your provost or president simply sends a brief email describing the concept to the appropriate program officer at Mellon.

We were shocked that Mellon replied that day, within hours, that they were interested and wanted to see a draft proposal. We then had a conference call with the program officer: on the call was our provost, the two faculty most involved in DH, myself, and our grants officer. We got clarification as to what Mellon liked and did not like. They are very clear in what they do and do not want to see. So we pulled together a draft, about 5 pages, and submitted that. We were even more surprised that Mellon responded again the same day saying that they would fund the project. Of course, that was a tentative approval. It still had to be approved by the board of Mellon.

I encourage you not to be shy about approaching Mellon but the contact, at least for the liberal arts program, should come from the college’s senior administration. Many people are aware that research libraries often get significant Mellon funding for digital library and digital scholarship initiatives. But that is through a separate process, a different program officer at Mellon. So it’s important to make sure what division of Mellon you are targeting. And Mellon is also very interested in collaborative endeavors and multi-institutions initiatives.

If your institution has not received Mellon funding before, you probably will want to start with a small concept, perhaps a planning grant. In our initial contact, we did not specify a dollar amount. Mellon will tell you the amount that they will fund.

So what are we doing? Our grant proposal is titled DH Studio: a pedagogical innovation. We wanted to anchor our initiative around the curriculum, particularly a series of one credit courses in DH that serve as labs for humanities courses. Mackenzie Brooks will speak more about the DH Studio courses.

Our grant is divided into multiple areas: staffing for the library to support DH studio, incentive grants to faculty, summer research grants, professional development, a speaker series, student workers, and funding to send students to conferences. The about page of our DH website has more details on these initiatives.

So everything looks really great. We have the senior administration fully behind DH, great leadership from the faculty, very positive buzz among the faculty, the library is excited about DH, and we have a large grant. What could go wrong? One very important thing: lack of student interest.

We thought students would be excited to learn this stuff. But our students are very practical, very career oriented. They could not make the connection between DH and their careers. Part of the problem is that term DH. It means nothing to students.

And building interest among students is a major focus of our initiative this year. [At this point in the talk, I spoke about some our curricular activites. A focus was on the courses we’re teaching and the enrollment issues we encountered. I’m going to be doing an upcoming talk at DLF on the specifics of that issue. I’ll post those comments when they’re available.]

Article

Digital history course project

In the second class of the digital history course. We focused on working with data, which is the largest part of the course project.

We started by reviewing two readings involving our case study of the Legacies of British Slave-ownership. Appendices 1 & 2 of the book about that project provide insights into prosopography and database development. As we reviewed those readings, I explained terms that were not yet familiar to the students. And we explored concepts around collecting and organization data about individuals. The course project page provides further background on the project and a few sample maps.

 

Article

Creativity and Code

The third class of multimedia storytelling design is focused on what I call creativity and code. Continuing the focus on Snow Fall, the class reading for today is How We Made Snow Fall. That last link is a really good article, worth reading closely.

Creative thoughts from the how Snow Fall is made article:

  • Making a single story out of the digital assets….”to weave things together so that text, video, photography and graphics could all be consumed in a way that was similar to reading–a different kind of reading.” Talk about the origin of the word text…Latin…to weave (see Latin dictonary)
  • The design process: initial prototyping, collaboration, integration of graphics and video into “the narrative experience”
  • “a lot of trial and error and experimenting”
  • “design revisions and tweaks”
  • filmmaking techniques, but reading centric
  • “We focused on the pacing, narrative tension, and story arc–all while ensuring that each element gave the user a different experience of the story.”
  • moving images…pauses at “critical moments in the text”
  • “Having a tight edit that slowly built the tension of the narrative was the overall goal.”
  • Color palettes
  • Biggest challenge: “managing the path we wanted the reader to follow”

 

Much of this class period will be getting students to do HTML hands-on. We’ve talked a lot about HTML in the first class and looked at a lot of HTML code, but I want to get a sense as to how far the students are coming along with actually doing something with HTML. I suspect not far.

Some thoughts on topics to cover in today’s class:

  • Have the students open up the W3schools site. A good reference source for tags. But, also, for those new to HTML: the try it yourself  online editor is an extremely simple way for seeing how tags work.
  • Tell students about lynda.com. Not required for this class but a great resource for learning on your own. In future versions of this course, I might think about requiring lynda.com access rather than a book.
  • What is a plain text file? Contrast with binary files using machine code and with WYSIWYG document editors. What’s a text editor? A code editor? Try opening a binary file in a text editor.
  • File extensions. Nice to show those extensions in Mac OS X (Finder>Preferences>Advanced>Show all filename extensions.

I had a student email me with a problem in getting an HTML document display in the browser as a Web page. Instead, the page simply showed the HTML code. The problem was that the student followed the instructions in the Duckett book and used TextEdit on the Mac to create the page. TextEdit, being a rather confusing software program for writing HTML, saved the document as RTF (even though the student had correctly added the .html extension). There’s a non-intuitive option within TextEdit for saving as plain text.

For this class I’m recommending the use of Atom, which is already installed on the iMacs in the journalism lab. But make sure that students know how to install this on their own laptops.

  • Do students understand that a website is a directory (i.e., folder) on a server?
  • Create a basic web page in HTML. Perhaps by just copying over what they had done in the w3schools try it editor.
  • Save the page as index.html…as a way of introducing the importance of index.html as a filename in web site directories. Stress, though, that not any directory can serve web pages. You need a directory that is associated with web server software. In the next class we will look at actually uploading the pages to a server.
  • Play around with HTML. Go over again the head and body. Title. H# tags.
  • Introduce lists and links.
  • Relative and absolute URLs.
  • Talk about text formatting (non-CSS).
  • Take questions.

 

Article

The simplicity of the web

The second class of multimedia storytelling design is focused on what I call the simplicity of the web. My advancing age, almost 50, gives me the advantage of having witnessed the evolution of the web from a text-based browser to the apparent complexity of modern web sites. I encourage those learning the web to break down the complexity and focus first on the simple, foundational aspects.

For our text in this course we’re using Jon Duckett’s HTML & CSS: design and build websites. Written for beginners, this book presents the basics in an engaging manner (with beautiful page layouts). I did choose, however, not to assign all the chapters in the same order as in the book. For the first class, we’re focusing on chapters 1, 2, & 5. Throughout this class we’ll be using the example of NY Times Snow Fall. It’s a complex piece but useful for these (mostly) journalism students to know how it was constructed.

Here are some of the questions (and occasional commentary) guiding discussion in this two-hour class:

Structure

  • What do we mean by structure?
  • Why are we talking about documents?
  • What are the structural elements on Snow Fall?
  • How can you see those HTML elements in the browser? How do you turn off the styles?
    • View Source
    • Unusually, the view source for Snow Fall is the whole article and not just what is visible.
    • What’s happening in the head and body?
    • Chrome needs the web developer plugin to disable all styles. (What’s an extension for a browser?)
    • In Firefox, it’s easier to view a page without styles
      • Firefox – View – Page Style – No Style.
    • A page without style: THAT is the simplicity of the web.
      •  In Firefox, show how you can hover over element with mouse and see the code view.
    • Chrome – Inspect element. I prefer how Chrome hover highlights the full element.
  • Do you see a hierarchy of information? Start with the <html> tag.
  • What’s a title in HTML?
  • What’s a header?
  • What’s the body?

In the view source of Snow Fall, (finally) around line 827, you’ll find:

<h1>Snow <span>F</span>all</h1>
<h2>The Avalanche at Tunnel Creek</h2>

Let’s look at that first paragraph.

  • What’s a heading?
  • What’s an element? What are tags? Any difference between an element and a tag?
  • What is markup and why is it used? What’s the purpose of elements and tags? Why is it necessary?
    • The machine reads character by character. A simple concept. Maybe so obvious that it’s not clearly grasped. Very important to slow down and read a page as the machine, the software, reads the page. The angle brackets are signifiers to the machine. Literally, signs that give directions to the browser about what to do.
  • What is plain text? What’s the difference between a plain text file and, say, a Microsoft Word file? Are there other types of markup languages?
    • Mention the Scholarly Text Encoding course
  • What are attributes of an elements?
  • Can I just use any tag? What tags are possible and how do I know?
  • Key HTML elements for beginners:
    • <body>
    • <head>
      • What’s the difference between the <head> element and a heading?
    • <title>

Text

Think about the separation of content from markup. Then think about the separation of content/markup from style/presentation.

Structural markup: show  examples of each in Snow Fall.

Semantic markup: examples of each in Snow Fall.

Heading tags: choose based on structure and not appearance.

The all important paragraph <p> tag.

Why is Duckett even mentioning <b> and <i> and not <strong> and <em>?

White space collapses on a web page.

Line breaks <br/>, horizontal rules <hr/> and empty elements

Blockquote

Many semantic elements are not used very often

Editors: time to fire up Atom?

Images

Keeping your images in a folder. Remember that a web site is simply a folder, right?

<img>

Image formats

Resolution

Raster & vector images

Animated GIFs

Transparency

 

When examining Snow Fall, take a moment and talk about not over linking. What’s the difference between this article and a Wikipedia page filled with links? What impact does that have on readability? On keeping you engaged with the story? Or, possibly more importantly, on the site?

With Snow Fall, what’s the difference between reading just the text and viewing the site? Do you wonder how many people actually read the whole article? Would another format actually have done more justice to the writing? (That’s a strange phrase…”done more justice”….privileging the written word over other forms of storytelling?)

 

 

 

 

Article

A new course: multimedia storytelling design

This morning starts the first class of a new course on multimedia storytelling design that I’m co-teaching with Professor Toni Locy of our journalism department.  The subtitle of the course is “How’d They Do that?” The benefit of co-teaching with a journalist is that the copywriting is great! Here’s the course description:

Have you ever wondered how The New York Times and The Guardian put together their Pulitzer Prize-winning interactive stories, Snow Fall: The Avalanche at Tunnel Creek and NSA Files Decoded: What the Revelations Mean to You? This course introduces students to digital tools that will help them imagine, design and create powerful, compelling interactive features with audio, video, graphics—and words—that are on the cutting edge of journalism and mass communications. Students will learn basic web design and programming skills through HTML, CSS and JavaScript.

This course is designed for students with little or no coding experience but who have a burning desire to learn, “How they did that,” so they no longer are mystified by what’s behind the curtain on websites. Students also will learn key terminology and practices that will enable them to envision, report and execute compelling online narratives through the interplay of text, images, sound and video that optimizes the reader experience. By the end of the term, students will appreciate the power and potential of interactive storytelling, and the creative possibilities of gathering and delivering the news in the 21st century.

The course meets Monday and Wednesday 10am – noon in the journalism lab, which is equipped with 15 iMacs. This is a very hands-on class, though we do not expect students to have had any prior experience with web design and development.

Wait!? No prior experience with web design? That does make it challenging since we need to teach the basics of HTML and CSS. Obviously, there’s no way that anyone can fully come up to speed on interactive web design in course of only one term. We aim to showcase the possibilities and to ensure that the students learn the foundations of web design. We want the students to come out of this course with the confidence and excitement that they can pursue careers in this area. Some may be enchanted by the design aspects, others may be intrigued by the possibilities of coding. And others may not pursue a technical career in web work, but at least will know how to converse intelligently with designers and developers.

The course is structured around deconstructing several examples of high-quality multimedia journalism. Among the sites we’ll be examining:

Each class period will start with the students discussing their reactions to various elements of a particular site. We want the students to think about the elements (interactivity, color, typography, etc.) used by each site to engage readers. Then we’ll pull back the curtain, so to speak, to dissect the actual construction of the site. Along the way, we will teach HTML and CSS from the ground up.

The students also will work on a course project as a team. The project will incorporate everything that they’ve learned. Since this is a journalism class, the project will have a significant reporting component. Students will brainstorm and storyboard the project, then implement it as a web site. The result will be an interactive multimedia story.

This is going to be an exicting and intense course!

Article

Prepping for the digital history class

This afternoon I’m teaching the first class on Digital History taught at Washington and Lee University. This is a one-credit class that is part of our DH Studio series, which is a set of one-credit lab courses for the humanities. I’m not a historian. I’m a librarian. I’m a technologist. And I’m fairly confident in saying that I know as much about Internet technologies as anyone. And what I don’t know off-hand, I know how to learn quickly. And that knowing how to learn technologies is one of the core concepts I’m emphasizing in the course.

History, the study of the past, is the context in this course through which we will study digital methodologies and tools. One could adapt this same course, with some variation, to the study of other disciplines: literature, journalism, sociology, anthropology, art history, politics, and so forth. The examples utilized would be different and certain approaches would vary. But a commonality exists among the ways that digital media facilitates discipline-specific inquiry. At the undergraduate teaching level it’s particularly important to emphasize that these digital approaches are not restricted to the academy. These skills transfer directly to a career in practically any industry and line of work, whether private or public.

I strongly feel that liberal arts students, particularly those studying the humanities, are in a very advantageous position to pursue technology-based careers. Without wanting to sound arrogant, I always cite myself as an example. As an English major at a small liberal arts college I avoided technology as much as possible. There wasn’t much of it around in the mid-1980s anyway. But when I got to graduate school, I was dragged kicking-and-screaming to the computer. I came to realize that technology was all about logical thinking. Learning a new technology was about breaking down complexity, identifying the logical components, and piecing together the structure. That’s the same process I had learned in studying literature, history, religion, and philosophy. I was very comfortable as a liberal arts student in dealing with ambiguity. But technology is not at all ambiguous.

 

The first day of class

As a one-credit course this class meets only once a week. We’re scheduled to meet for two hours every Thursday afternoon in the IQ Center, which is a great facility for collaborative learning. Students are expected to bring their laptops to class since there will be a lot of hands-on learning. The first hour of each class will be discussion. We’ll have a conversation about the resources, methodologies, and tools we’re examining. One of my goals for any undergraduate class is that I really want these college-age students to develop an ease in communicating and collaborating with someone who is thirty years older. That’s how life is in the workplace. You don’t just work with people your own age.

The second hour will be hands-on. And it’s likely that we won’t always meet for the full two hours, but I wanted to have the time blocked out so that the students could have time with me every week to work with the tools.

The class enrollment is small: only 2 students. Understanding why the course is so under enrolled is a post for another day, and a talk I’m giving at the upcoming DLF Forum. But, actually, it’s great just to have 2 students. And it’s especially great for them. Talk about the benefits of small class size! That’s why you go to a small liberal arts college: not to be stuck in an auditorium with dozens of other students.

The small class size means that attendance is really important. And the discussion should be a lot more engaging. Class participation 30% of the grade.

 

Course structure

This class could serve well as a companion to a regular history course. But there are a lot of logistical issues in scheduling a one-credit course as a co-requisite to a three-credit course. I needed to find some historical context in which to explore the digital methodologies and tools. I decided to focus on the history of Washington and Lee University (W&L). The namesakes of the university lend enough historical material, much of which is controversial (particularly with Lee). But the course is not primarily a history of W&L. The historical matter is simply a context. And that’s what makes this course different from a history course. Students will learn a lot about W&L history, but that’s not the primary goal of the course. My expectation is that this digital history course will continue year-after-year and the projects developed through this course will build on each other every year. Ultimately, through this course, we aim to develop a digital research environment for the study of W&L.

 

Case studies

To gain an informed understanding of digital history we will explore a few projects. A project we will examine closely is the Legacies of British Slave-ownership (LBS). The legacy of slave ownership is relevant to the history of W&L. And from a digital perspective, the LBS site is an outstanding example of digital scholarship that also demonstrates the connection to print scholarship through the scholarly book that was produced by the project team.

Other projects we will examine include the Trans-Atlantic Slave Trade Database, Visualizing Emancipation, and Photogrammar.

 

Course project

As a lab course, we need to centralize our work around a course project. Our starting point will be to learn about the shift in student demographics at W&L over time.  Some still think of W&L as a Southern institution, but any conversations with students on campus today quickly reveal that the student body includes many from New Jersey, Massachusetts, and other Northern states as well as the midwest. But how do we quantify and visualize that information?

And there’s the strong assumption that W&L students historically have been from the South. We will collect the data to show exactly where W&L students have come from over the years. We will develop an interactive map that visualizes the origins of W&L students from 1790 until 2015. In this Fall Term we will not complete every year of that data set, but we will establish the structural foundation and create version 1.0 of the interactive map.

 

It’s almost time for class. In another post I’ll review one of the methodologies (prosopography) that we will be exploring as well as a key tool (CartoDB).

css.php