Where do patrons get lost? A study of library navigation.

In the Assessment & User Experience Department, we’re always looking for ways to improve how our patrons experience the libraries’ physical and online spaces. One of our primary ways of learning about our patrons is our biennial user satisfaction survey, which we use to collect opinions from large groups of our patrons about a wide range of issues.

One topic that comes up regularly among our patrons is the navigation of our physical spaces. Like many libraries, our buildings have evolved over time, and that can make navigating our spaces a bit complicated. On Duke’s West Campus, we have three library buildings that are interconnected – Rubenstein Library, Perkins Library, and Bostock Library. Responses and comments on our biennial survey confirm what we hear anecdotally – patrons have trouble navigating these three buildings.

Deep Dive into Navigation Concerns

But how can we follow up on these reports to improve navigation in our spaces? Ideally, we would gather data from a large number of people over a long period of time to find very common and problematic navigation issues. Our biennial survey offers data from a large number of people over time, but it isn’t a great format for gathering detailed data about narrow subjects like navigation.  Conducting an observational study of our spaces would explore navigation directly, but it would only include a small number of people, and the likelihood that we would catch individuals having trouble with navigation is low. We could try conducting ad hoc surveys of patrons in our spaces, but it would be difficult to ensure we are including people who have had navigation trouble, and it may be difficult for patrons to recall their navigation trouble on the spot.

What we needed was a way of capturing common examples of patrons having trouble with navigation. We decided that, instead of asking patrons themselves, our best resource would be library staff. We know that when patrons are lost in our buildings, they may reach out to staff members they see nearby. By surveying staff instead of patrons, we take advantage of staff who know the buildings well and who are commonly in particular areas of the buildings, noticing and offering help to our struggling patrons.

We decided to send a very simple survey to all staff in these library buildings. Staff could fill it out multiple times, and the only two questions were:

  • What is a common question you have helped patrons with?
  • Where are the patrons when they have this question, typically?

We had a great response from staff (72 responses from 36 individuals), and analyzing the responses showed several sources of confusion.

Pie chart showing categories of responses to library navigation survey. 35% of responses reported patrons in the wrong building. 26% reported patrons in the right general area. The rest were split amongst "wrong campus building," "wrong floor", and "can't find books."

Focusing on questions where patrons are in library spaces and not near a help desk, two concerns account for over 60% of reported patron navigation issues:

  • Building confusion
  • Hidden rooms

Trouble Between Buildings

Our three connected library buildings, unfortunately, connect in ways that are not obvious to new visitors. Because buildings only connect on certain levels, it is easy for patrons to be looking for a location on the right floor but the wrong building. By asking staff for specific locations of both patrons and their desired destination, we could compile the most frequent problems that involve being in the wrong building. Unsurprisingly, the locations that cause the most difficulty are our large meeting rooms and classroom spaces, especially those that are not on the ground floor of the buildings.

The most common problems seem to happen when patrons leave the first floor while in the wrong building, expecting the buildings to connect on the other floors (or not realizing which building they are in). As you can see from the side-view of our buildings below, the Perkins and Bostock library building have easy connections on all floors, but the Rubenstein Library only connects to Perkins on the first floor. Our survey confirmed that this causes many issues for patrons looking for 2nd floor or Lower Level meeting rooms in Perkins and upper level meeting rooms in Rubenstein.

A diagram showing a side-view of navigation between the three library buildings. Rubenstein and Perkins connect on the first floor. Perkins and Bostock connect on all but the first floor.

While we are still in the process of developing and testing possible solutions, we hope to redesign signage in a way that better signposts when patrons should proceed onward on the current floor and when they should transition up or down.

Trouble on the Same Floor

Our survey suggests, unfortunately, that it is not enough to get patrons to the correct floor. Depending on the route the patron takes, there are still common destinations that are difficult to see from stairwells, elevators, and main hallways. Again, this difficulty tends to arise when patrons are looking for meeting rooms. This makes sense, as events held in our meeting rooms can attract patrons who have not yet been to our buildings.

Staff reports for same-floor confusion focus largely on floors where room entrances are hidden in recesses or around corners and where rooms are spaced apart such that it is hard to simply follow room number signage. As a notable example, the 2nd floor of Perkins Library seems especially confusing to patrons, with many different types of destinations, few of which are visible from main entrances and hallways. In the diagram below, you can see some of the main places patrons get lost, indicating a need for better signage visible from these locations. (Pink question marks indicate the lost patrons. Red arrowheads indicate the desired destinations.)

A floor plan of Perkins 2nd floor, with curved arrows showing reports of patrons who are far away from their desired destination.

