Day 2, workshop 4, Inge Van Nieuwerburgh
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Day 2, workshop 4, Inge Van Nieuwerburgh

on

  • 3,412 views

 

Statistics

Views

Total Views
3,412
Views on SlideShare
3,409
Embed Views
3

Actions

Likes
1
Downloads
11
Comments
1

2 Embeds 3

https://twitter.com 2
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • good contains all the achiving basics associated with experience
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 100.000 tapes uit de jaren ‘70 en ‘80 in Toulouse space center
  • Selection!
  • zie ook seal of approval DANS An OAIS is an archive, consisting of an organization of people and systems, that has accepted the responsibility to preserve information and make it available for a Designated Community
  • Submission Information package Archival Information Package Dissemination Information Package
  • zie ook seal of approval DANS An OAIS is an archive, consisting of an organization of people and systems, that has accepted the responsibility to preserve information and make it available for a Designated Community

Day 2, workshop 4, Inge Van Nieuwerburgh Presentation Transcript

  • 1. (meta)data standards for digital archiving DISH 2009 @ Rotterdam Universiteitsbibliotheek Gent – MMLab UGent
  • 2. Summary
      • Introduction
      • Defining the problem
      • State of the art:
        • OAIS
        • Data formats
        • Metadata schemas
        • Declarative containers
      • Layered Metadata Model
      • Best practices
  • 3. Introduction
  • 4. BOM Vl: Preservation and disclosure of multimedia data in Flanders
      • Flemish project – 1.5 years
      • Cross sectoral: broadcasters, archival institutions, cultural sector and the libraries.
      • Studies:
      • Needs for preservation
      • Selection
      • Metadata standards & exchange formats
      • Digital rights
      • Supply and distribution models
  • 5. Defining the problem
  • 6. Problems when archiving digital information
    • Problem 1 .
      • Analogous formats are disappearing and have to be replaced by digital alternatives.
      • Quick growth of data.
      • Discrepancy between the short life span of digital technology and the need for long term archiving.
  • 7. Problems when archiving digital information
    • Problem 2 .
      • In digital form, information is abstract , independent from the storage medium. The abstract information has to be preserved, not the medium.
  • 8. Problems when archiving digital information
    • But also consider…
  • 9. Growth Storage capacity of desktop computers (HanKwang 2008)
  • 10. Evolution of used file formats (PRONOM) 1980 1990 2000 ‘ 86 – TIFF3 ’ 87 ‘88 TIFF4 & 5 ‘ 92 – TIFF6 ‘ 96 - PNG 1.0 ’ 99 – PNG 1.2 ’ 00 - JPEG2000 ‘ 92 - JPEG ’ 87 – GIF87 ’ 87 – GIF89 ‘ 92 - MrSID ‘ 85 - BMP ‘ 84 - TGA ‘ 03 - SVG ’ 84 - GEM Raster
  • 11. Evolution format derivatives
    • MIME type image/tiff:
    • TIFF (alle versies)
    • TIFF/IT
    • TIFF G4/LZW/UNC
    • Digital Negative Format (DNG)
    • GeoTIFF
    • Pyramid TIFF
    Bron: PRONOM Technical Registry [http://www.nationalarchives.gov.uk/pronom/]
  • 12. Riscs at the long term Bit Errors/Bugs File Format Changes Time Changing Technology Organizational changes Interpretation of the format 1980 1990 2000
  • 13. Study: state of the art (meta)data standards
  • 14.
    • What is a digital archive NOT :
      • mass storage for active applications and data
      • a networked backup solution
    • What is a digital archive:
      • Storage of digital information with historical , scientific , financial or legal value in the long term.
      • Platform independent access to digital information for 50, 100 years or longer .
    What is a digital archive?
  • 15. OAIS
  • 16. Open Archival Information System (OAIS)
    • Reference model for the description of digital archives.
    • Developed in 1982:
      • NASA (US)
      • ESA (EU)
      • RSA (USSR)
      • NASDA (Japan)
    • Since 2002 ISO Standard 14721
  • 17. OAIS model
    • Consists of 3 parts:
      • Description of an archival system : responsabilities, procedures and a common terminology.
      • Functional model : all processes needed for the longterm preservation of digital information.
      • Information model : describes the stored digital information.
  • 18. OAIS functional model
  • 19.
    • Need to explore the necessary, recommended and generally used standards
      • technical schemas
      • descriptive schemas
      • preservation schemas
      • structural schemas
    • What are the different metadata schemas (if any) used in the different cultural sectors?
    Standards
  • 20. Data formats
  • 21. What
    • Raw data is increasingly storage consuming
    • Need to compress: compression standards
      • video: Mpeg-2, H.264/Mpeg-4 AVC, Motion JPEG2000
      • audio: MP3, AAC
      • images: JPEG, TIFF
    • Need for container formats for exchange of A/V material
      • MXF, AVI, WMA, MP4
  • 22. Metadata schemas
  • 23. What
    • Descriptive metadata
    • Administrative metadata
    • Preservation metadata
    • Technical metadata
    • Usage data
  • 24. Standards
    • Especially for descriptive metadata: differences in sectors
      • => Preferred standard per sector?
      • Differences in detail
      • Differences in structure
      • Differences in relations
    • Preservation metadata: PREMIS
    • Conceptual models
  • 25. Declarative containers
  • 26. What
    • Compound information objects, combining descriptive, administrative and/or structural metadata
    • Advantage: the ease to exchange and reuse them
    • some examples:
      • METS
      • MPEG-21 DIDL: describe complex digital objects
      • LOM: learning objects
      • ORE: model to describe aggregations
  • 27. Layered Metadata Model
  • 28. How to proceed?
    • Need for a layered metadata model to manage digital archive
    • Why? Too much differences between data models
    • Need a common ground
  • 29. Solution: layered metadata model
    • Model in different layers:
      • A generic top level descriptive metadata schema (DC)
      • A refined standard per sector for detail, to preserve the metadata in detail
      • + Preservation metadata, technical metadata and rights metadata
  • 30. Layered metadata model MARCXML TIFF PSD Descriptive metadata: Dublin Core Preservation metadata: PREMIS Rights metadata: PREMIS, MPEG-21/REL, INDECS, ODRL, XrML Technical metadata: PREMIS, MPEG-7, Z38.87, AudioMD, VideoMD, TextMD MARC Standard TIFF Standard
  • 31. Layered Metadata Model
    • Descriptive Model: Dublin Core
    • Most interoperable, cross sectoral.
    • Greatest common divider of all metadata models.
    • All fields are repeatable and optional.
        • Mapping between own metadata model.
    • Dublin Core as pidgin:
      • DC as common layer above the own metadata.
      • DC as model for querying.
      • Discovery and identification of digital objects.
  • 32. Layered Metadata Model
    • Descriptive Model: Dublin Core
    • How to disseminate as DC?
    • Crosswalk to DC is made for the most important metadata models used in the sectors:
    • Libraries: MARC21
    • A/V Sector: P/Meta
    • Arts sector and museums: CDWA and SPECTRUM
    • Archiving sector: ISAD(G) and EAD
    • Crosswalks can be used to disseminate the DC records via OAI-PMH, GRDDL(XSLT), mapping API (D2RQ), or ontology linking.
  • 33. Layered Metadata Model
    • Preservation Model: PREMIS
    • Administrative metadata + Rights Metadata
    •  assisting in the management of the digital objects.
    • Technical metadata
    •  assisting the access (conversions or emulation).
    • Preservation Metadata
    •  Tracking the provenance – history of all actions on an object.
  • 34. Layered Metadata Model Preservation Model: PREMIS
  • 35. Layered Metadata Model
    • Preservation Model: PREMIS
    • Objects: Describes the objects to be preserved in a technical manner.
    • 3 subclasses:
        • Bitstream
        • File
        • Representation
    • Facilitates the conversion or emulation process.
  • 36. Layered Metadata Model
    • Preservation Model: PREMIS
    • Objects:
        • Describes the objects to be preserved in a technical manner.
        • 3 subclasses:
          • Bitstream
          • File
          • Representation
        • Facilitates the conversion or emulation process.
  • 37. Layered Metadata Model
    • Preservation Model: PREMIS
    • Agents:
        • Aggregates information about agents (persons, organisations, software) associated with rights management and preservation events in the life of a data object .
        • No direct relation between Agent and Object:
          • May hold or grant one or more rights
          • May carry out, authorize, or compel one or more events.
        • Identify agents uniquely.
  • 38. Layered Metadata Model
    • Preservation Model: PREMIS
    • Events:
        • Actions that modify objects should always be recorded. Other actions such as copying an object for backup purposes may be recorded in an Event entity.
        • Stored separately from the digital object.
  • 39. Layered Metadata Model
    • Preservation Model: PREMIS
    • Rights:
        • The minimum core rights information that a preservation repository must know, however, is what rights or permissions a repository has to carry out actions related to objects within the repository.
        • These may be granted by copyright law, by statute , or by a license agreement with the rightsholder.
  • 40. Layered Metadata Model
    • Preservation Model: PREMIS
    • Intellectual Entity:
        • Descriptive metadata: out of scope for PREMIS.
        • Dublin Core
  • 41. Layered Metadata Model
    • Preservation Model: PREMIS
    • PREMIS OWL:
        • Semantic (OWL) ontology following the data dictionary of PREMIS 2.0.
        • Published Online:
        • http://multimedialab.elis.ugent.be/users/samcoppe/ontologies/Premis/premis.owl
        • Documentation Online:
        • http://multimedialab.elis.ugent.be/users/samcoppe/ontologies/Premis/index.html
  • 42. Best practices Or How to minimize risks
  • 43. B est Practice # 1: Store technical metadata Bron: Adrian Brown, National Archives UK; “Developing Practical Approaches to Active Preservation”
  • 44. Bitrot/Software errors
    • No storage device is perfect and eternal.
    • David Rosenthal Stanford University “Bit Preservation: A Solved Problem?”
    • Bit half-life of 8 x 10^17 year => gives 50 % chance that 1 Petabyte survives a century without errors.
    • Comparable studies by Carnegie Mellon University, Google and CERN
  • 45. Bitrot/Software errors
    • Volker Heydegger University of Cologne
    • Analysing the Impact of File Formats on Digital Integrity
  • 46. B est Practice # 2: Preserve preservation metadata
    • Checksums
    • Digital Signatures
    • Provenance
  • 47. Interpretation riscs One of the coolest and oldest dwarf stars ever been found.
  • 48. B est Practice # 3: Representation metadata
    • Time
    • Place
    • Wave lengths/Calibration data
    • Provenance
  • 49. Technology Changes + = Documentation Information Syntax Semantics 4b50 0403 0014 0000 0008 0cdb 282e 7d22 ddaa 0243 0001 ab00 0002 000f 0000 6341 5f65 666f INC $D020 DEC $D020 JMP $2000 LDX $D020 INX STX $D020 JMP $2000 LDA $5000
  • 50. B est Practice # 4: Do not trust software
    • It is an illusion to think that software will always offer access to the archived data.
    • Computer software is an active component in the archive and it knows only two possible states:
      • It works and is maintained .
      • It does not work and is not maintained .
  • 51. B est Practice # 4: Do not trust software (cont.)
    • Case 2: Software does not work, is not maintained:
      • Documentation metadata has to contain the source code of the original software.
      • Emulation has to be foreseen; metadata has to contain all the emulation parameters .
    • Case 1: Software works, is maintained:
      • The archive has the software.
      • The user has the software.
      • Both cases have a dynamic metadata layer with all the software aspects needed to access the data.
  • 52. Descriptive metadata
    • Are descriptive metadata (or other access tools like thumbnails, previews) data or metadata ?
    • Non-discussion: ‘metadata’ is a relative term.
    • as Data:
      • Advantage : descriptive metadata are ‘core business’, too valuable not to be archived.
      • Disadvantage : this type data is very dynamic.
    • as Metadata :
      • Advantage : metadata are dynamic; can be adapted to the needs of the archive.
      • Disadvantage : which descriptive model have to be used: MARC, EAD, P/META,…?
  • 53. B est Practice # 5: Store descriptive metadata as data Provide a broadly accepted descriptive model like Dublin Core
    • Dublin Core describes the ‘Who’, ‘What’,’Where’, ‘When’ and ‘How’.
    • Sector specific descriptive metadata models have finer granularity.
    • Use international standards (MARC, EAD, P/Meta).
  • 54. Want to know more? Book (in dutch): “ (Meta)datastandaarden voor digitale archieven full-text available book “, Bastijns, Paul; Coppens, Sam; Corneillie, Siska; Hochstenbach, Patrick et al. , ( 2009 ); http://hdl.handle.net/1854/LU-480734 Deliverable Layered metadata model: http://hdl.handle.net/1854/LU-764194
  • 55. Q & A