Page History

...

1. Initial simplification of Installation/Upgrade processes (see DS-802)
2. Refactoring & modularization, which may include taking initial steps detailed in the following proposals (Note: the implementation details of these proposals are obviously up for discussion):
   1. Begin to Restructure Trunk Projects - with a goal of ensuring our various applications do not all need to be installed out of the box
   2. Begin Refactoring the DSpace Domain Model - with a goal of ensuring we begin to separate our data model from underlying data access services (will be necessary to help support move towards Fedora-Inside, while also potentially enabling use to expand support for additional databases, etc)
   3. Move towards more widespread usage of DSpace 2.0 Services (some examples in this proposal: Replace DSpace ConfigurationManager and PluginManager)
3. Begin to Improve "Interoperability" / Integration points
   1. Release a beta version of REST API
   2. Potentially allow for AIP Transmission via SWORD?
4. Also release features which just missed 1.7, but seem of high interest. Especially the following (this is not an exhaustive list!):
   1. Additional Curation Tasks?
   2. Context-Guided Ingest?
   3. SWORD Client for DSpace? - of high interest if we wanted to enable AIP Transmission via SWORD
   4. Other features listed on DSpace Release 1.8.0 Notes

DSpace 1.9.0 (TBD - Oct 2012?)

...

1. Additional Refactoring & Modularization (especially in preparation for "DSpace with Fedora Inside"). This may include the following proposals (Note: the implementation details of these proposals are obviously up for discussion):
   1. Any refactoring that didn't happen in time for 1.8.0
   2. Refactor Packagers to support Chain of Command (if it doesn't make it in 1.8.0)
   3. Metadata For All - begin to enable metadata on all DSpace Objects
2. Improvements / simplification of DSpace Configuration (perhaps even moving some configs to a DB). Minimally, this needs to simplify the 'dspace.cfg'.
3. Change which Interfaces come "out-of-the-box", and allow others to be optionally installed at a later time (The following is only meant as an example.)
   1. Default install may only include: XMLUI, SOLR, possibly SWORD?
   2. Change LNI, OAI-PMH, REST and JSPUI to "optional".
      1. Potentially 'deprecate' support for LNI (or locate external, third-party support for it). Discuss whether any other Interfaces should be similarly deprecated (based on community-wide usage, etc).
   3. Encourage the community to develop / share / support their own third-party UIs (which potentially could communicate with DSpace via REST API, or via a refactored DSpace Domain Model API).
4. Asynchronous Job Scheduler? (would replace the need to schedule jobs via 'cron' or similar)
5. Any Features/Changes that just miss making it into 1.8.0

...