As we develop solutions to highlight locations of hidden rooms, we are considering options like large vinyl lettering or perpendicular corridor signs that alert people to rooms around corners.

Final Thoughts

This technique worked really well for this informal study – it gave us a great place to start exploring new design solutions, and we can be more proactive about testing new navigation signage before we make permanent changes. Thanks for your great information, DUL staff!

FOLIO Update November 2019

Here at Duke, the buzz continues around FOLIO. We have continued to contribute to the international project  as active participants on the FOLIO Product Council,  special interest groups, and contribute development resources. You can find links to the various groups on the FOLIO wiki.

We’ve also committed to implementing the electronic resource management (ERM)-focused apps in summer of 2020. Starting with the ERM-focused apps will give us the opportunity to use FOLIO in a production environment, and will be a benefit to our Continuing Resource Acquisitions Department since they are not currently using software dedicated to electronic resources to keep track of licences and terms.

 

Our local project planning has come more into focus as well. We have gathered names for team participants and will be kicking off our project teams in January. As we’ve talked about the implementation here, we’ve realized that we have a number of tasks that will need to be addressed, regardless of subject matter. For example, we’re going to need to map data – not just bibliographic, holdings and item data, but users, orders, invoices, etc. We’ll also need to set up configurations and user permissions for each of the apps, and document, train, and develop new workflows. Since our work is not siloed in functional areas, we need to facilitate discussions among the functional areas. To do that, we’re going to create a set of functional area implementation teams, and work groups around the task areas that need to be addressed.

To learn more about the FOLIO project at Duke, fly on over to our WordPress site and read through our past newsletters, look through slides from past presentations, and check out some fun links to bee facts.

ArcLight at the End of the Tunnel

Archival collection guides—also known as finding aids—are a critical part of the researcher experience when finding and accessing materials from the David M. Rubenstein Rare Book & Manuscript Library and the Duke University Archives. At present, we have guides for nearly 4,000 collections with upwards of one million components that have some level of description. Our collection guides site is visited by researchers about 400 times per day.

example finding aid
An example collection guide.

In 2020, we’ll be making significant changes to our systems supporting archival discovery and access. The main impetus for this shift is that our current platform has grown outdated and is no longer sustainable going forward.  We intend to replace our platform with ArcLight, open source software backed by a community of peer institutions.

Finding Aids at Duke: Innovations Past

At Duke, we’re no strangers to pushing the boundaries of archival discovery through advances in technology. Way back in the mid 1990s, Duke was among pioneers rendering SGML-encoded finding aids into HTML.  For most of the 90s and aughts we used a commercial platform, but we decided to develop our own homegrown finding aids front-end in 2007 (using the Apache Cocoon framework). We then replaced it in 2012 with another in-house platform built on the Django web framework.

Since going home-grown in 2007, we have been able to find some key opportunities to innovate within our platforms. Here are a few examples:

finding aid with digitized component
Example archival component with inline embedded digital object and sticky navigation.

So, Why Migrate Now?

Our current platform was pretty good for its time, but a lot has changed in eight years. The way we build web applications today is much different than it used to be. And beyond desiring a modern toolset,  there are major concerns going forward around size, search/indexing, and support.

Size

We have some enormous finding aids. And we have added more big ones over the years. This causes problems of scale, particularly with an interface like ours that renders each collection as a single web page with all of the text of its contents written in the markup. One of our finding aids contains over 21,000 components; all told it is 9MB of raw EAD transformed into 15MB of HTML.

JWT Competitive Ads finding aid
A large finding aid — 15MB of HTML in a single page.

No amount of caching or server wizardry can change the fact that this is simply too much data to be delivered and rendered in a single webpage, especially for researchers in lower-bandwidth conditions. We need a solution that divides the data for any given finding aid into smaller payloads.

Search

Google Custom Search does a pretty nice job of relevance ranking and highlighting where in a finding aid a term matches (after all, that’s Google’s bread-and-butter). However, when used to power search in an application like this, it has some serious limitations. It only returns a maximum of one hundred results per query. Google doesn’t index 100% of the text, especially for our larger finding aids. And some finding aids are just mysteriously omitted despite our best efforts optimizing our markup for SEO and providing a sitemap.

search results powered by Google
Search Results powered by Google Custom Search

We need search functionality where we have complete control of what gets indexed, when, and how. And we need assurance that the entirety of the materials described will be discoverable.

Support

This is a familiar story. Homegrown applications used for several years by organizations with a small number of developers and a large number of projects to support become difficult to sustain over time. We have only one developer remaining who can fix our finding aids platform when it breaks, or prevent it from breaking when the systems around it change. Many of the software components powering the system are at or nearing end-of-life and they can’t be easily upgraded.

Where to Go From Here?

It has been clear for awhile that we would soon need a new platform for finding aids, but not as clear what platform we should pursue. We had been eyeing the progress of two promising open source community-built solutions emerging from our peer institutions: the ArchivesSpace Public UI (PUI), and ArcLight.

Over 2018-19, my colleague Noah Huffman and I co-led a project to install pilot instances of the ASpace PUI and ArcLight, index all of our finding aids in them, and then evaluate the platforms for their suitability to meet Duke’s needs going forward. The project involved gathering feedback from Duke archivists, curators, research services staff, and our digital collections implementation team. We looked at six criteria: 1) features; 2) ease of migration/customization; 3) integration with other systems; 4) data cleanup considerations; 5) impact on existing workflows; 6) sustainability/maintenance.

comparison of PUI and arclight
Comparison of the ASpace PUI and ArcLight, out-of-the-box UI.

There’s a lot to like about both the ASpace PUI and ArcLight. Feature-wise, they’re fairly comparable. Both are backed by a community of talented, respected peers, and either would be a suitable foundation for a usable, accessible interface to archives. In the end, we recommended that Duke pursue ArcLight, in large part due to its similarity to so much of the other software in our IT portfolio.

ArcLight is an extension to Blacklight, which is the key software component powering our library catalog, our Digital Collections / Digital Repository, and our Hyrax-based Research Data Repository. Our developers and operations staff have accumulated considerable experience working together to build, customize, and maintain Blacklight applications.

ArcLight Community Work Cycle: Fall 2019

Duke is certainly not alone in our desire to replace an outdated, unsustainable homegrown finding aids platform, and intention to use ArcLight as a replacement.

This fall, with tremendous leadership from Stanford University Libraries, five universities collaborated on developing the ArcLight software further to address shared needs. Over a nine week work cycle from August to October, we had the good fortune of working alongside Stanford, Princeton, Michigan, and Indiana. The team addressed needs on several fronts, especially: usability, accessibility, indexing, context/navigation, and integrations.

Arclight community work cycle II
Duke joined Stanford, Princeton, Michigan, and Indiana for Arclight Community Work Cycle II in fall 2019.

Three Duke staff members participated: I was a member of the Development Team, Noah Huffman a member of the Product Owners Team, and Will Sexton on the Steering Group.

The work cycle is complete and you can try out the current state of the core  ArcLight demo application. It includes several finding aids from each of the participating partner institutions. Here are just a few highlights that have us excited about bringing ArcLight to Duke:

ArcLight UI screenshots
Search results can be grouped by collection. Faceted navigation helps pinpoint items of interest from deep within a finding aid.
Screenshots of Arclight UI
Components are individually discoverable and have their own pages. Integrations with online content viewers and request systems such as Aeon are possible.

Here’s a final demo video (37 min) that nicely summarizes the work completed in the fall 2019 work cycle.

Lighting the Way

National Forum on Archival Discovery and DeliveryWith some serious momentum from the fall ArcLight work cycle and plans taking shape to implement the software in 2020, the Duke Libraries intend to participate in the Stanford-led, IMLS grant-funded Lighting the Way project, a platform-agnostic National Forum on Archival Discovery and Delivery. Per the project website:

Lighting the Way is a year-long project led by Stanford University Libraries running from September 2019-August 2020 focused on convening a series of meetings focused on improving discovery and delivery for archives and special collections.

Coming in 2020: ArcLight Implementation at Duke

There’ll be much more share about this in the new year, but we are gearing up now for a 2020 ArcLight launch at Duke. As good as the platform is now out-of-the-box, we’ll have to do additional development to address some local needs, including:

  • Duke branding
  • An efficient preview/publication workflow
  • Digital object viewing / repository integration
  • Sitemap generation
  • Some data cleanup

Building these local customizations will be time well-spent. We’ll also look for more opportunities to collaborate with peers and contribute code back to the community. The future looks bright for Duke with ArcLight lighting the way.

A Statement of Commitment

The featured image is from a mockup of a new repositories home page that we’re working on in the Libraries, planned for rollout in January of 2020.

Working at the Libraries, it can be dizzying to think about all of our commitments.

There’s what we owe our patrons, a body of so many distinct and overlapping communities, all seeking to learn and discover, that we could split the library along an infinite number of lines to meet them where they work and think.

There’s what we owe the future, in our efforts to preserve and share the artifacts of knowledge that we acquire on the market, that scholars create on our own campus, or that seem to form from history and find us somehow.

