Notes
Slide Show
Outline
1
Plans and Early Progress for
Ensuring Access To Mathematics Over Time
(EATMOT)
  • Marcy E. Rosenkrantz
  • Cornell University Library
  • Markus Enders
  • Göttingen State and University Library


2
Outline
  • Background and history of CU-Göttingen collaborations
  • Project goals and work Plan
  • Early progress
  • Plans and Open Questions
  • Acknowledgements


3
CUL-Gottingen Collaborations
  • Cornell, Göttingen, Michigan Math Books Project
  • The EMANI Project
  • Digital Math Library/European Digital Math Library
  • EATMOT
4
Project Goals and Work Plans
  •  Build interoperable, jointly managed digital archives of mathematics serial literature
  • 3-year effort
  • yr 1: OAIS metadata package development, internal message passing
  • yr 2: Prototype development
  •    yr 3: Working system, implement interoperability and joint management


5
Overview of the OAIS Model
6
Composite of all OAIS functions, grouped by “Functional Entities”
7
Early Progress
  • Stories – a page from Extreme Programming
  • Message passing
  • Metadata
  • (Journals, permissions, and ingest formats)


8
Three Stories
  • Develop Packaging Designs and Migration Plans
  • Establish Standards and Policies
  • Develop Preservation Strategies and Standards
  • Administer Database
  • Co-ordinate Access Activities
  • Generate DIP


  • Receive Data
  • Co-ordinate Updates
  • Error Checking
  • Manage Storage Hierarchy


  • Receive Submission
  • Generate AIP
  • Quality Assurance
  • Archival Information Update
  • Audit Submission


9
Three “Stories”
10
Story 2 – “Update Storage”
11
Story 2 – “Update Storage” (detail)
12
Story 2 – “Update Storage” (with relationships)
13
Story 2 – “Update Storage” (with messages)
14
Story 2 – “Update Storage” (with categorized messages)
15
Current situation at the
Digitization Center of SUB Göttingen
16
Archive information
17
Technical solution for long-time archiving
18
KOPAL
19
Architecture
20
Metadata Framework
21
AGORA DMS
22
Plans and Open Questions
  • What’s Next—Negotiating the Boundaries
    • How will we share the technical components of the archive?
    • How will we share the Preservation Planning functions
      • Local preservation policies may conflict
    • How will Administration work?
23
Acknowledgements
  • National Science Foundation Award # 0240450
  • Teammates: Bill Kehoe, Marty Kurth, Nancy McGovern, David Ruddy, Markus Enders, Olaf Brandt, David Fielding, Heike Neuroth, Frank Klaproth, Andrea Rapp, Tom Hickerson


24
 
25
Sample Storage Confirmation Message
26
Error Log
27
AIP used as Storage Confirmation message
28
AIP snippet
29
 Functional Entity Groups
  •  Ingest
  •  Storage
  •  Data Management
  •  Access
  •  Administration
  •  Preservation Planning
30
OAIS Functions – 1
  • Ingest
  • Receive Submission
  • Quality Assurance
  • Generate Archival Information Package
  • Generate Descriptive Information
  • Coordinate Updates


  • Archival Storage
  • Receive Data
  • Manage Storage Hierarchy
  • Replace Media
  • Error Checking
  • Disaster Recovery
  • Provide Data


  • Data Management
  • Administer Database
  • Perform Queries
  • Generate Report
  • Receive Database Updates


  • Preservation Planning
  • Monitor Designated Community
  • Monitor Technology
  • Develop Preservation Strategies and Standards
  • Develop Packaging Designs and Migration Plans


31
OAIS Functions – 2
  • Administration
  • Negotiate Submission Agreement
  • Manage System Configuration
  • Archival Information Update
  • Physical Access Control
  • Establish Standards and Policies
  • Audit Submission
  • Activate Requests
  • Customer Service


  • Common Services
  • Operating System services
  • Network services
  • Security services


  • Access
  • Coordinate Access Activities
  • Generate Dissemination Information Package
  • Deliver Response