Fedora Overview

Fedora-Commons Repository
A brief overview
Etienne Posthumus, DPO, TU Delft Library 08-06-09

What is it?
Fedora is a general-purpose, open-source digital object repository system.

What is it?
"Flexible Extensible Digital Object Repository Architecture"
NOT the Linux distribution

What is it?
…a persistence and service delivery platform

What is it?
…a persistence and service delivery platform
…implemented as a set of Java services (Tomcat)

What is it?
A well-funded active community with a long history.

Conforms to the OAIS reference model
Open Archival Information System
- an ISO model defined by Consultative Committee for Space Data Systems widely adopted in Archives community
Built on sub-systems Open Source, Open Standards

Persistent digital archive ‘files on disk’
bootstrappeable in the face of disaster
XML containers
asset management

XML containers
asset management
Scaleable triple-store
Mulgara

XML containers
asset management
Scaleable triple-store
Mulgara
Service delivery
XSLT via Saxon built-in
others pluggable

Advantages?
Scaling
Integrated Asset management
Extensive Versioning
Audit trails
Large(ish) community, esp. mindshare
General ‘fit and polish’
Goal is support for > 10 million objects

Downsides?
It’s a toolbox not a complete solution (front-end support)
Java code base (for some this is an advantage ;-)
Moving target in terms of innovation (also debatable)
Complexity of some concepts, steep learning curve
A lot of DIY is needed

Digital Object Model
Compound objects, aggregate items per object

Some ‘reserved’ item IDs

Some ‘reserved’ item IDs
Essentially an XML container

Digital Object Model <foxml:digitalObject PID="demo:31" VERSION="1.1" xmlns:foxml="info:fedora/fedora-system:def/foxml#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="info:fedora/fedora-system:def/foxml# http://www.fedora.info/definitions/1/0/foxml1-1.xsd"> <foxml:objectProperties> <foxml:property NAME="info:fedora/fedora-system:def/model#state" VALUE="Active"/> <foxml:property NAME="info:fedora/fedora-system:def/model#ownerId" VALUE="fedoraAdmin"/> <foxml:property NAME="info:fedora/fedora-system:def/model#createdDate" VALUE="2008-07-02T05:09:42.015Z"/> <foxml:property NAME="info:fedora/fedora-system:def/view#lastModifiedDate" VALUE="2008-07-02T05:09:42.015Z"/> </foxml:objectProperties> <foxml:datastream CONTROL_GROUP="X" ID="DC" STATE="A" VERSIONABLE="true"> <foxml:datastreamVersion CREATED="2008-07-02T05:09:43.328Z" FORMAT_URI="http://www.openarchives.org/OAI/2.0/oai_dc/" ID="DC1.0" LABEL="Dublin Core Record for this object" MIMETYPE="text/xml"> <foxml:xmlContent> <oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"> <dc:title>Apache Batik 1.5 Demo Directory</dc:title> <dc:creator>Chris Wilper</dc:creator> <dc:creator>The Apache Group</dc:creator> <dc:subject>svg</dc:subject> <dc:publisher>The Apache Group</dc:publisher> <dc:format>image/svg+xml</dc:format> <dc:identifier>demo:31</dc:identifier> <dc:relation>http://xml.apache.org/batik/</dc:relation> <dc:rights>The Apache License</dc:rights> </oai_dc:dc> </foxml:xmlContent> </foxml:datastreamVersion> </foxml:datastream> <foxml:datastream CONTROL_GROUP="E" ID="DS1" STATE="A" VERSIONABLE="true"> <foxml:datastreamVersion CREATED="2008-07-02T05:09:43.328Z" ID="DS1.0" LABEL="Local copy of batikBatik.svg" MIMETYPE="image/svg+xml"> <foxml:contentLocation REF="http://www.fedora-commons.org/demo/misc/batikBatik.svg" TYPE="URL"/> </foxml:datastreamVersion> </foxml:datastream> An Example

Content Model Architecture “ an integrated structure for persisting and delivering the essential characteristics of digital objects in Fedora” Modelling behaviours and structure of objects. Complicated, fairly new, not widely implemented yet, in flux. … can also be safely ignored when starting out. (which we did not realise)

Fedora at TU Delft Library
Used to create a repository Infrastructure

Fedora at TU Delft Library
Used to create a Repository Infrastructure
Multiple projects:
Institutional Repository (academic output)
Special Collections (Tresor, bouwkunde dias)
Expert Search (finding People)
3TU Datacentrum

Implementation
Front-end is Django application

Implementation
We use the REST API for communication

Implementation
Middleware as Python code providing a web API

Implementation
MOAI flexible OAI-PMH service

Implementation
MOAI flexible OAI-PMH service
Indexing via SOLR subsequently linked to DISCOVER

Conversion of existing repository
Legacy Stellent CMS stored in Oracle
Circa 12000 items
Mostly PDF plus metadata
Conversion scripts in Python
Bulk ingest

Community Participation
NL Fedora Usergroup
Contact with key Fedora participants at conferences
Presentations and workshop
Developer days planned
Possible collaboration on development
Sponsorship of open-source components

Plans
Convert existing repository with existing functionality
Incrementally build in new features on ongoing basis
Extend APIs and services
Linked Data repository
More innovative repository applications

Questions?
[email_address]
http://www.fedora-commons.org/

Fedora Overview

by eposthumus

Accessibility

Categories

Upload Details

Usage Rights

1 Embed 2

Statistics

Fedora Overview Presentation Transcript