A New & Improved Rubenstein Library Website

We kicked off the spring 2018 semester by rolling out a brand-new design for the David M. Rubenstein Library website.  The new site features updated imagery from the collections, better navigation, and more prominent presence for the exhibits currently on display.

Rubenstein website, Jan 2018
January 2018: New design for the Rubenstein Library homepage.

 

Much credit goes to Katie Henningsen and Kate Collins who championed the project.

Objectives for the Redesign

  • Make wayfinding from the homepage clearer (by reorganizing links into a primary dropdown navigation)
  • Dynamically feature Rubenstein Library exhibits that are currently on display
  • Improve navigation to key Rubenstein site pages from within research center / collection pages
  • Display larger images illustrative of the library’s distinctive and diverse collections
  • Retain aspects of the homepage that have been effective, e.g., hours and resource search boxes
  • Improve the site aesthetic

Internal Navigation

With a new primary navigation in hand on the Rubenstein homepage that links to key pages in the site, we began to explore ways to get visitors to those links in an unobtrusive way when they aren’t on the homepage.  Each research center within the library, e.g., the John W. Hartman Center for Sales, Advertising & Marketing History, has its own sub-site with its own secondary menus, which already contend a bit with the blue Duke Libraries menu in the masthead.  To avoid burying visitors in a Russian nesting doll of navigation, we decided to try dropping the RL menu down from the breadcrumb trail link so it’s tucked away, but still accessible when needed. We’re eager to learn whether or not this is effective.

Rubenstein primary navigation menu available from breadcrumb trail.

A Look Back

Depending on how you count, this is now the seventh or eighth homepage design for the Rubenstein Library (formerly the Rare Book, Manuscript, and Special Collections Library; formerly the Special Collections Library). I thought I’d take a quick stroll down memory lane, courtesy of the Internet Archive’s Wayback Machine, to reflect on how far we have come over the years.

1996

Duke Special Collections Library website, 1996
October 1996 (explore)

Features:

  • prominent news, exhibits, and online collections
  • links to online SGML- and HTML-encoded finding aids (42 of them!)
  • a site search box powered by Excite!

1997

April 1997 (explore)

Features:

  • two-column layout with a left-hand nav
  • digitized collections
  • a special collections newsletter called The Broadside
  • became the “Rare Book, Manuscript, and Special Collections Library” in 1997

2005

December 2005 (explore Jan 2006)

Features:

  • color-coded navigation broken into three groups of links
  • image from the collections
  • featured exhibit with image
  • rounded corners and shadows
  • first use of a CMS (content management system named Cascade Server)*

2007

August 2007 (explore)

Features:

  • first time sharing a masthead with rest of the Duke University Libraries
  • retained the lists of links, single collection image, and featured exhibit from previous iteration

2011

September 2011 (explore)

Features:

  • renamed as the David M. Rubenstein Rare Book & Manuscript Library
  • first time with catalog and finding aids search boxes on the homepage
  • first appearance of social media & RSS icons
  • first iteration to display library hours
  • first news carousel appearance

2014

January 2014 (explore)

Features:

  • new site in Drupal content management system
  • first responsive RL website (works well on mobile devices)
  • array of vertical image panels from the collections
  • extended color palette to match Duke University website styles (at the time)
  • gradients and rounded buttons with shadows
  • first time able to search digital collections from RL homepage
  • first site with Login button for Aeon (Special Collections request system)

2017

January 2017 (explore)

Features:

2018

Rubenstein website, Jan 2018
January 2018

Features

  • lightened the overall aesthetic
  • featured image cycling from selections at random (diagonally sliced using css clip-path polygons)
  • prominent current exhibits feed with images
  • a primary nav with dropdown menus

How long will this latest edition of the Rubenstein Library homepage stick around? Only time will tell, but we’ll surely continue to iterate, learn from the past, and improve with each attempt. For now, we’re pleased with the new site, and hope you will be as well.


* Revised Feb 9, 2018 to reflect that the first version using a content management system was in 2005 rather than 2007.

