Preservation Functionality in a Digital Archive Erik Oltmans Koninklijke Bibliotheek Raymond J. van Diessen IBM Business Consulting Services Hilde van Wijngaarden Koninklijke Bibliotheekv presented by: Martin Klein 04/14/2005

Outline e-Depot Preservation Subsystem Preservation Manager Preservation Layer Model View Paths / File Type Specification In Reality – The User Interface State of the Art / Conclusion

Introduction National Library of the Netherlands – Koninklijke Bibliotheek (KB) digital archiving system – e-Depot collaboration with IBM (NL) agreements with scientific publishers Preservation Manager added

e-Depot KB specified system requirements for OAIS based deposit system IBM delivered Digital Information Archiving System (DIAS) KB maintains service called e-Depot using DIAS workflow for archiving electronic publications validating & pre-processing of digital content gernerating & resolving id's searching & retrieving publications user identification, authentification & authorization

e-Depot (2) offline media (CD-ROM) “installables” CD-ROM installed on reference workstations (RWS) image generated including sofware & OS manual cataloguing and storing in e-Depot online media (electronic articles) send on tapes to KB or download via FTP

e-Depot (3) IAAIAA End User Metadata (Identifier) D I A S Catalogu e Storage Publisher Post office Metadata Content SIP Error Recovery

Preservation Subsystem Preservation Manager technical metadata of file format needed to render information Preservation Processor process of automatic migration of inaccessible formats Permanent Access Toolbox (PATbox) tools to ensure long-term access to electronic publications approach of Universal Virtual Computer (UVC)

Preservation Subsystem (2) Permanent Access Toolbox Preservation Processor Preservation Manager Preservation Subsystem SIPDIP Packaging & Delivery Access Data Management AIP Ingest AIP AdministrationMonitoring & Logging Archival Storage Delivery & Capture Data

Preservation Manager stores technical metadata for every file format in the e-Depot separate technical metadata from publications objectives: identify e-publications in danger of becoming inaccessible planning preservation activities (migration, emulation) specifying software & hardware environment to render content technical metadata structured according to Preservation Layer Model (PLM) and registered in View Paths PLM defines template for description of rendering environment View Path contains actual instance of a rendering path for a specific file format

Preservation Manager (2) 6 steps to define metadata in this framework: define: (1) attributes (2) layers (3) Preservation Layer Model (4) View Path (5) File Type Identification (6) Associate File Type Identification with View Path

Preservation Layer Model builds on the “von Neumann” computer architecture series of layers, build on functionality provided by previous layer to render any electronic publication layers can be identified  Reference Platform Operating System Viewer Application Data Format

Windows PDF viewer PDF version 1.2 Pentium 2 Pentium 3 Win 98Win 95 Win XP Preservation Layer Model (2) data format viewer application operating system platform

View Path format specific technical metadata is called View Path all file formats in e-Depot need at least on View Path multiple View Path for one file type possible categories to define the quality of different View Paths based on authenticity criteria high – matches perfectly medium – matches most low – matches

File Type Specification used to identify the different file formats (stored in e- Depot) link between files and View Path – stored in Table of Contents (TOC) publication has XML based TOC to specify name and file type unique File Type ID generated to associate file format with metadata defines in View Path => the only reference between metadata and electronic publication

The User Interface

The User Interface (2)

The User Interface (3)

The User Interface (4)

KB - State of the Art initially no preservation system in e-Depot included standalone version of Preservation Manager implemented – still testing ~47 file formats recognized over journals and 6 mio articles implemented export mechanism for interoperability

Finally... KB implemented concept of deposit system based on OAIS store publications and deal with metadata refering to layer model maintaining PLM and View Paths to avoid inaccessibility KB made some steps

References Preservation Functionality in a Digital Archive; Oltmans, E., van Diessen, J. Raymond, van Wijngaarden, Hilde, 2004 Digital Preservation at the Koninklijke Bibliotheek, van Wijngaarden, Hilde The e-Depot: Current Status & Developments, Oltmans, E. From Manifestation to Content - The selection policy of the National Library of the Netherlands, Amse, Anne Katrien