There’s what we owe the field, and the network of peer libraries that serve their own communities, each of them linked in a web of scholarship with our own. Within our professional network, we seek to support and complement one another, to compete sometimes in ways that move our field forward, and to share what we learn from our experiences.

The needs of information technology underlie nearly all of these activities, and to meet those needs, we have an IT staff that’s modest in size, but prodigious in its skill and its dedication to the mission of the Libraries. Within that group, the responsibility for creating new software, and maintaining what we have, falls to a small team of developers and devops engineers. We depend on them to enhance and support a wide range of platforms, including our web services, our discovery platforms, and our digital repositories.

This fall, we did some reflection on how we want to approach support for our repository platforms. The result of that reflection was a Statement of Commitment to Repositories Support and Development, a document of roughly a page that expresses what we consider to be our values in this area, and the context of priorities in which we do that work.

The committee that created the statement was our Digital Preservation and Publishing Program, or DP3 as call it in house. We summarized our values as “openness, community and peer engagement, and independence from vended platforms,” which have “guided us to build our repositories on open source software platforms.” We place that work within the context of very large, looming priorities like our transition to FOLIO as our Library Services Platform, and the project to renovate Lilly Library. There are others, not mentioned in the statement, that fill the pages of this blog.

The statement is explicit that we will not seek to find alternative platforms for our repository services in the next several years, and in particular while the FOLIO transition is underway. This decision is informed by our recognition that migration of content and services across platforms is complex and expensive. It’s also a recognition that we have invested a lot into these existing platforms, and we want to carve out as much space as we can for our talented staff to focus on maintaining and improving them, rather than locking ourselves into all-consuming cycles of content migration.

From a practical perspective, and speaking as the manager who oversees software development in the Libraries, I see this statement as part of an overall strategy to bring focus to our work. It’s a small but important symbolic measure that recognizes the drag that we create for our software team when give in to our urge to prioritize everything. 

The phrase “context switching” is one that we have borrowed from the parlance of operating systems to describe the effects on a developer of working on multiple projects at once. There are real costs to moving between development environments, code bases, and architectures on the same day, in the same week, during the same sprint, or within even an extended work cycle. We also call this problem “multi-tasking,” and the penalty it imposes of performance is well documented

Even more than performance, I think of it as a quality of life concern. People are generally happier and more invested when they’re able to do quality work. As a manager, I can work with scheduling and planning to try to mitigate those effects of multitasking on our team. But the responsibility really lies with the organization. We have our commitments, and they are vast in size and scope. We owe it to ourselves to do some introspection now and again, and ask what we can realistically do with what we have, or more accurately, who we are.

CaiaSoft: The GFA Replacement

This fall, Library ITS is helping the Library Service Center (LSC) plan the transition to new high density storage management software. We are engaging with CaiaSoft who provides new software that supports improved workflow processes and reporting for the LSC.

Why Is This Important?

The LSC is best described as the Libraries’ “Grand Central Station”, a topic highlighted in a 2012 article about the Center’s value to DUL.

The center houses roughly 6 million books, documents and archival materials belonging to Duke and other library systems. With this in mind, it is very important to have up-to-date technology, and software services that promotes efficient workflows.

Why Are We Planning This?

GFA, the LSC’s current software tool is running on an unsupported, end-of-life operating system.

As a result, we run the risk of unwanted processing delays in the event of a failure on the current server. In turn, these delays would affect staff, researchers, and others looking for materials located at the LSC.

Who Is Planning This?

The project’s cross-division team involves staff from the following DUL departments:

  • Access and Delivery Services
  • DUL Technical Services
  • Rubenstein Research Services
  • Library Service Center
  • Library ITS

When Are We Planning This?

The transition to CaiaSoft is intended to take place on a weekend in January 2020. After this, LSC staff and supporting departments expect to use CaiaSoft to manage items located at the LSC warehouse.

Prep Work

The Project Team, during the planning stages, will have these goals in mind:

  • Overseeing data loading and accuracy
  • Creating and documenting workflows
  • Managing scripts to ensure ALEPH integration
  • Ensuring future seamless FOLIO integration

Expected Benefits

The project team has identified several key benefits, most noteworthy is improved workflow support. In addition, other  benefits identified by the Project Team are (but not limited to):

  • Web Browser Access
    CaiaSoft runs as a web application. In contrast, GFA only runs within a SSH session and requires the use of added software.
  • Item-level Data Management
    Staff can create “data flags”, and assign them at item-level.  In contrast, this feature is not available in GFA.
  • Data Auditing
    CaiaSoft offers this feature, while GFA does not.
  • FOLIO Integration
    CaiaSoft developers are active in supporting FOLIO.
