Recently, I attended METRO’s Annual Conference where I presented on a panel titled “Getting More Out of (and Into) Your Collections Management System.” I spoke about my experience learning to code as a processing archivist and developing DACSspace. The following is the text from my presentation.
Last Friday, I attended the annual symposium of the Greater New York Metropolitan Area Chapter of the Association of College and Research Libraries (ACRL/NY). This year’s theme was Money and Power, and the talks covered standards, instruction, labor, and other library issues that intersect with issues of money and power.
I’m excited to announce that the Rockefeller Archive Center’s new Digital Media Log is live!
Since Project Electron kicked off in September, we’ve made significant progress on a number of different fronts. First, together with our Marist College partners, we created a milestones document which lays out major phases of work. We also developed some general principles and overall approaches to licensing project deliverables, including code, documentation and planning documents. Since we anticipate both of these documents will change over time, we’ve versioned them using git (and have pushed a copy to GitHub) so we can keep track of those changes. Continue reading
Along with Bonnie (read her report of the conference here), I attended the Preservation and Archiving Special Interest Group (PASIG) Fall 2016 conference last week. I learned a lot at this conference about the technical aspects of digital preservation, both from a theoretical as well as a practical perspective.
There were a host of good presentations which provided introductions or practical guides to implementing digital preservation processes. I particularly liked Bertram Lyon’s presentation on the “The Anatomy of Digital Files,” Alison Rhonemus, Julia Kim, Morgan Mckeehan, Dianne Dietrich and Erin Faulder’s presentation on “Emulation for Everyone,” and Sam Meister’s discussion of “The Ecosystem of Digital Objects.”
However – the last day of the conference, which brought critical theory to bear on many of the assumptions and accepted practices in the world of digital preservation – was one of the most provocative and stimulating days of conference learning I’ve experienced in quite some time.
One of the most mind-blowing presentations was Dragan Espenschied’s discussion of the work of Webrecorder, which is a tool to capture “recordings” of websites. In his talk, he made a passing comment that the web is often conceived of as a bunch of URLs at which you can access content, but really the web is made up of people situated in time and space, using a specific web browser, operating system and network infrastructure. The last session of the day was a panel which included Ingrid Burrington, an artist and writer whose work centers on the physical infrastructure that supports large digital networks. In closing, Burrington remarked that we often talk about this infrastructure as invisible, which isn’t really true; it’s more that it’s hiding in plain sight.
These two comments got me thinking about the nature of invisibility, and reminded me of the adage that “what you see depends on where you stand.” So when we say something’s invisible, we’re really talking about own perceptions rather than expressing a universal fact. Perhaps, instead of saying something is invisible, we should say it is invisible to us; that we are blind to that particular thing, person or process.
These ideas of invisibility and blindness were further amplified by Elvia Arroyo-Ramirez’s talk, which Bonnie wrote about in some detail. At the heart of Arroyo-Ramirez’s presentation was the question “what processes are we willing to work through rather than around?” a question that intersected with several conversations I had over the course of the conference about the perils of outsourcing digital preservation expertise (and to a certain extent, infrastructure) to a third party. Although that course of action can seem like an attractive solution (particularly in the short term), “working around” the problems of digital preservation by subcontracting expertise almost always has debilitating effects over the long- (or even medium-) term because it removes opportunities for building local capacity. In Arroyo-Ramirez’s talk as well as several informal conversations with colleagues, I heard a strong argument for taking the time to “work through” digital preservation processes, to engage with processes, tools and ideas intentionally with an eye to building human capacity.
As we continue to work on Project Electron, these ideas of invisibility and where we apply labor are critically important. We’ve talked a lot about enabling systems integration with this project, but what are the characteristics of those integrations? Are we working towards integrations that are “invisible,” and if so, what are the implications for the humans who interact with these systems? When we talk about “seamlessness,” do we simply mean seams we don’t see or understand? What are we blinding ourselves to in the search for efficient workflows and measurable results? What kind of work are we making possible and what are we inhibiting or even prohibiting?
Last week, I attended the Preservation and Archiving Special Interest Group (PASIG) Fall 2016 meeting, here in New York, at the Museum of Modern Art. Each day of the three-day conference focused on a different theme: Day 1 was “Bootcamp/101,” Day 2 was “Preservation and Archiving in Practice” and Day 3 was “Preservation Frontiers and the Bigger Picture.” While all three days were great, and I’d recommend checking out all of the presentations, the talks on the final day made me reflect critically on what it means to responsibly engage with digital preservation activities, especially at an institution like the Rockefeller Archive Center.
For many archives, the master shelf list has been a permanent staple since their inception. We have one. It’s an ever-growing Excel spreadsheet that lists the location of every single box in our collection down to the shelf number. It’s enormous, it’s unwieldy, and it takes a ton of work to keep updated month to month. For years we’ve been looking for a way to move away from it, and the release of ArchivesSpace version 1.5 has given us the rare opportunity to move entirely away from our spreadsheet into a more structured and interoperable. The Rockefeller Archive Center will no longer enter new information into our Master Shelf List. Continue reading