Hugh Mangum, Family and 100 years

What could me growing up in South West Virginia have to do with an itinerant photographer from Durham who was born in 1877?  His name was Hugh Mangum and he had a knack for bringing out the personalities of his subjects when, at the time, most photographs depict stiff and stoic people similar to the photograph below.

Hugh Mangum N475

We all have that family photo, taken with siblings, cousins or friends, that captures a specific time in our life or a specific feeling where you think to yourself “look at us” and just shake your head in amazement.  These photographs trigger memories that trigger other memories.  The photo below is that for me.  These are my siblings and cousins at my grandparents’ house in the early 90’s.  My siblings and I grew up on the same street as my grandparents and my cousins in the town of Blacksburg Virginia.  It seemed like we were always together but oddly there are very few pictures of all of us in one shot.

Adamo siblings and cousins circa 1990.

Even though this photograph was taken only a few decades ago a lot has changed in the lives of everyone in this photograph and also in the world of photography.  This picture was taken using ‘traditional’ film where, after taking the picture, you had to rewind the film, drop it off at the Fotomat to get your film processed and prints made before you could even see the images! We never knew if we had a “good” shot until days, sometimes weeks after an event.

Here is where my path intersects with Hugh Mangum.  We recently digitized some additional glass plate negatives from the Hugh Mangum collection.  Hugh was an itinerant photographer that traveled throughout North Carolina, Virginia and West Virginia.  In Virginia he traveled to Christiansburg, Radford and Roanoke.  These cities surround my hometown on three sides (respectively 8, 15 and 38 miles away).  These images were taken from 1890 to 1922.  This would put him in the area about 100 years before the family photo above.  I wonder if he passed through Blacksburg?

Hugh Mangum negatives N574, N576, N650.

Fast forward to 2018.  We carry computers in our pockets that have cameras that can capture every aspect of our lives.  We have social media sites where we post, share, tag, comment and record our lives.  I bet that even though we can now take thousands of photographs a year there are still the keepers.  The ones that rise to the top.  The ones that capture a moment in such a way that the younger generations might just say to themselves one day “look at us” and shaking their heads.

 

 

Snow Daze: Winter Weather Survival Tips

Snow is a major event here in North Carolina, and the University and Library were operating accordingly under a “severe weather policy” last week due to 6-12 inches of frozen precipitation. While essential services continued undeterred, most of the Library’s staff and patrons were asked to stay home until conditions had improved enough to safely commute to and navigate the campus. In celebration of last week’s storm, here are some handy tips for surviving and enjoying the winter weather–illustrated entirely with images from Duke Digital Collections!

  1. Stock up on your favorite vices and indulgences before the storm hits.

2. Be sure to bundle and layer up your clothing to stay warm in the frigid outdoor temperatures.

3. Plan some fun outdoor activities to keep malaise and torpor from settling in.

4. Never underestimate the importance of a good winter hat.

5. While snowed in, don’t let your personal hygiene slip too far.

6. Despite the inconveniences brought on by the weather, don’t forget to see the beauty and uniquity around you.

7. If all else fails, escape to sunnier climes.

8. Be thankful that Spring is on the way!

The images in this post are taken from the following digitized collections:  J. Walter Thompson Ford Motor Co. Advertisements, Ad*Access, William Gedney Photographs and Writings, Paul Kwilecki PhotographsW. Duke, Sons & Co. Advertising Materials, and Americans in the Land of Lenin: Documentary Photographs of Early Soviet Russia.

Stay warm!

Upgrading DukeSpace

The year 2006 was charged with epoch-defining events: Zidane head-butted Materazzi, the astronomers downgraded Pluto, Google bought Youtube, and Duke University Libraries rolled out DukeSpace (PDF). Built on the DSpace platform, DukeSpace has served as our institutional repository for almost a dozen years now, providing access for electronic theses and dissertations and Duke faculty publications.

While the landscape of open access has changed much over the intervening period, we can’t really say the same about the underlying platform of DukeSpace.

