Topic: Digital humanities

Making the Case for Drupal

By Erica Cavanaugh, CDE Project Developer
October 27, 2017

Digital publication remains a challenge for many documentary editing projects, especially when dealing with complex documents such as farm reports, financial records, and ship logs. Traditionally, editors have relied upon TEI-based solutions (an XML format for humanities projects), often omitting those more complicated documents and focusing instead on correspondence, speeches, and diary entries. Beyond that, these TEI-encoded documents need additional work. The documents need to be transformed from TEI into another code and then a custom publication environment needs to be developed. As a result, many projects struggle to use that model as a solution without external support. In order to address this issue, the Center for Digital Editing (CDE) has turned toward the open-source content management system Drupal.

Drupal is a freely available, open-source content management system. Its flexibility has allowed for the creation of diverse websites, including weather.com, fema.gov, university websites, and e-commerce sites. While it has a steep learning curve compared to other content management systems, it can be fully customized, giving users complete control over the types of metadata captured, defining relationships between content, displaying content, and developing user interaction. These features make Drupal ideal for digital humanities projects, such as digital documentary editions.

At its core, Drupal is written in PHP (a server-side scripting language) and uses MySQL (an open source relational database) to store its content. Customizations are then introduced with the installation of modules, which extend core functionality, and themes in order to modify site appearance. Conveniently, Drupal’s active user and developer community has contributed code, modules, and themes useful for digital documentary editions and other scholarly projects. These modules thus alleviate the need for projects to create custom code and significantly reduces the amount of “code” maintenance on the site. Module updates are fairly easy to install, too. (Those familiar with WordPress will find these updates to be similar to the process of using and updating plugins.)

For the CDE, these modules have allowed us to capture various types of metadata, develop an editorial interface, manage document workflow, and create a digital edition for both traditional types of documents and the more complex ones. Let’s look at our work in creating a user-friendly editorial apparatus.

So far, we have created fields for capturing metadata and the various elements of a transcribed document including dateline, salutation, body text, closing, and signature. Using these fields has made it easier to digitally transcribe documents as well as standardize their formatting. Moreover, by fielding each aspect, it is easier to export documents in various formats: they can be printed as PDFs, exported as Word documents, CSV files, or even mapped to XML schemas like TEI.

Another feature we have customized is the WYSIWYG or text editor. For many Drupal users, the standard WYSIWYG editor works well enough as is, making it easy to bold, italicize, underline, strikethrough, and superscript text, as well as list items. But documentary editors often need to do more than that. For some, it is important to apply small caps, indent the text, align bits of text left and right, or even replicate marginalia written sideways. While it is possible to enter the HTML and CSS by hand to implement this formatting, editors frequently are not familiar enough with HTML and CSS to do so. Such high-level customizations would also make it difficult for students to significantly contribute to these editions. Minor customizations to the WYSIWYG editor style sheet that are shared between Drupal installations, however, make it easy for editors and students to edit text as needed.

Drupal also simplifies the management of document workflow and the tracking of editorial changes. In order to do this, we have incorporated a couple of modules. One of these includes the Workflow module, an installation that allows for the creation of a customized document workflow. Using this module, we can create stages tailored to individual projects, identify the number of documents in a particular stage, and define which users can move a document from one stage to the next. Additionally, we can see who has done what and when, create a search interface to find documents in a particular stage, establish a student work portfolio, and bulk-publish groups of documents based on their stage.

Another module allows us to see versions and changes made to a document or other record, such as an identification. For ease of document management, each version of a record includes information about the date and user. Additionally, versions can be compared side-by-side, making it possible to tell what was changed. This feature is particularly useful when dealing with difficult-to-read words and transcriptions, as well as when drafting identifications.

For many projects, capturing metadata, completing editorial work, and managing the documents are all performed in an environment separate from the publication platform. With Drupal, however, we are able to digitally publish documents in the same environment in which the materials are prepared. Any number of documents or transcriptions can be published at the click of a button, and information need only be captured one time in order to create multiple, dynamic displays of the content, such as timelines, maps, and other site-generated visualizations. As we continue to advance, we can also look for ways to engage more with the public user.

Visualizing George Washington’s Voyage to Barbados

by Erica Cavanaugh, Research Editor
August 3, 2017

In anticipation of the upcoming edition of the diary George Washington kept during his trip to Barbados, I worked with editors Lynn A. Price and Alicia K. Anderson to create an interactive map of Washington’s voyage. The map not only illustrates the ship’s progress and landing but also describes the weather encountered and the food eaten during the journey. Such details are revealed by selecting from the various elements included on the map. Users can customize the display by toggling the selection of these elements on the legend or by zooming in and out on the map.

Washington’s voyage began prior to September 28, 1751, in the Chesapeake Bay (indicated by a red circle on the map). From there, a green line maps the latitude and longitude as recorded in Washington’s ship log from September 28 to October 30. At the end of the journey’s first leg, 19-year-old George Washington’s calculations placed the ship to the east of Barbados by about 450 nautical miles, as illustrated on the map, but the ship was actually about 10 miles west of the island. An icon in the shape of a pineapple marks his final destination. When selected, a map of the island is displayed, indicating where Washington’s ship landed.

Along the green line are four ship icons that reference notable points of Washington’s passage. When clicked, each ship icon displays an excerpt from the diary, highlighting common themes of his voyage. For example, the entry from October 6, 1751, discusses the food consumed on the journey. Throughout the diary, Washington was interested in the various types of fish he saw, at times detailing how they were caught, brought aboard the ship, and dressed. Another entry, dated October 19, 1751, discusses the stormy weather and a nearby hurricane.

