DSpace 1.8.0 was officially released to the public on November 4, 2011.
DSpace 1.8.0 can be downloaded immediately at either of the following locations:
- SourceForge: https://sourceforge.net/projects/dspace/files/
- SVN: http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.8.0/
In addition, you are welcome to try out DSpace 1.8.0 on http://demo.dspace.org/ and continue to provide any feedback you may have.
DSpace 1.8.0 is a scheduled, "time-based" release. In order to decrease delays in releasing new features and increase transparency, the DSpace Developers have scheduled 1.8.0 in advance and are basing its features on what we are able to complete within that timeframe.
Scheduling releases benefits us all as it should decrease the delays in releasing new features, and increase the transparency of the development process. The DSpace Developers feel that these benefits will far outweigh the cost of potentially having fewer major features in a given DSpace release. We hope the DSpace Community will also realize the immediate benefits, which should allow them to receive new features more quickly, rather than potentially waiting years for the next major release of the software. The DSpace Developers hope to continue this trend of "time based" releases with all future releases.
Changes to the DSpace 1.8 Upgrade / Configuration Process
In DSpace 1.8.0, there have been a few significant changes to how you upgrade and configure DSpace. Notably:
The dspace.cfg has been "split up": Many "module" configurations have now been moved out of the 'dspace.cfg' and into separate configuration files in the
Authentication Configurations are now in
Bulk Metadata Editing Configurations are now in the
Discovery Configurations are now in the
OAI-PMH / OAI-ORE Configurations are now in the
Solr Statistics Configurations are now in the
- All other DSpace configurations are still in the
- Behavior of 'ant update' has changed: The
ant updateupgrade command now defaults to replacing any existing configuration files (though the existing configuration files will first be backed up to a file with the suffix
- In prior versions of DSpace (before 1.8.0), this
ant updatecommand would leave existing configuration files intact (and you would have to manually merge in new configuration settings, which would be in a file with the suffix
*.new). If you prefer this previous behavior, you can still achieve the same result by running:
ant -Doverwrite=false update.
WARNING: If you choose to run
ant -Doverwrite=false updateplease be aware that this will not auto-upgrade any of your configuration files. This means you must closely watch the output of this command, and ensure you manually upgrade all configuration files in the
[dspace]/config/directory as well as all Solr configurations/schemas in the
- In prior versions of DSpace (before 1.8.0), this
New features in DSpace 1.8
DS-968 Configurable Reviewer Workflow
DS-749 Reordering of bitstreams.
DS-811 Ability to Withdraw/Reinstate/Delete Items in Bulk, via Batch Metadata Editing
For a list of all features/improvement/bugs released in 1.8.0, see the 1.8.0 Version History.
Released as Addons
These addons will be "compatible with 1.8.0", but will require a separate, optional installation.
- DS-876 Replication Task Suite.
- REST API (experimental). Unfortunately didn't receive enough attention for it to be formally released as part of 1.8. However, this is a fully functioning module, although not yet officially supported by the DSpace Committer group. Please see the wiki page for more details and instructions on how to incorporate the module into your local installation.
Postponed for a Future Release
- Core Service and Service Manager Refactorings
- Asynchronous Release Process Release various modules/addons separate from base install (Mark Diggory/@mire & others)
- Refactoring ConfigurationManager and PluginManager to use ServiceManager (@mire with others welcome)
- Context Guided Ingest (Richard Rodgers/MIT) – define an interface, where any submission code can write "attributes" and can retrieve those again later on. Can add any new attributes/values that you want for your submission code. Could be serialized to XML (using input-forms.xml) OR have an implementation of that service that stores in DB (recommended). JPA2?
- would allow for type-based submission processes (e.g. Theses/Dissertations could have different submission steps than articles/papers).
- based on the Item type based submission patch picked up by Robin Taylor (initially a GSoC project)
- DSpace "Easy" Installer (Tim Donohue)? See DS-802 and InstallerPrototype for more details
- Perhaps, alongside this, an easier way to "install" plugins/addons (like Curation Tool plugins)??
Timeline and Proceeding
It has been decided that DSpace 1.8.0 will be released in Oct 2011. The exact date is still being worked out. What follows is a tentative release timeline - it has changed slightly from its original state, but the final release will still come out sometime in Oct 2011.
- Very Tentative Release Timeline (This should not be considered final)
- August 19, 2011 : Feature Freeze Date
- September 2, 2011 : Final Documentation "Due Date"?
- September 9, 2011 : Release Candidate 1 release
- September 12-23, 2011 : Testathon
- October 19, 2011 : Release Candidate 2 release
- October 20-27, 2011 : Final Testing / Bug Fixing
- October 28, 2011 : 1.8.0 Final Release
- A few definitions:
- "Feature Freeze" - After this date, the feature listing cannot change. All new features must be completed by this date. After this date, the system is being stabilized in preparation for the first "Release Candidate"
- "Release Candidate" releases - These are initial releases after all features have been finalized. Features may not change, but bug fixes can be made. They are meant for very broad testing (e.g. Testathon), in order to find & fix any last bugs before the Final Release.
Release Process needs to proceed according to the following Maven release process: Release Procedure