Transcript Slide 1
Fedora and the Preservation of University Electronic Records Project NHPRC Electronic Records Research Grant Kevin L. Glick Manuscripts and Archives, Yale University Eliot Wilczek Robert Dockins Digital Collections and Archives, Tufts University SCOPA The 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 Introduction Project Goals Project Participants Project Funding SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Introduction Overall Plan of Work Requirements for Recordkeeping & Preservation Conceptualization of Ingest Conceptualization of Maintenance Fedora Analysis and Development SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Ingest Guide Ingest Guide Negotiate Submission Agreement Transfer and Validate SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Ingest Guide Negotiate Submission Agreement 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 SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Ingest Guide Transfer and Validate Create and Transfer SIP Validate Transform and Attach Metadata Formulate AIPs Assess AIPs Formally Accession SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Ingest Projects SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Ingest Guide Using the Ingest Guide Carefully documents accessioning Regularizes decision-making steps Semi-automated & Scaleable Arsenal of Resources SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Maintain Guide Overview What is Maintenance Collaboration Contract for Services SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Maintain Guide Maintain Guide Scheduled Event Types Irregular Event Types SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Maintain Guide Scheduled Event Types 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 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Maintain Guide Irregular Event Types 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 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Maintain Guide Irregular Event Types (cont.) 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 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Fedora Evaluation What is Fedora? A software framework for building applications A “philosophy” about digital assets A collaborative community Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Fedora Evaluation What is Fedora not? A finished application Provides pieces to assemble into complete applications Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Fedora Evaluation Fedora Object Model Atomic Unit is “Digital Object” Digital Objects Contain “Datastreams” Have “Disseminators” that contain “Methods” Relationships to other objects, forming network Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Fedora Evaluation Fedora & Object Oriented Programming Datastreams = Instance Fields Disseminators = Interfaces Disseminator Methods = Object Methods Relationships = Object References/Pointers Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University Fedora Evaluation Is Fedora a Records Preservation Application? No! Fedora only a framework for building applications SCOPA March 31, 2006 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Fedora Evaluation Can Fedora support a records preservation application? 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 Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Fedora Evaluation Fedora Improvements to Satisfy Maintain Guide Provide additional services to support records preservation and management Become highly reliable Storage Uptime and Access Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Fedora Evaluation Services Fedora Needs Integrate with identity management systems EASY Integrate administrative data with automated actions and access restrictions MODERATE Richer support for action tracking MODERATE Confidential Destruction of records components HARD Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Fedora Evaluation Reliability Features Consistency testing, error discovery/recovery MODERATE High uptime features HARD Fedora and the Preservation of University Electronic Records Project MSSA Yale University & DCA Tufts University SCOPA March 31, 2006 Conclusions & Future Directions Generalizable Findings Development of Tools Reassessment of Yale University Archives Future Research Projects? Fedora and the Preservation of University Electronic Records Project NHPRC Electronic Records Research Grant Thank You Kevin L. Glick Manuscripts and Archives, Yale University Eliot Wilczek Robert Dockins Digital Collections and Archives, Tufts University SCOPA The Standing Committee on Professional Awareness Yale University Libraries March 31, 2006