1. Flexible Extensible Digital Object Repository Architecture

2. Introduction to Fedora
An Open-Source Digital Repository Management System.
Fedora demonstrates how distributed digital library architecture can be deployed using web-based technologies, including XML and Web services.
Developed jointly by UVA and Cornell University.

3. Digital Content: not just documents ...
Some conventional objects
Complex, compound, dynamic objects

4. Why Fedora? (1) Digital Object Model Distributed Repositories
Abstraction: model for heterogeneous digital resources
Flexible: create different “content models”
Generic: no bifurcation of metadata and content
Aggregation: both locally stored content items and by-reference content items
Extensible: associate services with objects (extensible behavior interfaces)
Distributed Repositories
Interoperable object serialization (defined by XML schema)
Common web service APIs for access and management
Federation for distributed, virtual collections
Object Lifecycle Management (archive and preservation)
XML ingest, storage, and export
Content versioning
Object-to-Object relationships
Event history

5. Why Fedora? (2) Content repurposing Web Services
Provide multiple views of content/metadata
Dynamic transformations of content/metadata
Add new views/transformations over time
Web Services
Fedora is exposed via web services
Fedora can interact with other web services
Fedora uses WSDL to define interfaces and XML transmission
Easy integration with other applications and systems
Does not assume any particular workflow or end-user application
Generic repository service as substrate for many kinds of applications

6. Digital Object Model Architectural View
Digital object identifier
Persistent ID (
PID )
Service Perspective:
methods for disseminating “views” of content
Default Disseminator
Your Extension
Your Extension
Item Perspective:
Set of content or metadata items
Datastream (item)
Datastream (item)
Datastream (item)
Internal: key metadata necessary to manage the object
System
Metadata

7. Digital Object Model Service Relationships
Persistent ID (PID)
Service Definition
Metadata (WSDL)
System
Metadata
Datastreams
Behavior Definition
Object
behavior
subscription
Persistent ID (PID)
System
Metadata
Datastreams
Disseminators
Data Object
Behavior Mechanism
Object
Persistent ID (PID)
Service Binding
Metadata (WSDL)
System
Metadata
Datastreams
data contract
behavior contract
External
Service

8. How Users Access Digital Objects

9. Repository Managers have direct access to each component of a data object.

10. Fedora’s Architecture

11. A Running Fedora Demo

12. A Running Fedora Demo

13. A Running Fedora Demo

14. Questions?
For technical problems, feel free to contact me: