Posted by on Oct 12, 2015 in DGP Member Interviews |

Jaime McCurry - Digital Assets Librarian

Jaime offers some wonderful advice about digital asset management specific to policies and workflows for successful DAM system strategies.

What companies/organizations have you worked for as a DAM professional? What was your role at each?

I first started thinking about DAM while pursuing my MLIS. After graduating in 2013, I was selected to serve as a resident in the inaugural National Digital Stewardship Residency program, hosted by the Library of Congress, where I was placed at the Folger Shakespeare Library in Washington, D.C. as a digital archivist. For nine months I worked to evaluate the digital climate at the library as it related to digital asset management and digital preservation. In addition to working on the Folger’s web archiving program, I generated a file-format inventory of the born-digital assets created and held by the Folger’s theatre and television production departments. That inventory evolved into a prescriptive digital stewardship needs-assessment report, intended to support future institutional digital asset management projects and programs.

I am currently the Digital Assets Librarian at the Hillwood Estate, Museum & Gardens in Washington, D.C. At Hillwood, I am positioned in the Archives & Special Collections Library where I am responsible for developing, implementing, and sustaining our digital asset management, preservation, and stewardship practices. I administer our newly created institutional digital asset management program and manage our current DAMS. Some of my responsibilities include user-training, the development of local policies and workflows, overseeing any necessary system development work, and the general management of our digital collections.

How did you learn DAM? Any recommended sources?

As a library science student, I was drawn to all things digital: digital access and digital stewardship/preservation especially. When studying digital stewardship, you come to be familiar with what’s known as the digital lifecycle. The lifecycle model essentially could be considered a core tenet of the DAM profession: a digital asset is created, it is described, managed, preserved, and made discoverable, all to facilitate access, use, and reuse. These principles and their close connection to the DAM profession led me to learn more DAM and how proper digital asset management programs provide access to important collections of content.

Specifically, I found resources such as the Journal of Digital Media Management and blogs like CMSWire and DAM Guru to be very helpful. I’d definitely recommend anyone considering participating in the DAM Guru program to take the leap. I was fortunate to connect with a Guru in 2013 while working as a resident at the Folger and the conversation we had together was incredibly informative and insightful.

There are also tons of helpful resources coming out of the library and information science communities, especially regarding descriptive standards, digital access and preservation technologies, and general digital information management strategies: D-Lib Magazine, the Code4Lib Journal and community, and the Library of Congress’ The Signal to name a few.

What’s the most important thing for someone new to DAM to understand about DAM?

DAM is both an activity and an environment. These two existences rely on each other to survive. The activities that go into the continual management of your assets and DAMS as a whole rely completely on the working environment that provides the policies, workflows, motivation, and support for those activities to take place. That and while there are universal DAM strategies, each DAM environment will be slightly different at each institution you encounter. The structure, the bones, of your program should be determined by the needs and use-cases of your users. In my experience, solutions and workflows that attempt to complement and optimize native work habits are more likely to be adopted and to survive.

If you weren’t doing DAM as a career, what would you be doing?

Web development. I am learning to code in my spare time and have a growing love for graphic and user-centered web design. It would be so interesting to apply these interests in a cultural heritage/museum setting. I think a lot about sharing digital collections and about what an engaging digital collections portal or online web exhibition might look like. Those are thoughts I intend to explore further in the future.

What is your ongoing greatest challenge with DAM?

Well, there will always be the-great-metadata-challenge: how much is too much? How little is too little? Where is the balance? When I introduce the concept of metadata to our content-creators and our general users, I like to draw the connection between metadata and search performance. We’re trying to make sure that our content-creators are equipped with the tools and tips they need to describe their content efficiently so that our search results are as accurate as possible for our general users. I find that the example of searching and successfully finding the items you are looking for really resonates with users.

What was your biggest success with regard to DAM?

The full implementation of our current DAMS at Hillwood. It was, and still is, a definite journey from migrating content from the institution’s past DAMS to working with our terrific creators to describe and provide access to that content, some of it for the very first time! We’ve also undertaken two development projects to optimize the system to our needs and are already starting to see the rewards of such measures.

What more would you like to learn about DAM?

I would love to learn more about our DAMS’ API and more about APIs in general. There’s such a wealth of content that we’re managing, it would be really amazing to connect to and pull from that wealth in more creative ways to support the discovery of, use of, and interest in our assets.

—–
Would you like to be a DAM Guru Program featured DAM professional? Signup now (for free) or contact your DAM Guru Program manager.