At Duke, faculty approved an open access policy in March of 2010; it was a few weeks previous that DSpace 1.6 was released. By the end of the year it had moved ahead a dot release to 1.7.  Along the way, we did some customization to integrate with Symplectic Elements – the Research Information Management System (RIMS) that powers the Scholars@Duke site. That work essentially locked us into that version of DSpace, which remains in operation despite its final release in July 2013, and having reached its end of life four years ago.

Animated GIF of Zinedine Zidane head-butting an opponent in the final game of the 2006 FIFA World Cup.
If only I had the skills to photoshop DSpace 6.2 in for Zidane, and 1.7 for Materazzi. GIF from Something Awful.

Beginning last November, we committed to a full upgrade of the DukeSpace platform to the current version (6.2 as of this writing). We had considered alternatives, including replacing the platform with Hyrax, but concluded that that approach would be too complex.

So we are currently coordinating work across a technology team and the Libraries’ open access group. Some of the concerns that we have encountered include:

  • Integrating with updated versions of Symplectic Elements. That same integration that locked us into a version years ago lies at the center of this upgrade. We have basically been handling this process as a separate thread of the larger project. It will be critical for us to maintain the currency of this dependency with subsequent upgrades to both products.
  • Rethinking metadata architecture. The conceptual basis of the institutional repository is greatly informed by the definition and use of metadata. Our Metadata Architect, Maggie Dickson, mentioned this area in her “Metadata Year-in-Review” post back in December. She highlighted the need to make “real headway tackling the problem of identity management – leveraging unique identifiers for people (ORCIDs, for example), rather than relying on name strings, which is inherently error prone.” Many other questions have arisen this area, requiring extensive and ongoing discussion and coordination between the tech team and the stakeholders.
  • Migration of legacy stats data. How do we migrate usage stats between two versions of a platform so remote from each other in time? It has taken some trial-and-error to solve this one.
  • Replicating or enhancing existing workflows. Again, when two versions of a system are so different that an upgrade seems more like a platform migration, and our infrastructure and staffing have changed over the years, how do we reproduce existing workflows without disrupting them? What opportunities can we take to improve on them without destabilizing the project? Aside from the integration with Elements, we also have the important workflow related to the ingest of electronic theses & dissertations, which employs both self-deposit and file transfer from ProQuest. Re-envisioning and re-implementing workflows such as these takes careful analysis and planning.

While we have run into a few complicating issues during the process so far, we feel confident that we remain on track to roll out the upgraded version during the first quarter of 2018. Pluto remains a dwarf planet, Zidane manages Real Madrid (for now),  and to Mark Cuban’s apparent distress, Google still owns Youtube. Soon our own story from 2006 should reach a kind of resolution.

Photograph of the surface of Pluto, taken by the New Horizons spacecraft.
“Pluto’s Majestic Mountains, Frozen Plains and Foggy Hazes” – Image from NASA. Credits: NASA/JHUAPL/SwRI.

 

Moving the mountain (of data)

It’s a new year! And a new year means new priorities. One of the many projects DUL staff have on deck for the Duke Digital Repository in the coming calendar year is an upgrade to DSpace, the software application we use to manage and maintain our collections of scholarly publications and electronic theses and dissertations. As part of that upgrade, the existing DSpace content will need to be migrated to the new software. Until very recently, that existing content has included a few research datasets deposited by Duke community members. But with the advent of our new research data curation program, research datasets have been published in the Fedora 3 part of the repository. Naturally, we wanted all of our research data content to be found in one place, so that meant migrating the few existing outliers. And given the ongoing upgrade project, we wanted to be sure to have it done and out of the way before the rest of the DSpace content needed to be moved.

The Integrated Precipitation and Hydrology Experiment

