Version 4.0

Table of Contents:

Wish List for DSpace 4.0 (tentative)

Please feel free to list features / contributions you plan to develop for 4.0.  You can also add a JIRA ticket and mark it for "4.0" which will put it on the automated list below (see "Possible JIRA tickets to resolve")

New features in DSpace 4.0

DRAFT - DRAFT - DRAFT - amend the table below (taken from DSpace 3.0 release notes) - DRAFT - DRAFT - DRAFT

DSpace 4.0 ships with a number of new features. Certain features are automatically enabled by default while others require deliberate activation.  The following non-exhaustive list contains the major new features in 3.0 that are enabled by default:
	Batch import for Bibliographic formats Support for Endnote, BibTex, RIS, TSV, CSV Enhanced batch import routines Kindly contributed by the Greek National Documentation Centre/EKT
	Improvements to Authentication by Password now stores salted hashes old passwords will continue to work and will be automatically converted to salted hashes on next user login Kindly contributed by Mark H. Wood with the support of IUPUI University Library
	SWORDv2 module update (see Git Repo: https://github.com/nye-duo/DSpace/tree/swordv2contrib), which provides the following improvements:  some general bug fixes including: bitstream url construction, config options, context management and connection pool, ORIGINAL bundle problem ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. ) proper METSDSpaceSIP support in both deposit and update proper authentication for accessing actionable bitstreams (i.e. those that can be replaced via sword), tightened security options around mediated actions, and add extra security to the access of descriptive documents (deposit receipts, statements) more configuration options: bundles to expose in Statements, DepositMO extensions (for individual files), and many more some general refactoring addition of 404 responses where necessary better support for add/replace of metadata, and how metadata updates are handled on archived items update to latest version of Java Server library new bitstream formats in the bitstream registry Kindly contributed by Richard Jones with the support of ...
	DOI Support Unable to locate Jira server for this macro. It may be due to Application Link configuration. Kindly contributed by Pascal-Nicolas Becker & Mark Wood with the support of TU Berlin
The following list contains all features that are included in the DSpace 3.0 release, but need to be enabled manually. Review the documentation for these features carefully, especially if you are upgrading from an older version of DSpace.
	Discovery: Search & Browse Discovery is now enabled by default in both XMLUI and JSPUI. The Lucene & DB search & browse backend is still supported, but is deprecated and might be removed in a future release. Discovery enhancements for XMLUI: Spell checking Kindly contributed by @mire with the support of (??? the World Bank) Discovery enhancements in JSPUI (example) Kindly contributed by CILEA
	A new Bootstrap-based default look and feel for JSPUI Kindly contributed by CILEA
	Advanced Embargo Time based restrictions on both bitstreams and metadata Advanced mode for additional user group restrictions XMLUI only Kindly contributed by @mire with the support of the University of Michigan Libraries
	Mobile Theme for XMLUI matures from beta Documentation Kindly contributed by Elias Tzoc and James Russell with the support of Miami University
	Improvements to LDAP Authentication New option to map LDAP group membership to internal DSpace groups  Kindly contributed by Samuel Ottenhoff

Conceptual Ideas / Proposals

• REST API: We would like to have a stable, tested, read/write, documented, standards based REST API available. Already a working group has been formed to review the existing API's, and to evaluate the existing API's, and to research development of a new API. The API will either be included with the out-of-the-box DSpace, or it will be released a module to be enabled separately. The API working group will host a discussion panel at OR13 during the DSUG track. An API available will enable further re-use of repository data. Existing use-cases of the project range from building JS widgets to spit out a researcher's publications in repository to building a frontend web application.
  
  

Possible JIRA tickets to resolve (automated list)

This is the list of JIRA tickets ("New Features" and Improvements) currently scheduled for 4.0.  There is no guarantee they will all be completed in time for 4.0 release, and tickets may be dropped/added to the list at any time. But, if you'd like to volunteer to help with one, please let us know by attaching a comment to the ticket in question.

Changes

The following changes have already been made to the codebase and will be released in 4.0. Please note that the below listing is dynamically generated, so it will be changing as we continue to add new features, improvements and bug fixes to the 4.0 release.

New Features in 4.0

General Improvements in 4.0

Bug Fixes in 4.0

Organizational Details

Release Coordination

Instead of a single "Release Coordinator", the DSpace 4.0 release will be managed by a "Release Team".

Release Team Leader

• Mark H. Wood

Release Team Members

• Hardy Pottinger
• Mark H. Wood
• Andrea Bollini (4Science)

All Release Team membership information is tentative, as of July 8, 2013. Please feel free to volunteer if you are interested!

Timeline and Processing

Your contributions are welcome now! Code and documentation need not be finished, so long as it is working and we can all see what it is for. Time is set aside for fixing, polishing, and integration. We have some general Code Contribution Guidelines available, but you are also welcome to ask questions on the dspace-devel mailing list.

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