Fedora/Hydra (and DSpace)

From CURATEcamp
Jump to: navigation, search

Breakout Session Notes from CurateCAMP SE (Atlanta 2012)

  • Review of Hydra, Islandora and other Fedora applications
  • Fedora security implementations:
    • FeSL implementation at UNC
    • Ruby-based security at Indiana
    • storing permissions in SOLR for faster access
    • fedoraAdmin account vs. real users in the audit trail
  • Ingest considerations
    • admin client
    • uses of Fedora java message service
  • storage implementations
    • EMC's Akubra module
    • iRODS Akurbra module
    • hierarchal storage and storage hints

Conceptualizing the Discussion

  1. Layers
    • Storage
      • Triple-store Solutions
        • Mulgara
        • Jena
    • Search/Index
    • Metadata
    • Workflow
    • Presentation


  1. What options are there for authentication and access control?
  2. What are some of the benefits and pitfalls of particular approaches?
  3. How will Fedora behave in a linked-data world? What capabilities will it provide?
  4. Can something other than Fedora (ie. Mulgara) be used for triple-store metadata?
  5. What is the extent of transaction management within Fedora?
  6. How does Fedora handle large (30-40GB) data streams?


  1. For linked data, we must structure the Fedora architecture in such a way as to provide a framework for linked data
    • What specifically does this entail?
    • Triple-store metadata can be setup to something like Mulgara but it must be setup manually (through something like Trippi, a layer between triple-store and Fedora)
  2. JMS (Java messaging service) can be used for transaction management, but it is not quite atomic.
  3. There is something called "Fedora Management Data Streams" for handling large data streams, accessible via REST API.

Fedora Related Software

  1. Blacklight
    • Solr tool for searching, indexing, faceting.
    • Being used to manage multiple Voyager implementations at Wisconsin University schools.
  2. Islandora
    • A Drupal based front-end for Fedora.
    • Collection level editing
    • Some built-in workflows
    • Compatible with Drupal 5 & Drupal 6 (not Drupal 7).
  3. Fedora Enhanced Security Layer (FESL)
  4. Akubra
    • Storage Abstraction Layer for Fedora
    • Can utilize IRODS, S3, NAS, etc
    • Can enable "hinting" for destinations
  5. Fedora Enhanced Content Models
    • Enables some content validation abilities
  6. Active Fedora
  7. Opinionated Metadata (OM)
    • Nokogiri - Ruby XML Library
  8. Solrizer
  9. Hydrangia
    • Example Hydra implementation
  10. Hydraulics
    • Pipelines for "getting stuff in" (digitization)
  11. SolrMARC
    • Map Solr to MARC fields

Hydra Heads

  1. Hypatia
  2. Libra
  3. Hydrangia


  1. Sept 2011: Hydra no build-in authentication for workflows
  2. Fedora has both Flash & Java client based administration controls
  3. Fedora uses ITQL, SPARQL (others?)
  4. Berlin Benchmarks for triple-store performance comparisons