Page History

Introduction

@mire continues its own initiatives To continue evolving towards DSpace 2.0 goals this year by providing , @mire will continue to provide further refactorings of the DSpace legacy codebase. These refactoring efforts are focused now on resurrecting and completing the the DAO prototype work of past Hewlett Packard developer, James Rutherford. This work includes efforts to separate the legacy DSpace codebase into a separate Domain Model and Data Access Services. Once integrated into DSpace 1.8, new DSpace Services for legacy DSpace objects will provide a common API for both the DSpace Application tier and external addon modules.

...

Extraction of the DSpace Data Model as an API from the DSpace core libraries provides a contract for application developers to rely on when developing enduser applications for DSpace. Additional API on core DSpace busi- ness and data access services (workflow and data access) will assure that applications can rely on these serv- ices contractually while the underlying implementations are improved and alternate implementations begin to emerge. Past prototyping in the DSpace 2.0 and GSoC projects have verified that once properly restructured integration with alternative storage implementations including options such as Fedora, JCR Repositories, Dura- Cloud and Semantic Storage systems such as Tupelo will be greatly eased.  An initial Prototype of this API now resides in the dspace-model project and we will be providing JIRA tasks and patches to trunk that will reflect what are some relatively minor changes to the org.dspace.content and core packages to support it.

Preparing DSpace for Integration with Fedora

...

By continuing this path of development, we continue to show that the original funded DSpace 2.0 Initiative con- tinues to supply solutions and recommendations on the roadmap towards DSpace 2.0. With the Services frame- work and the first significant refactoring of DSpace core classes in place, the DSpace developer community can now begin to schedule changes that should happen as stepping stones to prepare the community for the release of a DSpace version 2.0.

Welcoming Collaboration

@mire realizes that such work on core DSpace libraries requires consensus and coordination into the community, as such we welcome feedback, critique and community participation on the initiative.