More Feature Comparisons

A full list of feature comparisons is available on our WIKI page — look for the “Feature Comparison – CAIASOFT vs GFA” section.

Questions? We Have Answers…

I will be available at “First Wednesday” on November 6 to take questions and (hopefully) provide answers.

Giao’s Whirlwind Experience as an ARL-LCDP Fellow

The Association of Research Libraries’ Leadership and Career Development Program (LCDP) just recently completed the capstone institute for the 2018-2019 cohort. As a member of that cohort, called “The Disruptors,” I wanted to showcase the program. First of all, it was a year-long program that consisted of an orientation, two institutes, a visit to my career coach’s institution, and a capstone institute.

2018-2019 ARL LCDP Fellows.

The Disruptors included librarians who hail mostly from ARL member institutions from all over the country and Canada. The program is intended for librarians of color who are mid-career and are interested in leadership development. The ARL LCDP was an eye-opening experience – one that gave me perspectives from my cohort that I would have never gleaned otherwise, one that allowed us to learn from each other’s challenges and successes, and one that has given me a cohort that I can always rely upon as I go through my professional journey.  

I’ll start from the beginning. The orientation in Washington DC was an opportunity for the 24 of us to get to know each other, to establish learning expectations for ourselves and each other, and to plot our journey as a group. We listed topics that we’d like to explore together (i.e. strategic planning, open access, fundraising etc.), and explored the idea of leadership together. Mark Puente, the Director of Diversity and Leadership Programs at ARL, and DeEtta Jones moderated this and many of our discussions (in person and online). What a fantastic duo Mark and DeEtta were – they make facilitation and instruction look easy!

The first Leadership Institute was hosted by The Ohio State University Library. Ohio in the middle of December was a truly invigorating experience. I learned a great deal about all kinds of management issues, including emotional intelligence and conflict resolution, and had opportunities to hear from library leaders such as Damon Jaggars, John Cawthorne, Jose Diaz, Deidra Herring, and Alexia Hudson-Ward. We also received a fantastic tour of their newly renovated flagship Thompson Memorial Library. This library reminded me of the Roman god, Janus, with two faces – one that looked to the past and another that looked to the future. One side of the library had a more traditional façade, consistent with the campus’s more stately frontages, and the other side had a modern look, built primarily with concrete, metal, and glass. What an amazing building that seamlessly combined their vibrant traditions with ambitious modernity. My career coach, Eileen Theodore-Shusta, from Ohio University, even drove up to meet me for dinner in Columbus, Ohio! What a treat it was to have met my career coach so early in the process! The company and the food were fantastic. It was such a hoot to have frozen custard in the middle of winter!

Interior view of the Thompson Library. Image by Brad Feinknopf via Elledecor.com

The second Leadership Institute was hosted by the University of Alberta, in Edmonton, Canada. What a lovely sight to see the Canadian plains in full bloom during May. Interestingly too (since I had never visited Canada at this time of year), the sun didn’t set until 10:00 pm! That was a slightly crazy insomnia-inducing experience. This Leadership Institute was facilitated by Kathryn Deiss and Melanie Hawks. As one of the founders of the Minnesota Leadership Institute, Kathryn shared her experiences and thoughts on diversity, equity, and inclusivity. We also learned a great deal from University of Alberta Libraries’ University Librarian, Dale Askey, and his professional journey. Preparation, perseverance, ambition, and risk-taking. All those words, and some more, crystallized my impression of that conversation.

View of the Kairos Blanket exercise. Image from kairosblanketexercise.org

The stand-out experience of this institute, I believe, was the Kairos Blanket exercise.  This was an immersive exercise that the entire cohort participated in. We began with a full house and quickly saw members of our group expelled from our respective lands either by death, disease, or governmental mandates (of course this was all pretend, but it was still quite striking). The group also read out loud the past experiences of First Nation Communities. To hear these stories of resilience against systematic violence and loss uttered by voices from the cohort members, was stark and emotional. This link provides more information about the program. The Kairos Blanket exercise, along with revelations on the Canadian government’s approach towards reconciliation with First Nation communities (aka Native Americans in the US) were deeply informative.

There were several highlights in the program beyond the events that we attended. Each LCDP Fellow underwent a Leadership Practices Inventory, a 360 assessment of our leadership skills. This assessment involved our reporting officer, our colleagues, and our direct reports. This was an incredibly enlightening experience, as many of us had not undergone such a review of this detail before.

