This page is outdated / obsolete!

This page details an ideal from Open Repositories 2010 which was loosely called "DSpace with Fedora inside".  Since that point, this concept never gained leverage or momentum in the DSpace or Fedora communities.  It is now considered outdated/obsolete based on the latest technology roadmaps for each platform. At this time, there are no immediate plans to merge DSpace and Fedora or rebuild DSpace as a Fedora-based application.  For more information on the direction of both DSpace and Fedora, please consult their respective technology roadmaps.

Roadmap

As DuraSpace moves forward with our roadmap plans for 2011-2012, we are looking for participants to collaborate on determining requirements, developing code and/or testing prototypes for a variety of use cases starting in the following areas:

  1. Propose a Fedora data model for DSpace data
    1. Related Project(s): There is prior art (which would need to be updated) for this from Google Summer of Code 2008 Fedora Integration and Google Summer of Code 2009 Fedora Integration. There was also a GSoC 2010 project to backport DSpace 2.x Storage Services to 1.x GSOC10 - Backport of DSpace 2 Storage Services API for DSpace 1.x. The GSoC 2010 project may enable the ability to use prior Fedora integrations in the DSpace 1.x platform.
  2. A conversion, crosswalking, or import utility to get DSpace data into the selected Fedora data model.
    1. Related Project(s): DuraSpace has developed a general  AIP Backup and Restore capability for DSpace 1.7. This feature provides a way to extract the items from DSpace's current internal store, along with all of their relationships (communities, collections, and people).
    2. Need determine if the current 1.7 AIP Backup & restore feature would need reworking in order to more easily crosswalk/map the data into the eventual Fedora data model.
  3. Designing an integration of the DSpace business logic, user authentication and authorization with Fedora.
  4. Porting the DSpace user, administrative, and web services interface applications to run against the resulting environment.
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.