Page History

...

DSpace & Fedora Integration Questions

...

What are the plans for integrating the DSpace application with the Fedora repository platform?

For some time there has been interest expressed among DuraSpace communities in having Fedora act as either a robust storage layer or archive layer behind the DSpace application while maintaining the out-of-the-box DSpace experience including workflows, and look and feel. There is work underway than may eventually enable the option to run the DSpace application on top of a Fedora repository. To achieve this requires a series of developments:

1. A way to extract the items from DSpace's current internal store, along with all of their relationships (communities, collections, and Epeople).
   • Related Project(s): DuraSpace is currently developing this as a general,
   roundtripping
   • backup/restore AIP capability for DSpace.
2. An implementation of the DSpace data model using the Fedora repository.
   • Related Project(s): There is prior art (which would need to be updated) for this from GSoC 2008 and GSoC 2009. There is also a current GSoC 2010 project to backport DSpace 2.x Storage Services to 1.x – this work may enable the ability to use prior Fedora integrations in the DSpace 1.x platform.
3. A conversion, crosswalking, or import utility for the above two items. There
   • Related Project(s): At this time, there is neither a schedule nor a
   committment
   • commitment for this
   yet
   • work.
4. Designing an integration of the DSpace business logic, User authentication and authorization with Fedora. This is no schedule or committment for this yet
   • Related Project(s): At this time, there is neither a schedule nor a commitment for this work.
5. Porting the DSpace user, administrative, and web services interface applications to run against the resulting environment. There is no schedule or committment for this yet
   • Related Project(s): At this time, there is neither a schedule nor a commitment for this work.

Not all of these steps need to be complete for some models of operation involving running DSpace and Fedora as distinct, cooperating applications.

What is the proposed end result of this integration?

The end result would be a family of packages that you would install together for the full DSpace experience. One of these packages would offer a Fedora-based storage layer. So, when you install DSpace, there would be an option to use Fedora as its storage layer.

Essentially, DSpace will still retain very similar interfaces and workflows, but it will now have "Fedora Inside".

Will

...

the end result still look like DSpace and be called DSpace?

Yes. We are committed to maintaining the DSpace out-of-the-box experience. This The end result of this integration may be an evolved version of DSpace (with new or slightly changed features), but it will still provide the same out-of-the-box institutional repository software.

To put it another way, the goals of DSpace software will not change. DSpace will continue to provide the same type of experiences you've come to expect. However, we hope the end result will provide even more useful features and will help to evolve the DSpace platform.

What are the perceived benefits? Why do this integration?

...

• Less redundancy between DSpace & Fedora code and development.
• Ability to combine development work/projects – a larger pool of developers working on common technologies.
• DSpace will also be able to take advantage of features offered by Fedora (which are not currently available in DSpace). An example is the file Some examples may include:
  • File versioning feature of Fedora, which DSpace could utilize to support versioning of DSpace Objects.
  • More flexible architecture, which may allow
  for item versioning.

Has this decision already been finalized? Or is this just a recommendation?

• • DSpace to eventually support hierarchies other than "Community -> Collection -> Item"
  • Flexible relationships model, which may allow for better defined relationships between DSpace Objects (e.g. linking together all articles within a Journal Issue, or all Issues within a Journal)

How is this work being supported?

DuraSpace cannot support this work on its own. That's why we are DuraSpace is making a strategic recommendation that the DSpace and Fedora communities work towards tighter integration between the software platforms.

DuraSpace is also backing up this recommendation committed to helping with strategic development work (DSpace AIP Export work).Needs rewording/massaging – Timwork that helps to further this initiative. For example, we feel our ongoing AIP Backup/Restore work will be beneficial in upgrading existing DSpace instances to an eventual DSpace with "Fedora Inside". However, we do not have the technical staff to do this work alone.

Who will do this work? When will it be complete?

We currently don't have an exact timeframe for this work to be complete. As with any open source development initiative, it needs ongoing commitment and volunteers from the community.

As stated, DuraSpace does not have the technical staff to do this work alone, nor would we want to. As with any open source development initiative, and is the commitment and support of the broader community will build a better 'end product', than if one institution were to implement it on their own. We are currently looking for DSpace & and Fedora community volunteers to help make this initiative happen.

How can I help? How do I volunteer?

Once this work is complete, how hard will the upgrade be for current DSpace users? Will I have to do all the work myself / how much expertise will I need to perform this upgrade?

...