Giao with her Career Coach, Eileen Theodore-Shusta, at Ohio University.

Also, each LCDP Fellow was paired up with a Career Coach – a librarian in a leadership role – who provided us insights into leadership and administration. As part of this program, the Career Coach would host their fellow at their institution. I had the wonderful opportunity to be paired with Eileen Theodore-Shusta of Ohio University. As the Director of Planning, Assessment, and Organizational Effectiveness at Ohio University, Eileen provided me valuable insights into library administration and management from a Human Resource perspective. What a fantastic visit to the beautiful Ohio University campus as well. I visited their Archives, Special Collections, Digital Archives, and even perused their Southeast Asia Collection.

Another integral piece to the LCDP experience was the Equity Toolkit. In between the institutes, we had  webinars and lessons from the Equity Toolkit, created by DeEtta Jones and Associates. This Toolkit included modules on Cultural Competence, Bias in the Workplace, and The Inclusive Manager. Using a combination of videos, text, quizzes and reflections, the Equity Toolkit was chock full of information and revelations. Also, this portion of the program included webinars where LCDP fellows and their career coaches were invited , as well as their supervisors, and the up-line administrators. The objective was to not only “preach to the choir”, but to include allies and influential voices in the discussion.

At last, the Capstone Leadership Institute in Washington DC, was the finale as we said our goodbyes. The Capstone was also a new beginning as we adopted our moniker, The Disruptors. We attended the ARL Directors’ evening reception and sat alongside library directors in the Fall  ARL Association meeting. Jennifer Garrett, Director of Talent Management at North Carolina State University, eloquently highlighted the ARL LCDP experience to these Library Directors, and Elaine Westbrooks, the University Librarian of UNC Chapel Hill’s Library, spoke about her time as a career coach and perfectly bookended the speech with her memories as a former ARL LCDP fellow. After all the celebrations, we reconvened, reminisced, and planned for the challenges and opportunities before us. 

The 2018-2019 ARL LCDP cohort in Ohio University. Image from arl.org.

How do we continue this journey? One step at a time. With each other.

Thank you to my former dean, Catherine Quinlan at the University of Southern California, and Duke University Libraries for your support and encouragement. It is on the shoulders of giants (and forward thinking institutions) that I see the world of great challenges and opportunities before me.

 

 

New Digitization Initiative and Call for Proposals

Two years ago, Duke Libraries Advisory Council for Digital Collections launched a new process for proposing digitization projects.  Previously the group accepted new digitization proposals every month. We decided to shift to a “digitization initiative” approach where the Council issues a time-based call for proposals focusing on a theme or format. This new method has allowed staff across different departments to plan and coordinate their efforts more effectively.  

This Fall we are inviting DUL staff to propose Audio and Video (A/V) based collections/items for digitization. DUL staff are welcome to partner with Duke Faculty on their proposals. We chose to focus on A/V formats this year due to the preservation risks associated with the material. Magnetic tape formats are especially fragile compared to film given their composition, and the low availability of players for accessing content.  

The complete call for proposals including criteria and a link to the proposal form is online.  Proposals should be submitted on or before November 18

What about non-A/V digitization proposals? 

The Advisory Council is working on another call for digitization proposals, which is intended to include non-A/V formats (manuscripts, photographs, and more).  We should be able to announce the new call before the end of the calendar year.  Stay tuned!

DUL staff can also submit proposals for small digitization projects anytime as long as they fit the criteria for an “easy” project. Easy projects are small in size and scope and include a wide range of formats; complete guidelines are online along with the proposal form.

 

Lighting and the PhaseOne: It’s More Than Point and Shoot

Last week, I went to go see the movie IT: Chapter 2. One thing I really appreciated about the movie was how it used a scene’s lighting to full effect. Some scenes are brightly lit to signify the friendship among the main characters. Conversely, there are dark scenes that signify the evil Pennywise the Clown. For the movie crew, no doubt it took a lot of time and manpower to light an individual scene – especially when the movie is nearly 3 hours long.

We do the same type of light setup and management inside the Digital Production Center (DPC) when we take photos of objects like books, letters, or manuscripts. Today, I will talk specifically about how we light the bound material that comes our way, like books or booklets. Generally, this type of material is always going to be shot on our PhaseOne camera, so I will particularly highlight that lighting setup today.

Before We Begin

It’s not enough to just turn the lights on in our camera room to do the trick. In order to properly light all the things that need to be shot on the PhaseOne, we have specific tools and products we use that you can see in the photo below.

