I havenâ€™t done much digital preservation. Iâ€™ve been in the bit trenches. The work Iâ€™ve done is to digital preservation as community sandbagging is to the Army Corps of Engineers. I need to reword my resume.
Bit preservation is our most urgent set of tasks; managing multiple copies, managing and using fixity information and ensuring our data is secure. All these activities are directed at long term usability, but digital preservation is broader. Itâ€™s concerned with the future viability of file formats and software; with future renderability. Having done the basic bit level work, we might consider migrating files en masse to more sustainable formats or â€œleave the bits aloneâ€ by emulating or virtualizing earlier computing environments.
Our digital preservation decisions will not be identical across institutions. Best practices are like recipes; theyâ€™re frameworks. â€œApproaches to copies and formats should fit the overall contours of your institutionâ€™s collecting mission and resources. This is about the digital infrastructure you establish to enable the more tailored work that is done around individual collectionsâ€ (Owens, p. 105). A video art or game collecting museum might attempt emulation to preserve as much of the experience of the work as possible; seeing the artifactual aspect as more intrinsic than the informational to its mission. But if those bits arenâ€™t safe, these considerations will never arise. Sandbag first.
Much of our study this week is focused on fixity and storage. In my bit preservation experience, fixity checks can get lost in the mix. 80% of NDSA member organizations reported that they use some sort of fixity checking. I think that members and non-members alike have mostly heard the urgent call to action to get the bits off the floor and maybe while theyâ€™re at it, make multiple copies. Then, of course, they have to store them somewhere, so theyâ€™re forced to make storage decisions. But Iâ€™m not so sure that organizations often understand the necessity of maintaining bit-level integrity and how theyâ€™d go about it. Then again, they could be taking it for granted that their storage solution is a fixity solution as well. And it might be, but I think thatâ€™s something of an afterthought.
Weâ€™re going to talk about access later in this course, but my impression has been that access, as a buzzword, can cloud our perspective on preservation. Iâ€™m concerned that when that scan hits the web, itâ€™s tempting to feel that our preservation work is done. Weâ€™d never take that approach to analog media. We wouldnâ€™t hang a painting in a gallery, throw our hammer in the truck and head home. Well we might, but weâ€™d be invested in maintaining the integrity of that work for future shows. Accessibility now isnâ€™t access. This might be obvious to us, but just this week I was speaking to someone about born digital material and they asked me if I was also interested in endangered media. Itâ€™s still a hard sell.
That brings me to one final thought I had while reading the case studies in the POWRR group white paper. The experience at Chicago State University was illuminating. â€œThe defining moment when several library staff members recognized the importance of digital preservation activities occurred when they realized that grant activities digitizing library collections included no provision for storage or preservationâ€ (p. 21). That might be because the grants themselves donâ€™t allow for appropriate storage solutions. I was investigating grants for an in-house digitization project I was working on and had determined that cloud storage was the best, and most affordable, offsite storage solution for my organization. Once I found a grant that wouldnâ€™t exclude in-house digitization projects, I realized it had seemingly arbitrary restrictions excluding â€œsubscription-basedâ€ or simply, â€œcloudâ€ storage.
Our reading this week helped me recontextualize my own work as a novice in this field. I wonder if anyone else had a similar experience.