Versions Compared

Old Version 5

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Version 1.8.0

Tip
titleDSpace 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:

Online Documentation is available at: DSDOC18.

Info

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. 

Table of Contents

New features in DSpace 1.8

minLevel2
outlinetrue
stylenone

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 [dspace]/config/modules/directory.
  • Behavior of 'ant update' has changed: The ant update upgrade 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 *.old).
    • In prior versions of DSpace (before 1.8.0), this ant update command 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 update please 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 [dspace]/solr/search/conf/ and [dspace]/solr/statistics/conf/ directories.

New features in DSpace 1.8 

Image Added

DS-982, DS-939 More Curation Tools/Plugins

Provided by MIT & Others.

 

DS-968 Configurable Reviewer Workflow
A project that makes Reviewer Workflow more configurable,orthogonal to Curation Tooling.
To illustrate the power of the framework, two optional workflows are included:

Image Added

DS-602 SWORD Client for DSpace
Enables DSpace to push/submit content to other SWORD enabled repositories

Provided by Robin Taylor of EDINA, University of Edinburgh.

 

DS-1005 SWORDv2 Server Module

Provided by Richard Jones and Stuart Lewis.

Image Added

DS-528 RSS feeds will support richer features, such as iTunes podcast and publishing to iTunesU (see new "webui.feed.podcast.*" settings).

Provided by Peter Dietz.

Image Added

Discovery Enhancements

  • DSCR-22 Discovery back end rewrite to support other back end implementations beside solr for discovery.
  • DS-971 Improved discovery configuration which utilizes spring & a config file that is located in the modules dir.
  • DSCR-25 New Discovery user interface.

    Provided by Kevin Van de Velde of @mire.

Image Added

DS-964 Rewrite of Creative Commons licensing for XMLUI

  • Better integrates the Creative Commons licence selection into the submission process
  • Legacy problem – do we update old license to new or not? Currently MIT runs 'split version' with old licenses looking like old, and new look like new.
    Provided by MIT.

Image Added

DS-749 Reordering of bitstreams.

Provided by Kevin Van de Velde of @mire.

 

DS-638 Enable virus checking during submission.

 

DS-811 Ability to Withdraw/Reinstate/Delete Items in Bulk, via Batch Metadata Editing

Provided by Stuart Lewis.

 

DS-941 One for the techies. Split up dspace.cfg into smaller more easily managed files. For more info see Upgrading From 1.7.x to 1.8.x

New Features are yet to be determined. If you have ideas or code you'd like to see make it into DSpace 1.8.0, please submit it to our Issue Tracker
Info
Note

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
  • 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 Installer Prototypefor more details
    • Perhaps, alongside this, an easier way to "install" plugins/addons (like Curation Tool plugins)??
    in our Issue Tracker.NOTE: This listing is not finalized, and is likely to change. Not all features/improvements/bugs currently scheduled for 1.8.0 are guaranteed to be in that release.

Organizational Details

Release Coordination

Timeline and Proceeding

RELEASE TIMELINE IS NOT FINALIZED! Two Release Timelines have been proposed and are currently being decided upon by the Committers.

...

Note

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:
      . Essentially a "Beta" release would be an very early release of the software, even before all features are finalized. They give developers an opportunity for early feedback from the community or other developers around a new features. They should not be considered stable (though hopefully they are relatively stable). Rather they are previews of upcoming features. Only features that are completed will be released into the Beta Release (i.e. the Beta Release waits for nothing – we release a new Beta even if there's not many new features completed). After and between Beta releases, features may change, up until the "Feature Freeze"
    • "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.
  • Proposed Release Timeline #1 - 9 months (same timeframe as 1.6.0 to 1.7.0)
    • May 13, 2011 : Beta 1
    • June 3, 2011 : Beta 2 (Note: OR11 is June 7-11)
    • July 22, 2011 : Feature Freeze
    • July 29, 2011 : Final Documentation "Due Date"?
    • August 5, 2011 : Release Candidate 1
    • August 8-19, 2011 : Testathon
    • September 2, 2011 : Release Candidate 2
    • September 5-14, 2011 : Final Testing / Bug Fixing
    • September 16, 2011 : Final Release
  • Proposed Release Timeline #2 - 10 months (slightly longer timeframe, but if we moved to 12 months timeframe afterwards, then we'd just do a new release every October, before the holidays get started)
    • June 3, 2011 : Beta 1 (Note: OR11 is June 7-11)
    • July 8, 2011 : Beta 2
    • August 19, 2011 : Feature Freeze
    • August 26, 2011 : Final Documentation "Due Date"?
    • September 2, 2011 : Release Candidate 1
    • September 5-16, 2011 : Testathon
    • September 30, 2011 : Release Candidate 2
    • October 3-12, 2011 : Final Testing / Bug Fixing
    • October 14, 2011 : Final Release

Release Process needs to proceed according to the following Maven release process: Release Procedure