Mapping James Joyce’s Ulysses

Abe Parrish and Sam Alexander standing in front of a projected image of a map of Dublin

Abe Parrish of the Map Department and Sam Alexander, a graduate student in English, joined us this week to discuss their digital interactive map of James Joyce’s Ulysses *. The project germinated as a component of an undergraduate seminar taught by Pericles Lewis, who approached Abe with the idea in August 2010. Once it reached beta stage, Sam brought the map to the seminar students for a test drive: part building, part analysis.

For the major work, the project needed just one primary source (a Yale-owned 1900 Dublin map) and one piece of software (ESRI’sArcGIS Viewer for Adobe Flex). Digitizing the map created a raster image, requiring subsequent conversion to a vector file for use in ArcGIS Viewer. The vectorized map was then layered over native ArcGIS topographic and street maps of contemporary Dublin and broken up into queryable blocks, allowing students to locate, mark, and annotate narrative locations in the historical image.

What sets ArcGIS Viewer apart from other programs like Google Earth is that it is browser-based, with the capacity for multiple users to view and edit geographical data at once and without downloading uncommon software or plug-ins. (Viewing the project does require the use of Adobe Flash, which effectively eliminates Apple mobile devices.) Traditional mapping software requires individuals to create discrete edits to maps and then merge the documents, rather than enabling collaborative editing.

Sam offered his students three choices for working with the map as part of the seminar.  The first option–building a stable base layer of data to which future users could add–would advantage the long-term, but be less interesting to current students.  The second option was to focus on the socio-political context of the novel such as locations of the famous Phoenix Park Murders.  The third option, which Sam recommended against, was to actually map the narrative of Ulysses.

Though his students ultimately picked the idea he recommended against, Sam believes that the decision to use the map to trace the narrative of Ulysses was ultimately the right decision. Mapping the novel forced a new type of engagement, and is unlike any scholarship currently available. To his knowledge, there are no other large-scale, detailed maps of Ulysses.

Reframing Ulysses in terms of its geography, Sam explains, can spatialize the temporal events of the novel. By using the mapping tool, even with the story’s forward-moving plot, readers were able to imagine Dublin all at once as if it were laid out before them, an aim Joyce avowed publicly. The map provided an entry point for students into the complicated character psychology of the novel. By seeing on the map which buildings and streets were influencing a character, students could better understand what might be pulling the thoughts of the character in specific directions. Perhaps seeing a tea house makes a character think of “the East,” or proximity of disparate ethnic communities makes a character meditate on immigration. Physical context clues offered by mapping the novel provide an often clearer and certainly richer engagement with the novel. Even moments where Joyce’s narrative seems to not make geographical sense (on one occasion, a character crosses a street in the opposite direction of the stated destination), interesting questions emerge. Did Joyce get it wrong? Was Joyce attempting to show how the character changes his mind, first moving in one direction and then another? Such geographical details are occluded from readers without intimate knowledge of the setting and provide new contexts for interpretation.

After incorporating around 80 events of the novel into the map, Sam asked his students to engage in an analysis of the project, offering suggestions for future use. One of the epistemological issues that emerged related to the choice of the word “event” for the points marked on the map. This decision was problematized when, for instance, characters thought of places (do you mark the character’s location or the thought-place location?) or perceived remote occurrences (mark the site of perception or of occurrence?). Some challenges were technical: The search tool might benefit from some tweaking and the number of metadata fields for each event was overly ambitious. Not all of the addresses are extant; this cross-temporal anomaly added layers of interpretation, as students looked for landmarks like Nelson’s Pillar, only to learn that it was destroyed by former IRA volunteers in 1966.

Opportunities remain to enhance the program by tracing routes, adding additional layers, and augmenting the program for growth. Students suggested attaching the map to a wiki and making it compatible with smartphones, selling an app to tourists on Bloomsday tours. We’re eager to see the project evolve in years to come, and curious about the archival challenges its growth might present!

For full coverage of this session, please click the video below (note a slight delay upon initial playback):

The CUNY Academic Commons: Building the Social University

Matthew Gold talks about the CUNY Academic Commons

Matthew Gold and Boone Gorges, respectively Project Director and Lead Developer for the CUNY Academic Commons, joine us today to discuss creating and maintaining a scholars’ social network using BuddyPress. (We’re currently trying to work towards implementing a similar system as a way of interconnecting the nearly 500 blogs and thousands of posts currently in WordPress.)

CUNY Academic Commons was launched in 2009 with three goals: connect people across campuses, create a space in which faculty members and grad students could create content, and encourage exploration and discovery. Because of the diverse population and geography of the CUNY system, there was an administrative need to create an integrated, connected, networked university. The academic commons grew out of a committee composed of two representatives from each of the colleges (faculty, staff, administrators, graduate students) and was charged with creating an academic technology commons to determine the best practices of teaching with technology.

After much discussion, they determined that they did not want an institutional repository (no social networking!), a perfect taxonomy, a hard sell to potential participants, or traditional model of tech support (hoping for a more do-it-yourself approach). Conversely, they were certain they wanted openness (in the ethos, mode of development, and access), an organic system, and decentralization.

Starting with the capacities already available in WordPress — author-focused, published content (blog posts) and commentary dependent on those posts —Academic Commons grew by adding the BuddyPress plugin, opening up the world of groups, profiles, and a media wiki. Going beyond blogs, forums, and documents, groups link people through profiles (much like Facebook). Groups ranging from focus on academic subjects (such as digital humanities or use of games in the classroom) to social subjects (such as Pizza in New York) have emerged to create powerful interactions on the website. Sorting devices through the News Feed enable filtered content (much like a Twitter feed), allowing users to look at the information sharing around the network most pertinent to individualized interests. The media wiki enables collaborative editing of documents as well as historical and meta-discussions about the site.

Matt and Boone argued that one of the most important features of the growth and functionality of the site is transparency in development and support. Boone emphasized the need to have porous boundaries between users and support at all levels, focusing on regular communication with the community through the “Feedback” tab located on the right side of every page. Primarily, the feedback tab is used to report (and fix) bugs, but it also enables members to suggest content and vote on others’ suggestions (much like Reddit or Digg). While some communication methods have added work, such as Boone’s development blog, some have added community (read: free) assistance, helping to track, edit, and test new developments. Ultimately, all of these functions are meant to incorporate the entire community into the building of the Commons so that users are engaged in creating a warmer community.

One of the missing pieces of the site, however, is the lack of available support for incorporating CUNY’s approximately 250,000 undergraduates. For the future, there is hope that Academic Commons will be able to include not only undergraduates, but also functions to engage content from Blackboard. Furthermore, Matt and Boone are happy (and eager) to talk with other universities interested in pursuing similar efforts — like Yale!

Interested in more?  See Matt and Boone’s powerpoint.


For full coverage of this session, please click the video below (note a slight delay upon initial playback):