Fedora Commons Overview and Future Plans

1
Fedora Commons Overview and Future Plans
Sandy Payette, Executive Director Cornell
University Library Metadata Working Group June
13, 2008
2
A Brief History
501(c)(3) Non-profit
2005
2012
2001
2007
Community, Partners, Donors
Moore
Mellon
Mellon
Major Funders
Mellon
3
Use Cases We Support
Scholarly Communication
Data Curation and Linking
Science
Humanities
Preservation and Archiving
Semantic Knowledge Spaces
R.D.W. Connor
4
Users of Fedora Commons open source
softwarehttp//fedora.info/wiki/index.php/Fedora
_Commons_Community_Registry

• National Libraries and Archives
• University Libraries and Archives
• Research Institutions
• Museums and Culture Organizations
• Semantic and Virtual Digital Libraries
• National Repository Consortia
• Publishing and Professional Societies
• Medical Centers and Libraries
• Government Agencies

5
How?
Web 2.0
Your Applications
Scholarly and e-Research
Other
Digital Libraries
Archive
Asset Management
Fedora Services and Middleware Layer
OAI
Search
Ingest
Fedora Repository
Etc.
Storage Layer
Other
Fast Disk
Honeycomb
6
Working Together with Target Communities
FC 2008 Community Solution Councils
open access publication
data curation
preserve/archive
e-research
7
Current Collaborative Engagements
TALKING
data curation
open access
PLANNING
DRSG
DOING
EOL
PLoS
JHU
ORE
IA
e-research
FIZ
archiving
Sun
NSDL
Hull
UVA
BHL
Oxford
Rutgers
Adore
DSpace
BNF
Portico
Aquifer
CUL
preservation
Kuali
institutional repo
Sakai
8

• Technology Perspective

9
Fedora Commons Open Source Projects

• Fedora Repository Project
• The original Fedora Project
• Fedora Middleware Project
• Service integration and enterprise-orientation
  for repositories
• Akubra Storage Project
• New storage plug-in architecture transactional
  file system
• Topaz Project
• Incubated project persistence service based on
  semantic triplestore
• Mulgara Triplestore Project
• Independent, but FC supports developer highly
  scalable triplestore

Fedora Commons open source projects can be
integrated together.
10
Fedora Repository Key Features

• Digital Object Model
• Aggregate content datastreams in an object any
  type of content
• Intermix both local content and external content
• Relationships among digital objects (via RDF)
• Register content models for known object
  patterns
• Repository Service
• Modular
• Web service interfaces (REST/SOAP)
• Versioning
• Dynamic service binding based on object content
  model types
• File-centric (all essential characteristics in
  XML files)
• RDF-based indexing (semantic triplestore index
  with query)
• Security with pluggable authentication and XACML
  policies
• Journaling (replay all events to create replicas
  of repository)

11
Basic Building Block Fedora Digital Object Model
(relationships and properties)
Persistent ID
DC
RELS-EXT
Reserved Datastreams
Audit Trail
Policy
Datastream 1
Datastream 2
Datastreams (any type, any number)
Datastream n
12
Forming Collections with relationships
isMemberOfCollection
isMemberOfCollection
isMemberOfCollection
Smiley Stuff Collection Object
13
Digital Objects... with compositional
relationships
14
Digital Objects information network
scholarly object
hasPart
annotates
hasPart
providesContext
Amazon Web Service
library content
External commercial web content
15
Fedora Repository Service For creating,
managing, providing access to various and sundry
objects
Fedora APIs (SOAP and REST)
Manage API
Access API
Registry Search
RDF Query
Ingest
Manage
Access
Validate
Policy
CMABind
RDF Index
Store
Registry
Triplestore
File system (Objects)
RDBMS (Registry)
16

• Roadmap Perspective

17
http//www.fedora-commons.org/resources/roadmap.ph
p
18
Roadmap Active Themes

• Ease of use
• Re-use and interoperability
• Web orientation
• Improved modularity
• Pluggable storage
• Workflow engine
• Messaging
• RDF and Semantic technologies
• Content models
• Solution bundles (including end-user
  applications)

19
2008 Notable Themes

• Solution bundle out of box application for
  repositories
• IR2 (Institutional Repository Application
  Take 2)
• Institutional repository ? moving towards
  enabling e-research
• Turn-key out of box user experience
• Means of achieving (2 strategies under
  consideration)
• FC and community developers build a brand new
  application
• Fedora DSpace collaboration
• Easy fit repositories behind the collaborative
  web
• Motivation enable seamless integration with
  e-research applications (e.g., Zotero) and enable
  re-use and sharing of repository content
• Object Reuse and Exchange (ORE) libraries
• Lightweight interfaces on Fedora repository
• Lightweight web protocol on Fedora repository
  (e.g., Atom, SWORD)

20
Better integration with web and workflows
Fedora APIs (SOAP and REST)
Manage API
Access API
Registry Search
RDF Query
Ingest
Manage
Access
Additional APIs SWORD (2008) APP (full) ?
JSR 170 ? Other ?
Validate
Policy
CMABind
RDF Index
Store
Registry
Triplestore
File system (Objects)
RDBMS (Registry)
21
Replication to Archival Storage

• Replica repositories, each with different
  underlying storage system useful for failover,
  redundancy, archiving
• Now Fedora Journaling http//fedora.info/download
  /2.2.1/userdocs/server/journal/index.html
• Future Journal Event Messaging via Fedora JMS

Follower Repository
Leader Repository
Journal Event Log
API events
API events
Sun Honeycomb
Can configure multiple followers
22
Better Service Integration
First, we are providing simple messaging (via
ActiveMQ in Fedora 3.0)
services listen and consumeevents or other
messages
GSearch
OAI
Simple JMS
Ingest
repository publishes events
More
Next, lightweight integration with workflow
engine(s) orchestration
23
The Model-Driven Repository Content Models and
Service Models
Persistent ID
DC
RELS-EXT
Audit Trail
Policy
Image
Preserve Metadata
Custom Metadata
24
Runtime dynamic services available on all
objects that conform to the content model
Persistent ID
DC
RELS-EXT
Get-Thumbnail-Size-Image Get-Web-Size-Image Get-Hi
gh-Resolution-Image
Audit Trail
Policy
Image
Preserve Metadata
Custom Metadata
25
Akubra Project backend storage interoperability
Fedora Repository Service
File system (Objects)
RDBMS (registry)
Triplestore (Mulgara/MPTStore)
26
(No Transcript)
27
(No Transcript)
28

• Elevator Speak Takeaway

29
Sloganfest 2008 Simple Message
30
www.fedora-commons.org