Most of the datasets that required moving were relatively small–a handful of files, all of manageable size (under a gigabyte) that could be exported using DSpace’s web interface. However, a limited series of data associated with a project called The Integrated Precipitation and Hydrology Experiment (IPHEx) posed a notable exception. There’s a lot of data associated with the IPHEx project (recorded daily for 7 years, along with some supplementary data files, and iterated over 3 different areas of coverage, the total footprint came to just under a terabyte, spread over more than 7,000 files), so this project needed some advance planning.

First, the size of the project meant that the data were too large to export through the DSpace web client, so we needed the developers to wrangle a behind the scenes dump of what was in DSpace to a local file system. Once we had everything we needed to work with (which included some previously unpublished updates to the data we received last year from the researchers), we had to make some decisions on how to model it. The data model used in DSpace was a bit limiting, which resulted in the data being made available as a long list of files for each part of the project. In moving the data to our Fedora repository, we gained a little more flexibility with how we could arrange the files. We determined that we wanted to deviate slightly from the arrangement in DSpace, grouping the files by month and year.

This meant we would have group all the files into subdirectories containing the data for each month–for over 7,000 files, that would have been extremely tedious to do by hand, so we wrote a script to do the sorting for us. That completed, we were able to carry out the ingest process as normal. The final wrinkle associated with the IPHEx project was making sure that the persistent identifiers each part of the project data had been assigned in DSpace still resolved to the correct content. One of our developers was able to set up a server redirect to ensure that each URL would still take a user to the right place. As of the new year, the IPHEx project data (along with our other migrated DSpace datasets) are available in their new home!

At least (of course) until the next migration.

A Year in the Life of Digital Collections

2017 has been an action packed year for Digital Collections full of exciting projects, interface developments and new processes and procedures. This blog post is an attempt to summarize just a few of our favorite accomplishments from the last year. Digital Collections is truly a group cross-departmental collaboration here at Duke, and we couldn’t do complete any of the work listed below without all our colleagues across the library – thanks to all!

New Digital Collections Portal

Regular visitors to Duke Digital Collections may have noticed that our old portal (library.duke.edu/digitalcollections/) now redirects to our new homepage on the Duke Digital Repository (DDR) public interface. We are thrilled to make this change! But never fear, your favorite collections that have not been migrated to DDR are still accessible either on our Tripod2 interface or by visiting new placeholder landing pages in the Digital Repository.

Audiovisual Features

Supporting A/V materials in the Digital Repository has been a major software development priority throughout 2017. As a result our A/V items are becoming more accessible and easier to share. Thanks to a year of hard work we can now do and support the following (we posted examples of these on a previous post).

  • Model, store and stream A/V derivatives
  • Share A/V easily through our embed feature (even on Duke WordPress sites- a long standing bug)
  • Finding aids can now display inline AV for DAOs from DDR
  • Clickable timecode links in item descriptions (example)
  • Display captions and interactive transcripts
  • Download and Export captions and transcripts (as .pdf, .txt.,or .vtt)
  • Display Video thumbnails & poster frames

Rights Statements and Metadata

