Fedora and the Preservation of University Electronic Records Project NHPRC Electronic Records...

Fedora and the Preservation of University Electronic Records

ProjectNHPRC Electronic Records Research Grant

Kevin L. GlickManuscripts and Archives, Yale University

Eliot WilczekRobert Dockins

Digital Collections and Archives, Tufts University

SCOPAThe Standing Committee on Professional Awareness

Yale University Libraries

March 31, 2006

Fedora and the Preservation of University Electronic Records Project

MSSA Yale University & DCA Tufts University

SCOPA March 31, 2006

Introduction

Project Goals

Project Participants

Project Funding




Introduction

Requirements for Recordkeeping & Preservation

Conceptualization of Ingest

Conceptualization of Maintenance

Fedora Analysis and Development

Overall Plan of Work




Ingest Guide

Negotiate Submission Agreement

Transfer and Validate

Ingest Guide




Ingest Guide

Establish Relationship

Define Project

Collect Information and Assess Value of Records

Assess Record Types

Assess Formats

Assess Identifier Rules

Assess Copyright

Assess Access Rights

Assess Recordkeeping System

Assess Feasibility

Finalize Submission Agreement

Negotiate Submission Agreement




Ingest Guide

Create and Transfer SIP

Validate

Transform and Attach Metadata

Formulate AIPs

Assess AIPs

Formally Accession

Transfer and Validate




Ingest Projects




Ingest Guide

Carefully documents accessioning

Regularizes decision-making steps

Semi-automated & Scaleable

Arsenal of Resources

Using the Ingest Guide




Maintain Guide

What is Maintenance

Collaboration

Contract for Services

Overview




Maintain Guide

Scheduled Event Types

Irregular Event Types

Maintain Guide




Maintain Guide

Incremental Backup of Administrative Metadata

Full Backup of Administrative Metadata

Full Backup of Records Components Store

Verify AIP Consistency

Verify Records Components

Check Access and Retention Status

Report on Media Life

Hardware Tests and Maintenance Window

Security Audit

Scheduled Event Types




Maintain Guide

Digital Object Accession

Retrieval Request

Query Request

Metadata Update Request

Format Transform Request

Remove Record Component Request

Preservation Application Hardware Environment Replacement

New AIP Format and/or New Preservation Application

New Records Component Store

Add Additional Representation Information

Change Standard Computing Platform

Irregular Event Types




Maintain Guide

Refresh Records Components Media

Respond to Checksum Failure

Respond to Media Failure: Records Component Store

Respond to Data Loss: Record Component Store

Respond to AIP Consistency Failure

Respond to Media Failure: Administrative Metadata Store

Respond to Data Loss: Administrative Metadata Store

Respond to Unintentional Data Damage

Respond to Security Breach

Irregular Event Types (cont.)




Fedora Evaluation

A software framework for building applications

A “philosophy” about digital assets

A collaborative community

What is Fedora?




Fedora Evaluation

A finished application

Provides pieces to assemble into complete applications

What is Fedora not?




Fedora Evaluation

Atomic Unit is “Digital Object”

Digital Objects Contain “Datastreams”

Have “Disseminators” that contain “Methods”

Relationships to other objects, forming network

Fedora Object Model




Fedora Evaluation

Datastreams = Instance Fields

Disseminators = Interfaces

Disseminator Methods = Object Methods

Relationships = Object References/Pointers

Fedora & Object

Oriented Programming




Fedora Evaluation

No! Fedora only a framework for building applications

Is Fedora a Records Preservation Application?




Fedora Evaluation

Short answer: Yes, with some work

Long answer: Provides good basis for storage & delivery Additional services needed to help support preservation activities and manage restrictions and disposition

Can Fedora support a records preservation

application?




Fedora Evaluation

Provide additional services to support records preservation and management

Become highly reliable Storage Uptime and Access

Fedora Improvements to Satisfy Maintain

Guide




Fedora Evaluation

Integrate with identity management systemsEASY

Integrate administrative data with automated actions and access restrictionsMODERATE

Richer support for action trackingMODERATE

Confidential Destruction of records componentsHARD

Services Fedora Needs




Fedora Evaluation

Consistency testing, error discovery/recovery MODERATE

High uptime featuresHARD

Reliability Features




Conclusions & Future DirectionsGeneralizable Findings

Development of Tools

Reassessment of Yale University Archives

Future Research Projects?

Fedora and the Preservation of University Electronic Records

ProjectNHPRC Electronic Records Research Grant

Kevin L. GlickManuscripts and Archives, Yale University

Eliot WilczekRobert Dockins

Digital Collections and Archives, Tufts University

SCOPAThe Standing Committee on Professional Awareness

Yale University Libraries

March 31, 2006

Thank You

Fedora and the Preservation of University Electronic Records Project NHPRC Electronic Records...

Documents

Transcript of Fedora and the Preservation of University Electronic Records Project NHPRC Electronic Records...