Case Study: PREMIS and DAITSS - PowerPoint PPT Presentation

About This Presentation
Title:

Case Study: PREMIS and DAITSS

Description:

Title: PREMIS - Preservation Metadata: Implementation Strategies Working Group Author: Brian Lavoie Last modified by: Priscilla Created Date: 7/22/2003 9:46:26 PM – PowerPoint PPT presentation

Number of Views:136
Avg rating:3.0/5.0
Slides: 13
Provided by: Brian893
Learn more at: https://www.loc.gov
Category:

less

Transcript and Presenter's Notes

Title: Case Study: PREMIS and DAITSS


1
Case Study PREMIS and DAITSS
  • May, 2011

2
  • DAITSS in use by Florida Digital Archive since
    2005
  • OAIS-based preservation repository system
  • Employs normalization and forward migration
  • Roughly 300,000 AIPS, 30 million files, 80 TB
  • Recently completely re-written (DAITSS 2.0)
  • DAITSS 2 follows PREMIS closely
  • Objects, Agents, Events
  • Data Model
  • Schema

3
Preservation Metadata in DAITSS
  • PREMIS metadata and format-specific technical
    metadata supplied (extracted/created) by system
  • Every package (AIP and DIP) has a METS descriptor
  • PREMIS is embedded in the METS descriptor
  • Format-specific technical metadata uses standard
    schema (where possible) treated as
    objectCharacteristicsExtension

4
A snippet of format information in the AIP
Descriptor
5
PREMIS Objects
  • Representation objects
  • AIP can contain 1,2 or 3 representations
  • Each has a separate StructMap in METS
  • Each has minimal PREMIS metadata
  • File objects
  • All PREMIS semantic units except for environment
  • Descriptions recorded in PREMIS and extensions
  • Bitstream objects
  • Described like File objects
  • Only for certain embedded bitstreams

6
PREMIS Events
  • PREMIS Events considered part of permanent
    provenance
  • Document stages of processing and actions on
    packages, e.g. submit, virus check, validate,
    normalize, migrate, ingest, disseminate, etc.
  • Stored in AIP descriptor file within the AIP so
    in Archival Storage and AIP Store
  • Also stored (selectively) in fast access database

7
Event information in the AIP Descriptor
8
Operations (Ops) Events
  • For tracking, problem-solving, operations audit
    trail
  • SIP rejected, ingest started, ingest finished,
    ingest snafu, disseminate started, disseminate
    finished, report sent, fixity success, fixity
    failure, etc.
  • Stored in DAITSS database, but not in AIP

9
PREMIS Agents
  • Used to document software agents
  • lt!-- premis agent --gt
  • ltagentgt
  • ltagentIdentifiergt
  • ltagentIdentifierTypegtURIlt/agentIdentifie
    rTypegt
  • ltagentIdentifierValuegtinfofda/daitss/des
    cription/v0.2.1lt/agentIdentifierValuegt
  • lt/agentIdentifiergt
  • ltagentNamegtFormat Description
    Servicelt/agentNamegt
  • ltagentTypegtWeb Servicelt/agentTypegt
  • ltagentNotegt
  • built with JHOVE 1.6 (built on January 24, 2001),
    DROID 3.0 with DROID signature file version 34.
  • lt/agentNotegt
  • lt/agentgt

10
Repository Exchange Package (RXP)
  • Common exchange format for transferring AIP from
    one repository to another
  • Use cases
  • Succession
  • Diversification
  • Software migration
  • Assumes repositories understand
  • structure of METS
  • semantics of PREMIS

11
RXP Structure
rxp root/ base of the RXP hierarchy. rxp.xml
(METS) descriptor for RXP rxp-digiprov.xml
(PREMIS) provenance for RXP. rxp-rep-n.xml
(METS) descriptor for senders representation(s)
. One file per representation. rxp-rep-n-digpro
v.xml (PREMIS) provenance for representation n.
files/ contains representation files
rxp root/
12
  • FDA and DAITSS information
  • http//fclaweb.fcla.edu/FDA_landing_page
  • RXP (TIPR) information
  • http//wiki.fcla.edu8000/TIPR
  • pcaplan_at_ufl.edu
Write a Comment
User Comments (0)
About PowerShow.com