Fedora Overview

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

3 comments

Comments 1 - 3 of 3 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

2 Favorites

Fedora Overview - Presentation Transcript

  1. Fedora-Commons Repository
    • A brief overview
    Etienne Posthumus, DPO, TU Delft Library 08-06-09
  2. What is it?
    • Fedora is a general-purpose, open-source digital object repository system.
  3. What is it?
    • Fedora is a general-purpose, open-source digital object repository system.
    • "Flexible Extensible Digital Object Repository Architecture"
    • NOT the Linux distribution
  4. What is it?
    • Fedora is a general-purpose, open-source digital object repository system.
    • …a persistence and service delivery platform
  5. What is it?
    • Fedora is a general-purpose, open-source digital object repository system.
    • …a persistence and service delivery platform
    • …implemented as a set of Java services (Tomcat)
  6. What is it?
    • Fedora is a general-purpose, open-source digital object repository system.
    • 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
    Built on sub-systems Open Source, Open Standards
    • Persistent digital archive ‘files on disk’
    • bootstrappeable in the face of disaster
    • XML containers
    • asset management
    • Scaleable triple-store
    • Mulgara
    Built on sub-systems Open Source, Open Standards
    • Persistent digital archive ‘files on disk’
    • bootstrappeable in the face of disaster
    • XML containers
    • asset management
    • Scaleable triple-store
    • Mulgara
    • Service delivery
    • XSLT via Saxon built-in
    • others pluggable
    Built on sub-systems Open Source, Open Standards
  7. 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
  8. 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
  9. Digital Object Model
    • Compound objects, aggregate items per object
  10. Digital Object Model
    • Compound objects, aggregate items per object
    • Some ‘reserved’ item IDs
  11. Digital Object Model
    • Compound objects, aggregate items per object
    • Some ‘reserved’ item IDs
    • Essentially an XML container
  12. Digital Object Model <foxml:digitalObject PID=&quot;demo:31&quot; VERSION=&quot;1.1&quot; xmlns:foxml=&quot;info:fedora/fedora-system:def/foxml#&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation=&quot;info:fedora/fedora-system:def/foxml# http://www.fedora.info/definitions/1/0/foxml1-1.xsd&quot;> <foxml:objectProperties> <foxml:property NAME=&quot;info:fedora/fedora-system:def/model#state&quot; VALUE=&quot;Active&quot;/> <foxml:property NAME=&quot;info:fedora/fedora-system:def/model#ownerId&quot; VALUE=&quot;fedoraAdmin&quot;/> <foxml:property NAME=&quot;info:fedora/fedora-system:def/model#createdDate&quot; VALUE=&quot;2008-07-02T05:09:42.015Z&quot;/> <foxml:property NAME=&quot;info:fedora/fedora-system:def/view#lastModifiedDate&quot; VALUE=&quot;2008-07-02T05:09:42.015Z&quot;/> </foxml:objectProperties> <foxml:datastream CONTROL_GROUP=&quot;X&quot; ID=&quot;DC&quot; STATE=&quot;A&quot; VERSIONABLE=&quot;true&quot;> <foxml:datastreamVersion CREATED=&quot;2008-07-02T05:09:43.328Z&quot; FORMAT_URI=&quot;http://www.openarchives.org/OAI/2.0/oai_dc/&quot; ID=&quot;DC1.0&quot; LABEL=&quot;Dublin Core Record for this object&quot; MIMETYPE=&quot;text/xml&quot;> <foxml:xmlContent> <oai_dc:dc xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:oai_dc=&quot;http://www.openarchives.org/OAI/2.0/oai_dc/&quot;> <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=&quot;E&quot; ID=&quot;DS1&quot; STATE=&quot;A&quot; VERSIONABLE=&quot;true&quot;> <foxml:datastreamVersion CREATED=&quot;2008-07-02T05:09:43.328Z&quot; ID=&quot;DS1.0&quot; LABEL=&quot;Local copy of batikBatik.svg&quot; MIMETYPE=&quot;image/svg+xml&quot;> <foxml:contentLocation REF=&quot;http://www.fedora-commons.org/demo/misc/batikBatik.svg&quot; TYPE=&quot;URL&quot;/> </foxml:datastreamVersion> </foxml:datastream> An Example
  13. 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)
  14. Fedora at TU Delft Library
    • Used to create a repository Infrastructure
  15. 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
  16. Implementation
    • Front-end is Django application
  17. Implementation
    • Front-end is Django application
    • We use the REST API for communication
  18. Implementation
    • Front-end is Django application
    • We use the REST API for communication
    • Middleware as Python code providing a web API
  19. Implementation
    • Front-end is Django application
    • We use the REST API for communication
    • Middleware as Python code providing a web API
    • MOAI flexible OAI-PMH service
  20. Implementation
    • Front-end is Django application
    • We use the REST API for communication
    • Middleware as Python code providing a web API
    • MOAI flexible OAI-PMH service
    • Indexing via SOLR subsequently linked to DISCOVER
  21.  
  22. Conversion of existing repository
    • Legacy Stellent CMS stored in Oracle
    • Circa 12000 items
    • Mostly PDF plus metadata
    • Conversion scripts in Python
    • Bulk ingest
  23. 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
  24. 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
  25. Questions?
    • [email_address]
    • http://www.fedora-commons.org/

+ eposthumuseposthumus, 8 months ago

custom

493 views, 2 favs, 0 embeds more stats

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 493
    • 493 on SlideShare
    • 0 from embeds
  • Comments 3
  • Favorites 2
  • Downloads 11
Most viewed embeds

more

All embeds

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories