Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The digital preservation technical context


Published on

Presentation given at: La preservación del patrimonio digital: conceptos básicos y principales iniciativas, Ministerio de Cultura, Madrid, Spain, March 15th, 2006

Published in: Technology, Education
  • Be the first to comment

The digital preservation technical context

  1. 1. The digital preservation technological context Michael Day, Digital Curation Centre UKOLN, University of Bath [email_address] La preservaci ón del patrimonio digital: conceptos básicos y principales iniciativas , Madrid, 14-16 March 2006
  2. 2. Session overview <ul><ul><ul><li>Introductory comments </li></ul></ul></ul><ul><ul><ul><li>Technical issues </li></ul></ul></ul><ul><ul><ul><li>Preservation strategies </li></ul></ul></ul><ul><ul><ul><li>Preservation metadata and shared infrastructure </li></ul></ul></ul>
  3. 3. Introductory comments
  4. 4. Digital preservation (1) <ul><ul><li>Concerns continued access (and use) </li></ul></ul><ul><ul><li>Digital preservation is NOT just about technology </li></ul></ul><ul><ul><li>Unites a range of interrelated issues: </li></ul></ul><ul><ul><ul><li>“ ... the planning, resource allocation, and application of preservation methods and technologies to ensure that digital information of continuing value remains accessible and usable” - Margaret Hedstrom (1998) </li></ul></ul></ul>
  5. 5. Digital preservation (2) <ul><ul><li>Is sometimes now characterised as 'digital stewardship' or 'digital curation' </li></ul></ul><ul><ul><ul><li>The concept of data curation originated in data-rich scientific domains like bioinformatics </li></ul></ul></ul><ul><ul><ul><li>Curation - &quot;The activity of managing and promoting the use of data from its point of creation, to ensure it is fit for contemporary purpose, and available for discovery and reuse&quot; - Philip Lord, et al . (2004) </li></ul></ul></ul><ul><ul><ul><li>&quot;Maintaining and adding value to a trusted body of information for current and future use&quot; -- DCC presentation at CNI (2005) </li></ul></ul></ul>
  6. 6. The fragility of digital content The main technical issues
  7. 7. General comments <ul><ul><li>Digital information is dependent on its technical environment </li></ul></ul><ul><ul><li>Physical objects are subject to: </li></ul></ul><ul><ul><ul><li>Physical deterioration </li></ul></ul></ul><ul><ul><ul><li>Technology obsolescence </li></ul></ul></ul><ul><ul><li>Relatively short timescales </li></ul></ul>
  8. 8. Storage media (1) <ul><ul><ul><li>A major focus of concern in the 1970s and 1980s </li></ul></ul></ul><ul><ul><ul><li>Current media types </li></ul></ul></ul><ul><ul><ul><ul><li>Typically, magnetic or optical tape and disks, various devices (e.g., memory sticks) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Examples include: CD-ROM, DVD (optical), DAT, DLT (magnetic) </li></ul></ul></ul></ul><ul><ul><ul><li>Unknown lifetimes </li></ul></ul></ul><ul><ul><ul><ul><li>Subject to differences in quality or storage conditions </li></ul></ul></ul></ul><ul><ul><ul><ul><li>But relatively short lifetimes compared to paper or good quality microform </li></ul></ul></ul></ul>
  9. 9. Storage media (2) <ul><ul><ul><li>Technical solutions: </li></ul></ul></ul><ul><ul><ul><ul><li>Periodic copying of data bits on to new media or types of media (refreshing) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Longer lasting media </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Migrating to good-quality microform or paper (!) </li></ul></ul></ul></ul><ul><ul><ul><li>In an organised preservation system, regular routines (quality checking, backup, replication, refreshing, etc.) will help solve the media longevity issue </li></ul></ul></ul>
  10. 10. Technology obsolescence (1) <ul><ul><ul><li>A set of much bigger problems </li></ul></ul></ul><ul><ul><ul><li>Software dependence </li></ul></ul></ul><ul><ul><ul><ul><li>Digital content is, at least in part, dependent on the configurations of hardware and software (applications and operating systems) that were originally used to interpret or display them </li></ul></ul></ul></ul><ul><ul><ul><li>Hardware and software obsolescence </li></ul></ul></ul><ul><ul><ul><ul><li>Application software and operating systems are upgraded regularly </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Hardware becomes obsolete or needs repair </li></ul></ul></ul></ul>
  11. 11. Technology obsolescence (2) <ul><ul><ul><li>Technical solutions </li></ul></ul></ul><ul><ul><ul><ul><li>Various preservation strategies have been developed to cope with the obsolescence problem </li></ul></ul></ul></ul><ul><ul><ul><ul><li>For the most part, these depend on the existence of a continual programme of active management (life cycle management) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Supported by systems that implement the various functional entities identified by the Reference Model for an Open Archival Information System (OAIS) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Preservation strategies can only be seen in this wider context </li></ul></ul></ul></ul>
  12. 12. Layers of meaning (1) <ul><ul><ul><li>Digital objects are logical entities not fixed to any one particular physical carrier </li></ul></ul></ul><ul><ul><ul><li>Three layers (Thibodeau, 2002): </li></ul></ul></ul><ul><ul><ul><ul><li>Physical objects: the actual bits stored on a particular medium </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Logical objects: defines how these bits are used by application software, based on data types (e.g. ASCII); in order to understand (or preserve) the byte-streams, we need to know how to process them </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Conceptual objects: what humans deal with in the real world, meaningful units of information </li></ul></ul></ul></ul>
  13. 13. Layers of meaning (2) <ul><ul><ul><li>On which of these layers should preservation activities focus? </li></ul></ul></ul><ul><ul><ul><ul><li>We need to preserve the ability to reproduce the objects, not just the bits </li></ul></ul></ul></ul><ul><ul><ul><ul><li>In fact, we could change the bits and logical representation and still reproduce an authentic conceptual object </li></ul></ul></ul></ul>
  14. 14. Authenticity and integrity <ul><ul><ul><li>Digital information can easily be changed (e.g., by design or accident) </li></ul></ul></ul><ul><ul><ul><li>How can we trust that an object is what it claims to be? </li></ul></ul></ul><ul><ul><ul><li>Mechanisms are available at the bit level (e.g. checksums), but will this be sufficient? </li></ul></ul></ul>
  15. 15. Problems of scale <ul><ul><ul><li>An increasing flood of 'born-digital' data </li></ul></ul></ul><ul><ul><ul><ul><li>Data deluge in science and engineering </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Petabytes generated by high throughput instruments, streamed from sensors and satellites, etc. </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>The World Wide Web </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Comprises billions of pages + &quot;deep Web&quot; </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Internet Archive = >1 petabyte, and growing @ 20 Tb. per month ( </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>5 exabytes of new information created in 2002: </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li> projects/how-much-info-2003/ </li></ul></ul></ul></ul></ul>
  16. 16. Some general principles (1) <ul><ul><li>Most of the technical problems associated with long-term digital preservation can be solved if a life-cycle management approach is adopted </li></ul></ul><ul><ul><ul><li>i.e. a continual programme of active management </li></ul></ul></ul><ul><ul><ul><li>Ideally, combines both managerial and technical processes, e.g., as in the OAIS Model </li></ul></ul></ul><ul><ul><ul><li>Many current systems (e.g. repository software) are attempting to support this approach </li></ul></ul></ul><ul><ul><ul><li>Preservation strategies need to be seen in this wider context </li></ul></ul></ul><ul><ul><li>Preservation needs to be considered at a very early stage in an object's life-cycle </li></ul></ul>
  17. 17. Some general principles (2) <ul><ul><li>Need to identify and understand the 'significant properties' of an object </li></ul></ul><ul><ul><ul><ul><li>Focuses on the essential </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Helps with choosing an acceptable preservation strategy </li></ul></ul></ul></ul><ul><ul><li>Encapsulation may have some benefits </li></ul></ul><ul><ul><ul><ul><li>Surrounding the digital object - at least conceptually - with all of the information needed to decode and understand it (including software) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Produces autonomous 'self-describing' objects, reduces external dependencies; linked to the Information Package concept in the OAIS Reference Model </li></ul></ul></ul></ul><ul><ul><li>Keep the original byte-stream in any case </li></ul></ul>
  18. 18. Digital preservation strategies
  19. 19. Preservation strategies <ul><ul><li>Three main families: </li></ul></ul><ul><ul><ul><li>Technology preservation </li></ul></ul></ul><ul><ul><ul><li>Technology emulation </li></ul></ul></ul><ul><ul><ul><li>Information migration </li></ul></ul></ul><ul><ul><li>Also: </li></ul></ul><ul><ul><ul><li>Digital archaeology (rescue) </li></ul></ul></ul>
  20. 20. Technology preservation <ul><ul><ul><li>The preservation of an information object together with all of the hardware and software needed to interpret it </li></ul></ul></ul><ul><ul><ul><ul><li>Successfully preserves the look, feel and behaviour of the whole system (at least while the hardware and software still functions) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>May have a role for historically important hardware </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Problems with storage and ongoing maintenance, missing documentation </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Would inevitably lead to 'museums' of “ageing and incompatible computer hardware” -- Mary Feeney </li></ul></ul></ul></ul><ul><ul><ul><ul><li>May have a short-term role for supporting the rescue of digital objects (digital archaeology) </li></ul></ul></ul></ul>
  21. 21. Technology emulation (1) <ul><ul><ul><li>Preserving the original bit-streams and application software; running this on emulator programs that mimic the behaviour of obsolete hardware </li></ul></ul></ul><ul><ul><ul><li>Emulators change over time </li></ul></ul></ul><ul><ul><ul><ul><li>Chaining, rehosting </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Emulation Virtual Machines </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Running emulators on simplified 'virtual machines' that can be run on a range of different platforms </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Virtual machines are migrated so the original bit-streams do not have to be </li></ul></ul></ul></ul></ul>
  22. 22. Technology emulation (2) <ul><ul><ul><li>Benefits: </li></ul></ul></ul><ul><ul><ul><ul><li>Technique already widely used, e.g. for emulating different hardware, computer games </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Preserves the original bits </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Reduces the need for regular object transformations (but emulators and virtual machines may themselves need to be migrated) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Retains ‘look-and-feel’ </li></ul></ul></ul></ul><ul><ul><ul><ul><li>May be the only approach possible where objects are complex or dependent on executable code </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Less 'understanding' of formats is needed; little incremental cost in keeping additional formats </li></ul></ul></ul></ul>
  23. 23. Technology emulation (3) <ul><ul><ul><li>Issues </li></ul></ul></ul><ul><ul><ul><ul><li>Which organisations have the technical skills necessary to implement the strategy? </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Preserving 'look and feel' may not be needed for all objects </li></ul></ul></ul></ul><ul><ul><ul><ul><li>It will be difficult to know definitively whether user experience has been accurately preserved </li></ul></ul></ul></ul><ul><ul><ul><li>Conclusions </li></ul></ul></ul><ul><ul><ul><ul><li>Promising family of approaches </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Needs further practical application and research </li></ul></ul></ul></ul>
  24. 24. Information migration (1) <ul><ul><ul><li>Managed transformations </li></ul></ul></ul><ul><ul><ul><ul><li>A set of organised tasks designed to achieve the periodic transfer of digital information from one hardware and software configuration to another, or from one generation of computer technology to a subsequent one - CPA/RLG report (1996) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Abandons attempts to keep old technology (or substitutes for it) working </li></ul></ul></ul></ul><ul><ul><ul><ul><li>A 'known' solution used by data archives and software vendors (e.g., a linear migration strategy is used by software vendors for some data types, e.g. Microsoft Office files) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Focuses on the content of objects </li></ul></ul></ul></ul>
  25. 25. Information migration (2) <ul><ul><ul><li>Main types (from OAIS Model) </li></ul></ul></ul><ul><ul><ul><ul><li>Refreshment </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Replication </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Repackaging </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Transformation </li></ul></ul></ul></ul><ul><ul><ul><li>Issues </li></ul></ul></ul><ul><ul><ul><ul><li>Labour intensive </li></ul></ul></ul></ul><ul><ul><ul><ul><li>There can be problems with ensuring the 'integrity and authenticity' of objects </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Transformations need to be documented (part of the preservation metadata) </li></ul></ul></ul></ul>
  26. 26. Information migration (3) <ul><ul><ul><li>Uses </li></ul></ul></ul><ul><ul><ul><ul><li>Seems to be most suitable for dealing with large collections of similar objects </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Migration can often be combined with some form of standardisation process, e.g., on ingest </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>ASCII </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Bit-mapped-page images </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Well-defined XML formats </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Migration on Request (CAMiLEON project) </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Keep original bits, migrate the rendering tools </li></ul></ul></ul></ul></ul>
  27. 27. Digital archaeology <ul><ul><ul><li>Not so much a preservation strategy, but the default situation if we fail to adopt one </li></ul></ul></ul><ul><ul><ul><li>Using various techniques to recover digital content from obsolete or damaged physical objects (media, hardware, etc.) </li></ul></ul></ul><ul><ul><ul><ul><li>A time consuming process, needs specialised equipment and (in most cases) adequate documentation </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Considered to be expensive (and risky) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Remains an option for content deemed to be of value </li></ul></ul></ul></ul>
  28. 28. Choosing a strategy (1) <ul><ul><ul><li>Preservation strategies are not in competition (different strategies will work together) </li></ul></ul></ul><ul><ul><ul><ul><li>A suggestion that we should keep the original bits (with documentation) in any case </li></ul></ul></ul></ul><ul><ul><ul><li>But the strategy chosen has implications for: </li></ul></ul></ul><ul><ul><ul><ul><li>The technical infrastructure required (and metadata) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Collection management priorities </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Rights management </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>e.g, Owning the rights to re-engineer software </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Costs </li></ul></ul></ul></ul>
  29. 29. Choosing a strategy (2) <ul><ul><ul><li>Tools for supporting preservation decisions, e.g. </li></ul></ul></ul><ul><ul><ul><ul><li>Preservation strategies </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Target formats for transformations </li></ul></ul></ul></ul><ul><ul><ul><li>Nationaal Archief (Netherlands) testbed project </li></ul></ul></ul><ul><ul><ul><li>Vienna University of Technology utility analysis tool </li></ul></ul></ul><ul><ul><ul><li>Both developed further by the Digital Preservation cluster of the DELOS Network of Excellence </li></ul></ul></ul>
  30. 30. Case study Rescue of content from BBC Domesday videodiscs
  31. 31. Rescue of BBC Domesday (1) <ul><ul><li>BBC Domesday project (1986) </li></ul></ul><ul><ul><ul><li>To commemorate the 900th Anniversary of the original Domesday survey </li></ul></ul></ul><ul><ul><ul><li>Two interactive videodiscs (12&quot;) </li></ul></ul></ul><ul><ul><ul><ul><li>Mixture of textual material (some produced by schools), maps, statistical data, images and video </li></ul></ul></ul></ul><ul><ul><ul><li>Technical basis: </li></ul></ul></ul><ul><ul><ul><ul><li>Hardware: BBC Master Series microcomputer and Philips Laservision (LV-ROM) player </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Some software in ROM chip, others on the discs </li></ul></ul></ul></ul><ul><ul><ul><ul><li>System obsolete by end of 1990s; working hardware becoming more difficult to find </li></ul></ul></ul></ul>
  32. 32. Rescue of BBC Domesday (2) <ul><ul><ul><li>CAMiLEON project </li></ul></ul></ul><ul><ul><ul><ul><li>Proof of concept for the emulation approach </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Converted data into media-neutral form </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Adapted an existing emulator for the BBC microcomputer to render Domesday content </li></ul></ul></ul></ul><ul><ul><ul><li>The National Archives (and partners) </li></ul></ul></ul><ul><ul><ul><ul><li>Reengineered the whole system for use on Windows PCs </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Digital versions of images and video converted from original master tapes (still held by BBC) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Developed an improved interface </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Web version: </li></ul></ul></ul></ul>
  33. 36. Preservation metadata and shared infrastructures
  34. 37. Preservation metadata (1) <ul><ul><li>All digital preservation strategies depend - to a greater or lesser extent - on the creation, capture and maintenance of metadata </li></ul></ul><ul><ul><ul><li>Preservation metadata: </li></ul></ul></ul><ul><ul><ul><ul><li>The &quot;information a repository uses to support the digital preservation process,&quot; specifically &quot;the functions of maintaining viability, renderability, understandability, authenticity, and identity in a preservation context&quot; (PREMIS Data Dictionary, 2005) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Cuts across older categorisations of metadata (descriptive, administrative, structural) </li></ul></ul></ul></ul>
  35. 38. Preservation metadata (2) <ul><ul><li>PREMIS Working Group </li></ul></ul><ul><ul><ul><li>Preservation Metadata: Implementation Strategies </li></ul></ul></ul><ul><ul><ul><li>Working Group sponsored by OCLC and RLG </li></ul></ul></ul><ul><ul><ul><li>Reviewed earlier Metadata Framework document and existing practice </li></ul></ul></ul><ul><ul><ul><li>Focused on implementation and definition of 'core' metadata </li></ul></ul></ul><ul><ul><ul><li>PREMIS Data Dictionary (May 2005) </li></ul></ul></ul>
  36. 39. Preservation metadata (3) <ul><ul><ul><li>PREMIS Data Dictionary </li></ul></ul></ul><ul><ul><ul><ul><li>Less explicitly based on OAIS Information Model structure than older OCLC/RLG Framework </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Based on own data model </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Defines some of the semantic units for: Objects, Events, Agents, Rights </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Supports automatic capture, where possible </li></ul></ul></ul></ul><ul><ul><ul><li>PREMIS also provides: </li></ul></ul></ul><ul><ul><ul><ul><li>An XML implementation, e.g. for use in a packaging format like METS (Metadata Encoding and Transmission Standard) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Maintenance activity (Library of Congress) </li></ul></ul></ul></ul>
  37. 40. Shared infrastructures <ul><ul><ul><li>For example: registries for sharing information about, or for identifying or validating formats, etc. </li></ul></ul></ul><ul><ul><ul><ul><li>There is &quot;… a pressing need to establish reliable, sustained repositories of file format specifications, documentation, and related software&quot; (Lawrence, et al ., 2000) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>DSpace 'bitstream format registry' </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Global Digital Format Registry (GDFR) </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Some components exist, e.g. Typed Object Model, JHOVE tool </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>DCC Representation Information registry </li></ul></ul></ul></ul>
  38. 41. Some final comments <ul><ul><li>The technical issues of digital preservation are only one part of a multidimensional problem </li></ul></ul><ul><ul><li>Progress has been made on addressing technical problems </li></ul></ul><ul><ul><li>Need for sustainability and co-operation </li></ul></ul><ul><ul><li>Need for people with the appropriate skills </li></ul></ul>
  39. 42. Acknowledgements <ul><li>UKOLN is funded by the Museums, Libraries and Archives Council, the Joint Information Systems Committee (JISC) of the UK higher and further education funding councils, as well as by project funding from the JISC, the European Union and other sources. UKOLN also receives support from the University of Bath, where it is based: </li></ul><ul><li>The Digital Curation Centre is funded by the JISC and the UK e-Science Programme: </li></ul>