Versions Compared

Old Version 3

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version 4

changes.mady.by.user Chris Beer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Using RDF responses that contain full profile information for the object and datastreams to minimize HTTP round-trips
  • Allowing (and exposing) arbitrary properties on objects, and pushing that through the stack, in order to let Hydra heads "tag" objects with arbitrary, non-datastream information

Running a Hydra head over fcrepo4

Our Sufia-based hydra head is maintained at https://github.com/futures/fcrepo4-demo-hydra-app. It uses a forked version of Rubydora:

gem 'rubydora', :git => 'http://github.com/projecthydra/rubydora.git', :branch => 'fcrepo4'

and ActiveFedora >= 6.4.

All of the Fedora 4-specific changes are constrained to the Rubydora fork. Everything else should just work. Some unit and integration tests that expect Fedora 3-like behaviors (DC, RELS-EXT, etc) may fail, but most end-user facing features should work unchanged.

Fedora 4 does not have some Fedora 3 concepts, like external and redirect datastreams. The sufia-based head does not use these features, but we expect they could be mimicked at either the Rubydora level, or created as an optional service at the Fedora level.