The map also includes illustrations of the Bermuda Triangle and the North Equatorial Current. While it is unlikely that Washington’s voyage took him through the Bermuda Triangle, his brother Lawrence probably sailed through it when he traveled from Barbados to Bermuda, searching for relief from his illness. It is likely, however, that the North Equatorial Current and trade winds (not illustrated) would have impacted the brothers’ journeys to and from Barbados.

Developed with help from the Center for Digital Editing, this interactive map was created using Leaflet, an open-source JavaScript library for mobile-friendly interactive maps, and MapBox, an open-source mapping tool for creating custom-designed maps. To plot the points from George Washington’s ship log, the latitude and longitude were converted from degrees, minutes, and seconds to decimal points. A map from the Department of Geography at Hunter College was referenced to plot the North Equatorial Current. Public domain images were used for the ship and pineapple icons. The map of Barbados is courtesy of the John Carter Brown Library, Map Collection.

You can view and explore the interactive map of Barbados here.

 

 

Testing the Financial Papers Website

by Erica Cavanaugh, Research Editor
March 17, 2017

One of the primary goals of the George Washington Financial Papers Project (GWFPP) has been to make Washington’s financial records freely accessible. The GWFPP team has worked tirelessly to provide accurate transcriptions as well as to build and illustrate relationships among people, places, and themes. However, what would be the point of all this if no one could use the website? In order to make sure the GWFPP site is accessible, efficient, navigable, and meaningful, we conducted usability testing in December 2016. Using the University of Virginia’s Scholars’ Lab, we invited students and some faculty members to explore the site and assess its navigability and accessibility.

Continue reading

What is the Center for Digital Editing?: A Partner, a Leader, an Organizer

by Jennifer Stertzer, Senior Editor at the Washington Papers and Director of the CDE
October 28, 2016

The Center for Digital Editing (CDE) at the University of Virginia has a very specific mission: to advance the practice of editing by creating and encouraging the growth of innovative project solutions. We aim to help projects accomplish the twin goals of documentary editing—scholarship and accessibility—by taking full advantage of the possibilities of our hyperlinked world. Over the past year, we have identified four elements we see as essential to advancing that mission: research and development, engagement, project consultation and development, and education.

Continue reading

Washington Papers Editors Share Work, Meet Hamilton’s George Washington at Human/Ties National Endowment for the Humanities Conference

by Kim Curtis, Research Editor
September 30, 2016

From September 14 to 17, the University of Virginia (UVA) hosted Human/Ties, a four-day celebration of the 50th anniversary of the National Endowment for the Humanities (NEH). To explore and honor the vital role played by the humanities in today’s world, the forum brought together multiple University departments and programs, including the Washington Papers, as well as speakers and artists from across the country and around the world.

Continue reading

Documentary Editing at the Digital Humanities Summer Institute

By Cathy Moran Hajo, Director of the Jane Addams Papers Project
July 1, 2016

IMG_20160617_124340732-300x222Since 2001, the Digital Humanities Summer Institute, held annually in Victoria, British Columbia, Canada, has been an annual gathering of technologists, scholars, librarians, graduate and undergraduate students…and editors. For the past three years, Jennifer Stertzer (Washington Papers) and Cathy Hajo (The Jane Addams Papers Project), joined this year by Erica Cavanaugh (Washington Papers), have offered a course titled “Conceptualising and Creating Digital Editions,” one of a rich slate of hands-on and theoretical week-long immersions into digital humanities.

Continue reading

The George Washington Financial Papers Project: Building Content-Specific Taxonomies and System Specifications

By Senior Editor Jennifer Stertzer & Research Editor Erica Cavanaugh
April 28, 2016

One of the many interesting challenges the George Washington Financial Papers Project (GWFPP) team has faced is how best to make content accessible, or more accurately, intellectually accessible. This is hardly a new challenge, though, as editors have always worked to move beyond mere availability.

Regardless of approach (whether print or digital), documentary editions are created to make documents and content accessible: transcriptions make hard-to-decipher text readable; annotations provide contextualization and aid in understanding; and indexes allow users to search for both explicit text as well as indirect references, concepts, themes, and ideas. Indeed, several of the project’s goals relate directly to this intellectual accessibility: to provide accurate and understandable transcriptions and manuscript images, to supply context for these materials, and to create an opportunity for reader/user engagement.

What makes this challenge particularly interesting for the project has been the opportunity to create accessibility while developing a content management/publication platform. This allows us to experiment with how best to organize and structure the content within the system so that we can build a variety of access points. We will explore the different aspects of this process in the next few blog posts from the GWFPP team, beginning with our work with taxonomies.

Continue reading

Nearing Completion, the George Washington Financial Papers Project Will Expand Scholarship on Washington and the Versatility of the Digital Humanities

By Jennifer E. Stertzer, Senior Editor
January 29, 2015

Making George Washington’s financial papers accessible had been an early goal of the Washington Papers, but given the intricacies of the financial papers and our means of publication, very little had been done. In the 1980s, the Washington Papers published several cash accounts (in print) from the ledgers in the Colonial Series of the Papers of George Washington. Over the years, we included a few others as documents and used them for our annotations where possible. Things began to shift as we moved forward with our digital rendition of the letterpress volumes. We began to think about solutions for the financial papers, and our ideas grew and evolved with the huge advances made in the field of digital humanities in the last few years.

Continue reading