We have 4 high-powered lights (two sets of two Buhl SoftCube SC-150 models) pointed directly in the camera’s field of view. There are two on the right and two on the left. These are stationed approximately 3.5 feet off the ground and approximately 2.5 feet away from the objects themselves. These lights are supported by Avenger A630B light stands. They allow for a wide range of movement, extension, and support if we need them.

But if bright, hot lights were pointed directly at sensitive documents for hours, it would damage them. So light diffusers are necessary. For both sets of lights, we have 3 layers of material to diffuse the light and prevent material from warping or text from fading. The first layer, directly attached to the light box itself, is an inexpensive sheet of diffusion fabric. This type of material is often made from nylon or silk, and are usually inexpensive.

The second diffusion layer is an FJ Westcott Scrim Jim, a similar thin fabric that is attached to a lightweight stand-up frame, the Manfrotto 156BLB. This frame can also be moved or extended if need be. The last layer is another sheet of diffusion fabric, attached to a makeshift “cube” held up by lightweight wooden rods. This cube can be picked up or carried, making it very convenient if we need to eventually move our lights.

So in total, we have 4 lights, 4 layers of diffusion fabric attached to the light boxes, two Scrim Jims, and the cube featuring 2 sides of additional diffusion fabric. After having all these items stationed, surely we can start taking pictures, right? Not yet.

Around the Room

There are still more things to be aware of – this time in the camera room itself. We gently place the materials themselves on a cradle lined with a black felt, similar to velvet. This cradle is visible in the bottom right part of the photo above. It is placed on top of a table, also coated in black felt. This is done so no background colors bounce back or reflect onto the object and change what it looks like in the final image itself. The walls of the camera room are also painted a neutral grey color for the same reason, as you can see in the background of the above photo. Finally, any tiny reflective segments between the ceiling tiles have been blacked out with gaffer tape. Having the room this muted and intentionally dark also helps us when we have to shoot multi-spectral images. No expense has been spared to make sure our colors and photos are correct.

Camera Settings

With all these precautions in place, can we finally take photos of our materials? Almost. Before we can start photographing, we have to run some tests to make sure everything looks correct to our computers. After making sure our objects are sharp and in focus, we use a program called DTDCH (see the photo to the right) to adjust the aperture and exposure of the PhaseOne so that nothing appears either way too dim or too bright. In our camera room, we use a PhaseOne IQ180 with a Schneider Kreuznach Apo-Digitar lens (visible in the top-right corner of the photo above). We also use the program CaptureOne to capture, save, and export our photos.

Once the shot is in focus and appropriately bright, we will check our colors against an X-Rite ColorChecker Classic card (see the photo on the left) to verify that our camera has a correct white balance. When we take a photo of the ColorChecker, CaptureOne displays a series of numbers, known as RGB values, found in the photo’s colors. We will check these numbers against what they should be, so we know that our photo looks accurate. If these numbers match up, we can continue. You could check our work by saving the photo on the left and opening it in a program like Adobe Photoshop.

Finally, we have specific color profiles that the DPC uses to ensure that all our colors appear accurate as well. For more information on how we consistently calibrate the color in our images, please check out this previous blog post.

After all this setup, now we can finally shoot photos! Lighting our materials for the PhaseOne is a lot of hard work and preparation. But it is well worth it to fulfill our mission of digitizing images for preservation.

What we talk about when we talk about digital preservation

(Header image: Illustration by Jørgen Stamp digitalbevaring.dk CC BY 2.5 Denmark)

Here at Duke University Libraries, we often talk about digital preservation as though everyone is familiar with the various corners and implications of the phrase, but “digital preservation” is, in fact, a large and occasionally mystifying topic. What does it mean to “preserve” a digital resource for the long term? What does “the long term” even mean with regard to digital objects? How are libraries engaging in preserving our digital resources? And what are some of the best ways to ensure that your personal documents will be reusable in the future? While the answers to some of these questions are still emerging, the library can help you begin to think about good strategies for keeping your content available to other users over time by highlighting agreed-upon best practices, as well as some of the services we are able to provide to the Duke community.

File formats

Not all file formats have proven to be equally robust over time! Have you ever tried to open a document created using a Microsoft Office product from several years ago, only to be greeted with a page full of strangely encoded gibberish? Proprietary software like the products in the Office suite can be convenient and produce polished contemporary documents. But software changes, and there is often no guarantee that the beautifully formatted paper you’ve written using Word will be legible without the appropriate software 5 years down the line. One solution to this problem is to always have a version of that software available to you to use. Libraries are beginning to investigate this strategy (often using a technique called emulation) as an important piece of the digital preservation puzzle. The Emulation as a Service (EaaS) architecture is an emerging tool designed to simplify access to preserved digital assets by allowing end users to interact with the original environments running on different emulators.

