Trained in Classification, Without Classification

by Ashley Blewer

This is the first post in the bloggERS Making Tech Skills a Strategic Priority series.

Hi, SAA ERS readers! My name is Ashley Blewer, and I am sort of an archivist, sort of a developer, and sort of something else I haven’t quite figured out what to call myself. I work for a company for Artefactual Systems, and we make digital preservation and access software called Archivematica and AtoM (Access to Memory) respectively. My job title is AV Preservation Specialist, which is true, that is what I specialize in, and maybe that fulfills part of that “sort of something else I haven’t quite figured out.” I’ve held a lot of different roles in my career, as digital preservation consultant, open source software builder and promoter, developer at a big public library, archivist at a small public film archive, and other things. This, however, is my first time working for an open source technology company that makes software used by libraries, archives, museums, and other organizations in the cultural heritage sector. I think this is a rare vantage point from which to look at the field and its relationship to technology, and I think that even within this rare position, we have an even more unique culture and mentality around archives and technology that I’d like to talk about.

Within Archivematica, we have a few loosely defined types of jobs. There are systems archivists, which we speak of internally as analysts, there are developers (software engineers), and there are also systems operations folks (systems administrators and production support engineers). We have a few other roles that sit more at the executive level, but there isn’t a wall between any of these roles, as even those who are classified as being “in management” also work as analysts or systems engineers when called upon to do so. My role also sits between a lot of these loosely defined roles — I suppose I am technically classified as an analyst, and I run with the fellow analyst crew: I attend their meetings, work directly with clients, and other preservation-specific duties, but I also have software development skills, and can perform more traditionally technical tasks like writing code, changing how things function at a infrastructure level, and reviewing and testing the code that has been written by others. I’m still learning the ropes (I have been at the organization full-time for 4 months), but I am increasingly able to do some simple system administration tasks too, mostly for clients that need me to log in and check out what’s going on with their systems. This seems to be a way in which roles at my company and within the field (I hope) are naturally evolving. Another example is my brilliant colleague Ross Spencer who works as a software engineer, but has a long-established career working within the digital preservation space, so he definitely lends a hand providing crucial insight when doing “analyst-style” work.

We are a technical company, and everyone on staff has some components that are essential to a well-rounded digital preservation systems infrastructure. For example, all of us know how to use Git (a version control management system made popular by Github) and we use it as a regular part of our job, whether we are writing code or writing documentation for how to use our software. But “being technical” or having technical literacy skills involves much, much more than writing code. My fellow analysts have to do highly complex and nuanced workflow development and data mapping work, figuring out niche bugs associated with some of the microservices we run, and articulating in common human language some of the very technical parts of a large software system. I think Artefactual’s success as a company comes from the collective ability to foster a safe, warm, and collaborative environment that allows anyone on the team to get the advice or support they need to understand a technical problem, and use that knowledge to better support our software, every Archivematica user (client or non-client), and the larger digital preservation community. This is the most important part of any technical initiative or training, and it is the most fundamental component of any system.

I don’t write this as a representative for Artefactual, but as myself, a person who has held many different roles at many different institutions all with different relationships to technology, and this has by far been the most healthy and on-the-job educational experience I have had, and I think those two things go hand-in-hand. I can only hope that other organizations begin to narrow the line between “person who does archives work” and “technical person” in a way that supports collaboration and cross-training between people coming into the field with different backgrounds and experiences. We are all in this together, and the only way we are gonna get things done is if we work closely together.



Ashley works as at Artefactual Systems as their AV Preservation Specialist, primarily on the Archivematica project. She specializes in time-based media preservation, digital repository management, infrastructure/community building, computer-to-human interpretation, and teaching technical concepts. She is an active contributor to MediaArea’s MediaConch, a open source digital video file conformance checker software project, and Bay Area Video Coalition’s QCTools, an open source digitized video analysis software project. She holds Master of Library and Information Science (Archives) and Bachelor of Arts (Graphic Design) degrees from the University of South Carolina.

Advertisements

Software Preservation Network: Prospects in Software Preservation Partnerships

By Karl-Rainer Blumenthal

This is the fourth post in our series on the Software Preservation Network 2016 Forum.
____

Software Preservation Network logoTo me, the emphases on the importances of partnership and collaboration were the brightest highlights of August’s Software Preservation Network (SPN) Forum at Georgia State University. The event’s theme, “Action Research: Empowering the Cultural Heritage Community and Mapping Out Next Steps for Software Preservation,” permeated early panels, presentations, and brainstorming exercises, empowering as they did the attending stewards of cultural heritage and technology to advocate the next steps most critical to their own goals in order to build the most broadly representative community. After considering surveys of collection and preservation practices, and case studies evocative of their legal and procedural challenges, attendees collaboratively summarized the specific obstacles to be overcome, strategies worth pursuing together, and goals that represent success. Four stewards guided us through this task with the day’s final panel of case studies, ideas, and a participatory exercise. Under the deceptively simple title of “Partnerships,” this group grounded its discourse in practical cases and progressively widened its circle to encompass the variously missioned parties needed to make software preservation a reality at scale.

