{"id":359,"date":"2022-09-06T10:09:05","date_gmt":"2022-09-06T10:09:05","guid":{"rendered":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/?p=359"},"modified":"2022-09-06T10:10:53","modified_gmt":"2022-09-06T10:10:53","slug":"minimum-preservation-for-maximum-results-its-a-good-idea-if-it-works","status":"publish","type":"post","link":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/2022\/09\/06\/minimum-preservation-for-maximum-results-its-a-good-idea-if-it-works\/","title":{"rendered":"Minimum Preservation for Maximum Results? It’s a good idea if it works!"},"content":{"rendered":"

\"iPres2022In less than a week, iPres22<\/a> will kick off in Glasgow, right on our doorstep! If you\u2019re not already acquainted with iPres, welcome! There\u2019s something for everyone! iPres is the world\u2019s largest digital preservation conference where practitioners from all sorts of backgrounds and industries gather to share challenges and strategies. <\/span>\u00a0<\/span><\/p>\n

At this year\u2019s iPres, among other things, I\u2019m running a workshop with Caylin Smith (Head of Digital Preservation at Cambridge University Library) and Patricia Falcao (Time-based Media Conservator at Tate) on Preserving Complex Digital Objects – Revisited<\/a><\/span>. We ran a similar workshop at iPres 2019 in Amsterdam, breaking into groups to undertake different aspects of the preservation process with one complex digital object (\u2018Breathe\u2019 by Kate Pullinger<\/a><\/span>).<\/span>\u00a0<\/span><\/p>\n

This year, each of the speakers will bring a digital object from their own collections that they consider to be complex. We will break participants into small groups to try an experiment:<\/span>\u00a0<\/span><\/p>\n

Can a Minimum Viable Preservation (MVP) approach be applied to complex digital objects? Read more to learn about what MVP digital preservation looks like and what to expect from the workshop!<\/span> If you’re planning to attend iPres, come join us!\u00a0<\/span><\/p>\n

<\/p>\n

Applying a Minimum Viable Preservation (MVP) Approach to Complex Digital Objects<\/strong>\u00a0<\/span><\/p>\n

This Workshop defines MVP (Minimum Viable Preservation) as an approach to digital preservation that takes the minimum steps necessary to ensure access to a digital object for one generation (IT system generation). Other terms floating around for this concept (more or less) include minimal effort ingest, parsimonious preservation, and risk-based preservation. Rather than apply sophisticated frameworks or standards to every digital resource, is it possible to assess precise risks and implement solutions that mitigate those risks only and not imagined risks for which we have no or very weak evidence?\u00a0<\/span>\u00a0<\/span><\/p>\n

Let\u2019s find out.\u00a0<\/span>\u00a0<\/span><\/p>\n

The approach outlined here is derived from a few different sources and ideas about how to streamline digital preservation and simplify the systems and processes we use.<\/span>\u00a0<\/span><\/p>\n

The earliest concept of minimum, or \u2018parsimonious\u2019 preservation comes from Tim Gollins in 2009 where he advocates for using as much pre-existing infrastructure as possible rather than a complex, bespoke system. According to Gollins, parsimonious preservation focuses on minimum access provision (rather than trying to achieve widespread, remote access) and initial retention for roughly 5-10 years (or the lifespan of a typical IT system). He argues that parsimonious preservation should not be conflated with \u2018cheap\u2019 preservation but rather understood as practical approaches that emphasise good capture practice and early intervention. However, Gollins proposes that this approach can only be applied to smaller, more heterogeneous collections. His main evidence to support his argument that software obsolescence may not pose a major risk, for example, is restricted to a file-level preservation approach.\u00a0<\/span>\u00a0<\/span><\/p>\n

Nine years later in October 2018, Paul Wheatley of the DPC argues for simplified ingest to digital preservation systems by reducing the role of file format validation. He argues that attempting to fix \u2018failed\u2019 files can lead to unintentional loss of meaning or functionality, but more importantly, takes up a huge amount of time for very little return. While he concedes that file format validation does have a role to play, it\u2019s most effective when improving target formats that are more preservable in the first place. Rather bleakly, he argues complex format specifications are unlikely to be detailed enough to support backwards engineering of a tool that can render those files anyway. He advocates instead for developing rendering tools that can auto-parse files to discover problems and report on them so risks can be evaluated by preservationists rather than just assumed to be problematic. Wheatley\u2019s proposal is speculative, though, and calls for further research into the efficacy of such auto-rendering tools. Also, similarly to Gollins\u2019, Wheatley\u2019s proposal is focussed on file-level preservation.\u00a0<\/span>\u00a0<\/span><\/p>\n

In response to Wheatley\u2019s takedown of the digital preservation mainstay of format validation, in November 2018, Matthew Addis speculates whether the digital preservation community could establish a universal (or widely applicable) Minimum Viable Preservation approach to manage the bulk of digital data more efficiently. (He also coined the term we have adopted for this workshop, with thanks.) Like Gollins\u2019 and Wheatley\u2019s arguments, Addis\u2019s approach is very file-centric, proposing shared workflows (via COW) and automated preservation actions (via PAR) that can be applied at the file level. Addis proposes that an MVP approach can support the majority of content to free up capacity for curators to build more sophisticated preservation approaches for more complex content. He goes on to state:<\/span>\u00a0<\/span><\/p>\n

\u2018That’s not to say that other content types won’t be harder or need more steps, especially\u00a0 complex digital objects where an authentic user experience is a key part of preservation [\u2026] But maybe there is a place for a simple MVP approach to complex objects too – if it’s not easy to find or keep or run a full-on renderer, then simply recording \u201ca previous rendering of\u201d the content (video, screencams, webrecorder.io etc.) could be an MVP approach to take.\u2019<\/span>\u00a0<\/span><\/p>\n

In this workshop we take up Matthew Addis\u2019 challenge that there may be a way to take a simpler, minimum approach to preserving more complex objects as well as more straightforward files (e.g. PDFs).\u00a0<\/span>\u00a0<\/span><\/p>\n

Given the limitations of the MVP or parsimonious preservation approaches, can a similar process be applied to more complex digital objects, like data-driven applications or virtual reality artworks? Will these types of approaches only work effectively for file-level preservation? Can a simpler, risk analysis-based approach capture the meaningful experience or responsive interactions so fundamental to many of the complex objects we describe in this workshop? <\/span>\u00a0<\/span><\/p>\n

From a practical perspective, if widespread remote access is not the goal, will it be (even) more difficult to make the case for resource and funding? The type of early intervention, high quality capture required to fulfil parsimonious preservation depends on skilled staffing capacity, which is out of reach for many organisations. Similarly, if an institutional strategy aims only to preserve content for only one IT system lifetime, will the resulting on-going, iterative preservation become unsustainable as content grows?\u00a0<\/span>\u00a0<\/span><\/p>\n

These are just some questions to consider while undertaking this activity. In the next hour or so, we ask you to break into groups and analyse one of three collection items presented today. With the available documentation, assess if an MVP (or adapted MVP) approach might adequately preserve that complex digital object.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

Questions to guide the activity:\u00a0\u00a0<\/strong><\/p>\n

    \n
  1. What is it? \u2013 Determine the basic components and decide what the object is<\/span><\/li>\n
  2. Why are you preserving this object? \u2013 Define the motivation and purpose for preserving this object, given the available information about the object and its institutional context\u00a0<\/span>\u00a0<\/span><\/li>\n
  3. Why was it created and who will use it in the future \u2013 Understand, to the best of your ability, what purpose the object is meant to serve, as envisioned by its creators, and who is likely to use it in the future<\/span>\u00a0<\/span><\/li>\n
  4. What aspects of the object matter to, or support, the purpose of preservation? \u2013 Decide what components or information is required to enable future use of this object by the identified future users, including dependencies, permissions, and related objects<\/span>\u00a0<\/span><\/li>\n
  5. What can you learn about the risks to this type of object? \u2013 Use the available documentation and your own quick, online research to learn what you can about this object or even possible preservation strategies<\/span>\u00a0<\/span><\/li>\n
  6. What further information is required to understand this object \u2013 Articulate what information, if any, is missing that might prevent you from making a preservation decision<\/span>\u00a0<\/span><\/li>\n
  7. What preservation actions are required to preserve this object? \u2013 Decide what action(s) you would take to enable access to this object for approximately 10 years (or one IT system generation)<\/span>\u00a0<\/span><\/li>\n
  8. How will you provide access to this object? \u2013 Determine what metadata and systems\/hardware are required to enable access to the preserved object in future<\/span>\u00a0<\/span><\/li>\n
  9. What steps might be taken to ensure longer-term access? \u2013 Consider what additional action or future processes would be required to ensure access to this object beyond the lifetime of a single IT system, even for perpetuity<\/span>\u00a0<\/span><\/li>\n
  10. Does this constitute a \u2018minimum viable preservation\u2019 approach? – Decide within your group whether you consider the required steps to preserve this object to align with the principles suggested about MVP. Can you preserve this without reliance on file format validation, for example? Could all or part of this process be applied to other similar objects in different types of institutions? Will bespoke tools or infrastructure be required to preserve this object or can well-supported, existing tools and infrastructure be used?\u00a0<\/span>\u00a0<\/span><\/li>\n
  11. If not, why not?<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

    \u00a0<\/span>\u00a0<\/span><\/p>\n

    Sources\u00a0<\/strong><\/p>\n

    Matthew Addis, \u2018Minimum Viable Preservation\u2019, DPC Blog (Nov 2018): <\/span>https:\/\/www.dpconline.org\/blog\/minimum-viable-preservation<\/span><\/a>\u00a0<\/span>\u00a0<\/span><\/p>\n

    Tim Gollins, ‘Parsimonious preservation: preventing pointless processes! (The small simple steps that take digital preservation a long way forward)’, Online Information (2009): <\/span>https:\/\/cdn.nationalarchives.gov.uk\/documents\/information-management\/parsimonious-preservation.pdf<\/span><\/a>\u00a0\u00a0\u00a0\u00a0<\/span>\u00a0<\/span><\/p>\n

    Paul Wheatley, ‘A valediction for validation?’, DPC Blog (October 2018): <\/span>https:\/\/www.dpconline.org\/blog\/a-valediction-for-validation<\/span><\/a>\u00a0<\/span><\/p>\n

    \u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

    In less than a week, iPres22 will kick off in Glasgow, right on our doorstep! If you\u2019re not already acquainted with iPres, welcome! There\u2019s something for everyone! iPres is the world\u2019s largest digital preservation conference where practitioners from all sorts … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":201,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[5,105,4],"tags":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p5j0gX-5N","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/posts\/359"}],"collection":[{"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/users\/201"}],"replies":[{"embeddable":true,"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/comments?post=359"}],"version-history":[{"count":11,"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/posts\/359\/revisions"}],"predecessor-version":[{"id":388,"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/posts\/359\/revisions\/388"}],"wp:attachment":[{"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/media?parent=359"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/categories?post=359"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/libraryblogs.is.ed.ac.uk\/bitsandpieces\/wp-json\/wp\/v2\/tags?post=359"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}