An alternative to emulation as a solution is to save your files in a format that can be consumed by different, changing versions of software. Experts at cultural heritage institutions like the Library of Congress and the US National Archives and Records Administration have identified an array of file formats about which they feel some degree of confidence that the software of the future will be able to consume. Formats like plain text or PDFs for textual data, value separated files (like comma-separated values, or CSVs), MP3s and MP4s for audio and video data respectively, and JPEGs for still images have all proven to have some measure of durability as formats. What’s more, they will help to make your content or your data more easily accessible to folks who do not have access to particular kinds of software. It can be helpful to keep these format recommendations in mind when working with your own materials.

File format migration

The formats recommended by the LIbrary of Congress and others have been selected not only because they are interoperable with a wide variety of software applications, but also because they have proven to be relatively stable over time, resisting format obsolescence. The process of moving data from an obsolete format to one that is usable in the present day is known as file format migration or format conversion. Libraries generally have yet to establish scalable strategies for extensive migration of obsolete file formats, though it is generally a subject of some concern.

Here at DUL, we encourage the use of one of these recommended formats for content that is submitted to us for preservation, and will even go so far as to convert your files prior to preservation in one of our repository platforms where possible and when appropriate to do so. This helps us ensure that your data will be usable in the future. What we can’t necessarily promise is that, should you give us content in a file format that isn’t one we recommend, a user who is interested in your materials will be able to read or otherwise use your files ten years from now. For some widely used formats, like MP3 and MP4, staff at the Libraries anticipate developing a strategy for migrating our data from this format, in the event that the format becomes superseded. However, the Libraries do not currently have the staff to monitor and convert rarer, and especially proprietary formats to one that is immediately consumable by contemporary software. The best we can promise is that we are able to deliver to the end users of the future the same digital bits you initially gave to us.

Bit-level preservation

Which brings me to a final component of digital preservation: bit-level preservation. At DUL, we calculate a checksum for each of the files we ingest into any of our preservation repositories. Briefly, a checksum is an algorithmically derived alphanumeric hash that is intended to surface errors that may have been introduced to the file during its transmission or storage. A checksum acts somewhat like a digital fingerprint, and is periodically recalculated for each file in the repository environment by the repository software to ensure that nothing has disrupted the bits that compose each individual file. In the event that the re-calculated checksum does not match the one supplied when the file has been ingested into the repository, we can conclude with some level of certainty that something has gone wrong with the file, and it may be necessary to revert to an earlier version of the data. THe process of generating, regenerating, and cross-checking these checksums is a way to ensure the file fixity, or file integrity, of the digital assets that DUL stewards.

Resonance of a Moment

Resonance: the reinforcement or prolongation of sound by reflection from a surface or by the synchronous vibration of a neighboring object

(Lexico, 2019)

Nearly 4 months have passed since I moved to Durham from my hometown Chicago to join Duke’s Digital Collections & Curation Services team. With feelings of reflection and nostalgia, I have been thinking on the stories and memories that journeys create.

I have always believed a library the perfect place to discover another’s story. Libraries and digital collections are dynamic storytelling channels that connect people through narrative and memory. What are libraries if not places dedicated to memories? Memory made incarnate in the turn of page, the capturing of an image.

Memory is sensation.

In my mind memory is ethereal – wispy and nebulous. Like trying to grasp mist or fog only to be left with the shimmer of dew on your hands. Until one focuses on a detail, then the vision sharpens. Such as the soothing warmth of a pet’s fur. A trace of familiar perfume in the air as a stranger walks by. Hearing the lilt of an accent from your hometown. That heavy, sticky feeling on a muggy summer day.

Memories are made of moments.

I do not recall the first time I visited a library. However, one day my parents took me to the library and I checked out 11 books on dinosaurs. As a child I was fascinated by them. Due to watching so much of The Land Before Time and Jurassic Park no doubt. One of the books had beautiful full-length pullout diagrams. I remember this.

Experiences tether individuals together across time and place. Place, like the telling of a story is subjective. It holds a finite precision which is absent in the vagueness and vastness of space. This personal aspect is what captures a person when a tale is well told.  A corresponding chord is struck, and the story resounds as listeners see themselves reflected.

When a narrative reaches someone with whom it resonates, its impact can be amplified beyond any expectations.

There are many unique memories and moments held in the Duke University Libraries digital collections. Come take a journey and explore a new story.

My humanity is bound up in yours, for we can only be human together. ~Desmond Tutu

Notes from the Duke University Libraries Digital Projects Team