Tim Walsh (@bitarchivist), Digital Archivist at the Canadian Centre for Architecture (CCA), introduced the origins of his museum’s software preservation mission in its research program Archaeology of the Digital. Advancing one of the day’s key motifs–of software as environment beyond mere artifact–Walsh explained that the CCA’s ongoing mission to preserve tools of the design trades compels it to preserve whole systems environments in order to provide researcher access to obsolete computer-assisted design (CAD) programs and their files. “There are no valid migration pathways,” he assured us; rather emulation is necessary to sustain access even when it is limited to the reading room. Attaining even that level of accessibility required CCA to reach license agreements with the creators/owners of legacy software, one of the first, most foundational partnerships that any stewarding organization must consider. To grow further still, these partnerships will need to include technical specialists and resource providers beyond CCA’s limited archives and IT staff.

Aliza Leventhal (@alizaleventhal), Corporate Librarian/Archivist at Sasaki Associates, confronts these challenges in her role within a multi-disciplinary design practice, where unencumbered access to the products of at least 14 different CAD programs is a regular need. To meet that need she has similarly reached out to software proprietors, but likewise cultivated an expanding community of stewards in the form of the SAA Architectural Records Roundtable’s CAD/BIM Taskforce. The Taskforce embraces a clearinghouse role for resources “that address the legal, technical and curatorial complexities” of preserving especially environmentally-dependent collections in repositories like her own and Walsh’s. In order to do so, however, Leventhal reminded us that more definitive standards for the actual artifacts, environments, and documentation that we seek to preserve must first be established by independent and (inter-)national authorities like International Organization for Standardization (ISO), the American Institute of Architects (AIA), the National Institute of Building Sciences, and yet unfounded organizations in the design arts realm. Among other things, after all, more technical alignment in this regard could enable multi-institutional repositories to distribute and share acquisition, storage, and access resources and expertise.

Nicholas Taylor (@nullhandle), Web Archiving Service Manager at Stanford University Libraries, asked attendees to imagine a future SPN serving such a role itself–as a multi-institutional service partnership that distributes legal, technical, and curatorial repository management responsibilities in the model of the LOCKSS Program. Citing the CLOCKSS Archive and other private networks as a complementary example from the realms of digital images, government documents, and scholarly publications, Taylor posited that such a partnership would empower participants to act independently as centralizing service nodes, and together in overarching governance. A community-governed partnership would need to meet functional technical requirements for preservation, speak to representative use cases, and, critically, articulate a sustainable business model in order to engender buy-in. If successful though, it could among other things consolidate the broader field’s needs to for licensing and IP agreements like CCA’s.

In addition to meeting its member organizations’ needs, this version of SPN, or a partnership like it, could benefit an even wider international community. Ryder Kouba (@rsko83), Digital Collections Archivist at the American University in Cairo, spoke to this potential from his perspective on the Technology and Research Working Group of UNESCO’s PERSIST Project. The project has already produced guidance on selecting digital materials for preservation among UNESCO’s 200+ member states. Its longer term ambitions, however, include the maintenance of the virtual environments in which members’ legacy software can be preserved and accessed. Defining the functional requirements and features of such a global resource will take the sustained and detailed input of a similarly globally-spanning community, beginning in the room in which the SPN Forum took place, but continuing on to the International Conference on Digital Preservation (iPres) and international convocations beyond.

blumenthal_spn_ersblog_1 blumenthal_spn_ersblog_2

 

 

 

 

 

 

Attendees compose matrices of software preservation needs, challenges, strategies, and outcomes. Photos by Karl-Rainer Blumenthal (left) and @karirene69 (right), CC BY-NC 2.0.

The different scales of partnership thus articulated, the panelists ended their session by facilitating breakout groups in the mapping of discrete problems that partnerships can solve through their necessary steps and towards ideal outcomes. At my table, for instance, the issue of “orphaned” software–software without advocates for long-term preservation–was projected through consolidation in a kind of PRONOM-like registry to get the maintenance that they deserve from partners invested in a LOCKSS-like network. Conceptually simple as each suggestion could be, it could also prompt such different valuations and/or reservations from among just the people in the room as to illustrate how difficult the prioritization of software preservation work can be for a team of partners, rather than independent actors. To accomplish the Forum attendees’ goals equitably as well as efficiently, more consensus needed to be reached concerning the timeline of next steps and meaningful benchmarks, something that we tackled in a final brainstorming session that Susan Malsbury will describe next!

____

Karl-Rainer Blumenthal is a Web Archivist for the Internet Archive’s Archive-It service, where he works with 450+ partner institutions to preserve and share web heritage. Karl seeks to steward collaboration among diversely missioned and resourced cultural heritage organizations through his professional work and research, as we continuously seek new, broadly accessible solutions to the challenges of complex media preservation.