slide1 l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
CITRA 2010 PowerPoint Presentation
Download Presentation
CITRA 2010

Loading in 2 Seconds...

play fullscreen
1 / 13

CITRA 2010 - PowerPoint PPT Presentation


  • 142 Views
  • Uploaded on

Planning a trusted digital repository Case: Norway. CITRA 2010. 1) New storage system at The National Archives of Norway 2) The definition and management of archival packages ( specifications from the joint Norwegian DIAS project ). Oslo 15.09.2010 Trond Sirevåg

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'CITRA 2010' - risa


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1
Planning a trusted digital repository

Case: Norway

CITRA 2010

1) New storage system at The National ArchivesofNorway

2) The definition and managementofarchivalpackages (specifications from the joint Norwegian DIAS project)

Oslo 15.09.2010

Trond Sirevåg

The National Archives of Norway

planned storage system at the na 1
Planned storage system at the NA (1)

Inner closed zone

Closed zone

Classified records

Dedicated equipment

(No communication with SDR)

Specially protected room

Protected equipment with no direct external communication

  • Storage system:
  • SAN (Storage Area Network) with disk system and 2 tape-robots
  • Only accessible for dedicated staff in separate, closed nerwork
  • Purpose:
  • Secure storage
  • Ingest and maintenance of archival packages
  • No user-services and no external access

Secured Digital Repository (SDR)

Archival packages

(originals – not for user-services)

Tape

robot 2

Tape

robot 1

Disk-system

Access for specially authorized staff - only

Access for dedicated maintenance staff - only

planned storage system at the na 2
Planned storage system at the NA (2)

Same repository room

Inner closed zone

Closed zone

Open zone

Classified records

Secured Digital Repository (SDR)

Archival packages

(originals – not for user-services)

Accessible Repository

User-copies from SDR

(DIPs – Dissimination Information Packages)

Dedicated equipment

(No communication with SDR)

Tape

robot 2

Tape

robot 1

Disk-system

Disk-system

Protected equipment with no direct external communication

Accessible from Local Area Net-work – But no Internet connection

Specially protected room

Access for specially authorized staff - only

Access for dedicated maintenance staff - only

Access for NA staff and user-services. – A service outside Digital Repository is used for Internet distribution

core function management of archival packages aips
Core function:Management of archival packages (AIPs)

Archival packages mgmt. system

Sluice

Sluice

  • The SAN management system:
  • Management confined to digital objects: migration of bits and blocks, and the copying of tar-files to tape + verification.
  • Archival objects management:
  • Generates and maintains AIPs
  • Incorporates AIPs in repository (SDR)
  • Controls gates (”sluices”) between zones

Classified records

Secured Digital Repository (SDR)

Archival packages - Versions for long-term storage

Accessible Repository

DIPS (User-versions/copies)

ingest the process
Ingest – the process

AIP incorporation

Archival packages mgmt. system

Sluice

Sluice

AIP generattion

Technical test

SIP control &

Quarantine

Incoming SIP

Classified records

Secured Digital Repository (SDR)

Archival packages - Versions for long-term storage

Accessible Repository

DIPS (User-versions/copies)

Testing area.

Acquisition control

The Archival management system and the SIP control area are located within the closed zone

the definition and management of archival packages in norwegian state and municipal repositories
The definition and management of archival packages in Norwegian state and municipal repositories
  • Specifications from the DIAS project (Digital Archival Structure)
  • A project carried out jointly in 2010 by The National Archives and 4 municipal and intermunicipal archives: Oslo, Bergen, the counties of Trøndelag and the county of Møre and Romsdal - funded by ABM-utvikling (ABM Development)
dias archival packages basic standards 1
DIAS Archival PackagesBasic standards (1)

The OAIS model (ISO 14721)

A package in which an archival object is stored as a self-contained unit

and in which the archival object is permanently connected with:

logical metadata (preservation metadata to understand it, and

technical metadata to read and present it

Package Information

Preservation Description Information

(Logical metadata)

Content Information

Data object

(Data files)

Representation Information

(Techn. metadata)

dias archival packages basic standards 2
DIAS Archival PackagesBasic standards (2)
  • TRAC - Trustworthy Repository Audit and Certification - Criteria and Checklist (2007)
    • Additional requirements to ensure the sustained integrity and authenticity of objects in repository custody
  • TRAC-requirements in DIAS:
    • Acquisitions (SIPs) should be preserved unchanged (within AIPs)
    • If the repository transforms AIP content, a new AIP should be generated and preserved in addition to the former
    • All files within AIPs should have connected checksums
dias package model
DIAS Package model

DIAS uses AICs – Archival Information Collections – to connect different versions of an AIP

Original versjon included SIP

Transformed version (1)

Transformed version (2)

User version

implementation standards
Implementation standards
  • METS - Metadata Encoding & Transmission Standard
    • To describe the structure of packages
  • PREMIS - Preservation Metadata: Implementation Strategies
    • Metadata to support identity, understandability and authenticity
  • DIAS conclusions:
    • METS is used as package header og container
    • PREMIS is used for Preservation metadata
    • PREMIS is embedded in METS (via admSec)
    • Binary files are not converted to Base64
    • tar-format is used as container-format

The use of METS and PREMIS enables a standard XML Schema to generate archival packages according to the DIAS model

the dias archival package schema
The DIAS Archival package schema

Makes archival package generation independant of storage system and -technology

The DIAS structure should be able to describe the whole variety of transfers from state and municipal agencies

Users may also specify schema extensions

The DIAS schema can also be used for SIP- and DIP generation

Common tools may be developped to support package generation and package update

The DIAS-project specifies requirements to management system

Common schema and common tools enables organized education

management system requirements 1
Management system requirements (1)

Import files/objects and incorporate them in archival package

Generate checksums for files/objects

Generate PREMIS metadata files, METS file and tar file

Generate package (SIP, AIP) according to DIAS schema

Generate AIC package by connecting AIPs

Generate user version of package (DIP)

Generate checksum for total package (SIP/AIP/AIC/DIP)

Place/store total checksum outside package (AIC)

management system requirements 2
Management system requirements (2)

Extract information from package for export (defined functions)

Manage storage: write to chosen storage media/architecture – also in multiple copies

Collect (import) archival package from storage medium

Update archival package (AIP, AIC, DIP)

Verify checksums

Log collection (import) and generation of packages and their incorporation and location in repository

Give overview of stored packages (or packages written to the different storage media)

Produce reports on operations and stored packages