Bitstreams recently featured a review of all things metadata from 2017, many of which impact the digital collections program. We are especially pleased with our rights management work from the last year and our rights statements implementation (http://rightsstatements.org/en/). We are still in the process of retrospectively applying the statements, but we are making good progress. The end result will give our patrons a clearer indication of the copyright status of our digital objects and how they can be used. Read more about our rights management work in past Bitstreams posts.

Also this year in metadata, we have been developing integrations between ArchivesSpace (the tool Rubenstein Library uses for finding aids) and the repository (this is a project that has been in the works since 2015. With these new features Rubenstein’s archivist for metadata and encoding is in the process of reconciling metadata between ArchivesSpace and the Digital Repository for approximately 50 collections to enable bi-directional links between the two systems. Bi-directonal linking helps our patrons move easily from a digital object in the repository to its finding aid or catalog record and vice versa. You can read about the start of this work in a blog post from 2016.

MSI

At the end of 2016, Duke Libraries purchased Multispectral Imaging (MSI) equipment, and members of Digital Collections, Data and Visualization Studies, Conservation Services, the Duke Collaboratory for Classics Computing, and the Rubenstein Library joined forces to explore how to best use the technology to serve the Duke community. The past year has been a time of research, development, and exploration around MSI and you can read about our efforts on Bitstreams. Our plan is to launch an MSI service in 2018. Stay tuned!

Ingest into the Duke Digital Repository (DDR)

With the addition of new colleagues focussed on research data management, there have been more demands on and enhancements to our DDR ingest tools. Digital collections has benefited from more robust batch ingest features as well as the ability to upload more types of files (captions, transcripts, derivatives, thumbnails) through the user interface. We can also now ingest nested folders of collections. On the opposite side of the spectrum we now have the ability to batch export sets of files or even whole collections.

Project Management

The Digital Collections Advisory Committee and Implementation Team are always looking for more efficient ways to manage our sprawling portfolio of projects and services. We started 2017 with a new call for proposals around the themes of diversity and inclusion, which resulted in 7 successful proposals that are now in the process of implementation.

In addition to a thematic call for proposals, we later rolled out a new process for our colleagues to propose smaller projects in response to faculty requests, events or for other reasons. In other words, projects of a certain size and scope that were not required to respond to a thematic call for proposals. The idea being that these projects can be easily implemented, and therefore do not require extensive project management to complete. Our first completed “easy” project is the Carlo Naya photograph albums of Venice.

In 2016 (perhaps even back in 2015), the digital collections team started working with colleagues in Rubenstein to digitize the set of collections known in as “Section A”. The history of this moniker is a little uncertain, so let me just say that Section A is a set of 3000+ small manuscript collections (1-2 folders each) boxed together; each Section A box holds up to 30 collections. Section A collections are highly used and are often the subject of reproduction requests, hence they are perfect candidates for digitization. Our goal has been to set up a mass-digitization pipeline for these collections, that involves vetting rights, updating description, evaluating their condition, digitizing them, ingesting them into DDR, crosswalking metadata and finally making them publicly accessible in the repository and through their finding aids. In 2017 we evaluated 37 boxes for rights restrictions, updated descriptions for 24 boxes, assessed the condition of 31 boxes, digitized 19 boxes, ingested 4 boxes, crosswalked metadata for 2 boxes and box 1 is now online! Read more about the project in a May Bitstreams post. Although progress has felt slow given all the other projects we manage simultaneously, we really feel like our foot is on the gas now!

You can see the fruits of our digital collection labors in the list of new and migrated collections from the past year. We are excited to see what 2018 will bring!!

New Collections Launched in 2017

Migrated Collections

‘Tis the Season for New Beginnings

New Additions

Brief summaries of articles pulled from a future digitized issue published by The Chronicle, as part of the 1990s Duke Chronicle Digitization Project

The time has come for the temperature to drop, decadent smells to waft through the air, and eyes become tired and bloodshot. Yep, it’s exam week here at Duke! As students fill up every room, desk and floor within the libraries, the Digital Collections team is working diligently to process important projects.

One such project is the 1990s decade of The Duke Chronicle. By next week, we can look forward to the year 1991 being completely scanned. Although there are many steps involved before we can make this collection available to the public, it is nice to know that this momentous year is on its way to being accessible for all. While scanning several issues today, I noticed the last issue for the fall semester of 1991. It was the Exam Break Issue, and I was interested in the type of reading content published 26 years ago. What were the students of Duke browsing through before they scurried back home on December 16, 1991, you may ask…

  • There were several stories about students’ worst nightmares coming true, including one Physical Therapy graduate student who lost her research to a Greyhound bus, and an undergraduate dumpster diving to find an accidentally thrown away notebook, which encompassed his final paper.
  • A junior lamented whether it was worth it to drive 12 hours to his home in Florida, or take a plane after a previous debacle in the air; he drove home with no regrets.
  • In a satirical column, advice was given on how to survive exams. Two excellent gems suggested using an air horn instead of screaming and staking out a study carrel, in order to sell it to the highest bidder.

This is merely a sprinkling of hilarious yet simultaneously horrifying anecdotes from that time-period.

Updates to Existing Collections

Digital collections, originally located on the old Digital Collections website, now have new pages on the Repository website with a direct link to the content on the old website.

In addition to The Chronicle, Emma Goldman Papers, and other new projects, there is a continued push to make already digitized collections accessible on the Repository platform. Collections like Behind the Veil, Duke Papyrus Archive, and AdViews were originally placed on our old Digital Collections platform. However, the need to provide access is just as relevant today as when they were originally digitized.

As amazing as our current collections in the Repository are, we have some treasures from the past that must be brought forward. Accordingly, many of these older digital collections now possess new records in the Repository! As of now, the new Repository pages will not have the collections’ content, but they will provide a link to enable direct access.

New Page:

Vs.

Old Page:

The new pages will facilitate exposure to new researchers, while permitting previous researchers to use the same features previously allowed on the old platform. There are brief descriptions, direct links to the collections, and access to any applicable finding aids on the Repository landing pages.

Now that the semester has wound down to a semi-quiet lull of fattening foods, awkward but friendly functions, and mental recuperation, I urge everyone to take a moment to not just look at what was done, but all the good work you are planning to do.

Based on what I’ve observed so far, I’m looking forward to the new projects that Digital Collections will be bringing to the table for the Duke community next year.

 

 

References

Kueber, G. (1991). Beginning of exams signals end of a Monday, Monday era. The Duke Chronicle, p. 26.

Robbins, M. (1991). Driving or crying: is air travel during the holidays worth it? The Duke Chronicle, p. 13.

The Duke Chronicle. (1991). The Ultimate Academic Nightmares – and you thought you were going to have a bad week! pp. 4-5.

Metadata Year-in-Review

As 2017 comes to a close and we gear up for the new year, I’ve spent some time reflecting on the past twelve months. Because we set ambitious goals and are usually looking forward, not back, we can often feel defeated by all the work we haven’t gotten done. So I was pleasantly surprised when my perusal of the past year’s metadata work surfaced a good deal of impressive work. Here are a few of the highlights:

Development and Dissemination of the DDR MAP

Perhaps our biggest achievement of the year was the development of the DDR’s very first formally documented metadata application profile, the DDR MAP. A metadata application profile defines the metadata elements and properties your system uses, documenting predicates, obligations & requirements, and input guidelines. Having a documented and shared metadata application profile promotes healthy metadata practices and facilitates communication.

In addition to the generalized DDR MAP, we also developed a Research Data Metadata Profile and a Digital Collections Metadata Profile for those specific collecting areas.

Rights Management Metadata

It’s been written about on this blog a couple of times already (here and here) but I think it bears repeating: this year we rolled out a new rights management metadata strategy that employs the application of either a Creative Commons or RightsStatement.org URI to all DDR resources, as well as the option of applying an additional free text rights note to provide context:

We feel great about finally being able to communicate the rights statuses of DDR resources in a clear and consistent way to our end-users (and ourselves!).

Programmatic Linking to Catalog Records

Sometimes a resource in the DDR also has a record in the library catalog, and sometimes that record contains description that is either not easily accommodated by the DDR MAP, or it is not desirable to include it in the repository metadata record for a particular reason. It wasn’t in the cards to develop a synchronization or feed of the MARC metadata, but we were able to implement a solution wherein we store the identifier for the catalog record on the resource in the repository, and then use that identifier to construct and display a link back to the catalog record.

And Lots of Other Cool Stuff

There were a lot of other cool metadata developments this year, including building out our ability to represent relationships between related items in the DDR, developing policies regarding the storage and display of identifiers, and a fancy new structural metadata solution for representing the hierarchical structure of born digital archives. We also got to work on some amazing new and revamped digital collections!

Looking Ahead

Of course, we are setting ambitious goals for the coming year as well – plans to upgrade our current Dspace repository, DukeSpace, and implement the new RT2 connector to Elements, will involve substantial metadata work, and the current project to build a Hyrax-based repository for research data presents and opportunity for us to revisit and improve our Research Data Metadata Profile. And ideally we will be able to make some real headway tackling the problem of identity management – leveraging unique identifiers for people (ORCIDs, for example), rather than relying on name strings, which is inherently error prone.

And there is a whole slew of interesting metadata work for the Digital Collections program slated for 2018 , including adding enhanced homiletic metadata to the Duke Chapel Recordings digital collection.

Institutional multispectral imaging (MSI) survey results

Over the last year and a half, we’ve blogged quite a bit about our exploration of multispectral imaging (MSI) here at Duke Libraries. We’ve written about the hardware and software that we acquired in 2016 and about our collaboration and training to help us learn how to use this new equipment. We’ve shared examples from our experiments with MSI on various material and ink types and talked about how MSI can help inform conservation treatment and help uncover faded or hidden text.

Periodically, we’ve also mentioned our Duke MSI group. This group is a cross-departmental team of individuals that each bring to the table critical expertise to ensure that our MSI projects run smoothly and effectively. This past year, our team has created various best practices and workflows, tackled equipment and software hurdles, determined current resource capacity, imaged a number of materials from Duke’s collections, and documented data modeling scenarios. We’re really excited about and proud of the work that we’ve accomplished together.

Many times, though, we’ve talked about how helpful it would be to talk with other institutions that are doing MSI, particularly cultural heritage institutions and academic libraries, in order to learn how they develop their skills and organize their services. Luckily, the University of Manchester, an institution that has the same MSI system as ours, expressed interest in collaborating with us to our shared vendor R. B. Toth Associates. We had a very informative conference call with them in May 2017, during which we discussed their program, services, and technical details. We also shared documentation after the call, which has helped us refine our project request procedures and our deliverables that we provide to the requesters at the end of projects.

Since that collaboration proved so beneficial, we thought it would be helpful to reach out to other institutions that undertake MSI projects. Though it is difficult to determine exact numbers online, it is clear that very few cultural heritage organizations and academic libraries host their own MSI system. Therefore, we teamed up with R. B. Toth Associates again to determine what other institutions they’d worked with that may be interested in collaborating. They shared six institutions worldwide, and we created a brief online survey about the topics that we’d discussed with the University of Manchester, which included organization and staffing, time devoted to MSI, prioritization, project deliverables, and data modeling and access. Five of the six institutions thought that the survey applied to their current MSI setup and therefore completed the survey, and all six expressed some level of interest in future collaboration. The institutions that completed the survey are the Library of Congress, the Museums of New Mexico-Conservation, the University of Pennsylvania Libraries, KU Leuven Libraries, and the University of Copenhagen.

Out of the institutions that we’ve spoken with or surveyed (six in total, including the University of Manchester), we can determine that three have permanent MSI systems (the Library of Congress, the Museums of New Mexico, and University of Manchester). One institution’s survey results were unclear about owning its own system, and the other two institutions noted that they use MSI systems on an ad-hoc, project by project basis. One of those institutions indicated that they are in the initial stages of considering the purchase of a permanent system, and the institution that declined taking the survey stated that it was because they did not own their own system due to costs. Some institutions charge a fee for MSI projects, while others don’t. One institution that currently does not charge expressed interest in creating a cost recovery model.

In terms of the institutions that own a permanent MSI system, the Library of Congress is the only that has one full time employee devoted solely to MSI. The Museums of New Mexico have one employee that serves as the main PI for MSI, though the entire Conservation department is trained on the equipment and software. Their department devotes approximately 20 hours per week to MSI depending on the project. The University of Manchester has two imagers that devote one day per month to imaging, and process intermittently. The other institutions without permanent systems use a combination of trained staff, scholars, imaging scientists, object handlers and conservators, metadata and data managers, imaging technicians, and project managers based on specific project needs.

It appears that most institutions image their own collections for MSI projects, though one respondent indicated that they also partner with other conservation institutions for their research needs. Prioritization processes for MSI projects vary institution to institution. The Library of Congress is the exception, because that department solely does MSI projects, and therefore requests do not need to be prioritized with other digitization requests. The Museums of New Mexico prioritize on a first come, first serve basis, as long as the project is a good fit for MSI. The University of Manchester also has a pre-project process with conservation staff to determine if the project is a good fit for MSI. KU Leuven Libraries prioritizes based on scope, indicating the priority is documentary heritage with a strong focus on illuminated manuscripts, but will service other research if time permits. Additional prioritization strategies include availability of trained staff and scholars.

The institutions have similar goals for MSI projects based on whether a project is internal (for conservation or acquisition purposes) or external (research requested). These include pure documentation, establishing a condition baseline, forensic examination and reconstruction, pre-purchase examination, collecting spectral responses for preservation, revealing undertext for transcription, and revealing undertext for text identification.

Deliverables and preservation copies vary by institution as well. Three of the institutions always include some type of a report with the files. KU Leuven provides multiple reports, including a technical report about infrastructure, an analysis report, and an imaging methodology. Two of the institutions provide the raw and processed images, two provide only the processed images (as jpegs or tiffs), and two state that the deliverables vary based on project. The University of Pennsylvania is the only institution that noted that it provides metadata, which often include transcriptions or descriptive and structural metadata and is packaged in a preservation-ready package. One respondent replied that they retain raw data offline, but place processed captures into a digital asset management system (presumably for online access), and another noted that some projects have arranged preservation of their data packages through third parties that offer dark or accessible digital repositories. Every institution retains some or all of their MSI data internally.

This is just a brief summary of what we learned through this process—we were lucky to receive a lot of data and comments! We are very pleased with and thankful for their willingness to share. As noted earlier, all have expressed an interest in some level of future collaboration, so we’re hopeful to build a network of institutions that can provide feedback and advice to one another for future MSI needs. To all of our fellow MSI institutions, we thank you again for your participation! Please let me know if I misrepresented any of your information. We received a lot of great qualitative responses, and though I did my best to communicate those correctly, I may have misunderstood some responses.

Change is afoot in Software Development and Integration Services

We’re experimenting with changing our approach to projects in Software Development and Integration Services (SDIS). There’s been much talk of Agile (see the Agile Manifesto) over the past few years within our department, but we’ve faced challenges implementing this as an approach to our work given our broad portfolio, relatively small team, and large number of internal stakeholders.

After some productive conversations among staff and managers in SDIS where we reflected on our work over the past few years we decided to commit to applying the Scrum framework to one or more projects.

Scrum Framework
Source: https://commons.wikimedia.org/wiki/File:Scrum_Framework.png

There are many resources available for learning about Agile and Scrum. The resources I’ve found most useful so far in learning about the framework include:

Scrum seems best suited to developing new products or software and defines the roles, workflow, and artifacts that help a team make the most of its capacity to build the highest value features first and deliver usable software on a regular and frequent schedule.

To start, we’ll be applying this process to a new project to build a prototype of a research data repository based on Hyrax. We’ve formed a small team, including a product owner, scrum master, and development team to build the repository. So far, we’ve developed an initial backlog of requirements in the form of user stories in Jira, the software we use to manage projects. We’ve done some backlog refinement to prioritize the most important and highest value features, and defined acceptance criteria for the ones that we’ll consider first. The development team has estimated the story points (relative estimate of effort and complexity) for some of the user stories to help us with sprint planning and release projection. Our first two-week sprint will begin the week after Thanksgiving. By the end of January we expect to have completed four, two-week sprints and have a pilot ready with a basic set of features implemented for evaluation by internal stakeholders.

One of the important aspects of Scrum is that group reflection on the process itself is built into the workflow through retrospective meetings after each sprint. Done right, routine retrospectives serve to reinforce what is working well and allows for adjustments to address things that aren’t. In the future we hope to adapt what we learn from applying the Scrum framework to the research data repository pilot to improve our approach to other aspects of our work in SDIS.

Notes from the Duke University Libraries Digital Projects Team