Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 43 Next »

Version 5.0

DSpace 5.0 is still in the planning stages and will be released sometime in late (likely Nov/Dec) 2014

 

Table of Contents:

 

New features in DSpace 5.0 (WIP)

DSpace 5.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 5.0 that are enabled by default:

Easier Upgrading to 5.x from any previous DSpace version

Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Tim Donohue

 

XMLUI and JSPUI new features

Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Peter Dietz with the support of Ohio State University Libraries and Longsight

JSPUI new features

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Pascal-Nicolas Becker with the support of TU Berlin
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Greek National Documentation Centre/EKT

XMLUI new features

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Kevin Van de Velde and Bert Vanderhallen with the support of @mire (previously available only in JSPUI)
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Peter Dietz with the support of Ohio State University Libraries and Longsight
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Tim Donohue with the support of DuraSpace
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Peter Dietz with the support of Ohio State University Libraries and Longsight

 

New CRUD endpoints for REST web service API

Unable to locate Jira server for this macro. It may be due to Application Link configuration. by the Czech Technical University in Prague

Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Pascal-Nicolas Becker with the support of TU Berlin

UI support for metadata batch import from various bibliographic formats

Unable to locate Jira server for this macro. It may be due to Application Link configuration. Update to Biblio-Transformation-Engine 0.9.3.5 (changelog)

Kindly contributed by the Greek National Documentation Centre/EKT

Solr libraries were upgraded to version 4.10.2 (JSPUI, XMLUI and OAI modules)

Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Roeland Dillen with the support of @mire

  
The following list contains features that are included in the DSpace 5.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.

XMLUI new features

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by @mire
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by @mire
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Peter Dietz with the support of Ohio State University Libraries and Longsight 
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Robin Taylor
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Robin Taylor

DOI Support

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Mohamed Mohideen Abdul Rasheed
Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Terry Brady with the support of Georgetown University
Unable to locate Jira server for this macro. It may be due to Application Link configuration. by Mark H. Wood with the support of IUPUI University Library
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  by Mark H. Wood with the support of IUPUI University Library

Release TODO list

  • Solr index format upgrade from 1.6,1.7,1.8 to 5 currently requires manual, undocumented steps (see below). 2 options:
    1. We automate it
    2. We document it
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. Seems like we have 2 options:
    1. put Tomcat-specific code to JSPUI's web.xml
    2. just document this Tomcat 7-specific warning
      On DevMtg 2014-11-05 we decided to document for RC1 and decide before RC2

 

Solr upgrade (WIP)

Findings

Solr is distributed on Maven Central as a .war file, which includes the Lucene .jars. No Lucene version relevant to DSpace is available from Maven Central.

Solr is a wrapper for Lucene providing concurrency. Lucene can work with index files directly if we don't need concurrent access (i.e. before we start up Solr).

DSpace 1.6 was the first version to use Solr for statistics. In order to upgrade to DSpace 5, we need to upgrade the Solr index format in two steps. The second step is easy, upgrading from DSpace 3 (Solr 3.5) to DSpace 5 means just running the Solr 4.4 optimize command, which can be run even concurrently when the UIs are running. However, Solr 4.4 doesn't understand the legacy index formats used in Solr before 3.5. Therefore, in the first step, we need to use Solr 3.5 or Lucene 3.5 to upgrade from the older index versions to 3.5.

Suggested upgrade

We need to avoid the conflict of having both Solr 3.5 and 4.4 in the DSpace classpath. Therefore I suggest to run the first step before the Solr 4.4 webapp is started as part of DSpace 5.

To do that, we need to:

  1. detect the index version using getCurrentVersion(index_dir)
  2. for any version older than LUCENE_35 go to 3, otherwise go to 7
  3. get the Solr 3.5 war from Maven Central
  4. extract the lucene-core-3.5.0.jar from the Solr 3.5 war
  5. run the IndexUpgrader class of Lucene 3.5 (or optimize())
  6. start up DSpace in order to start up Solr 4
  7. run the IndexUpgrader class of Lucene 4.4

The manual steps would be:

mkdir solr-3.5.0
cd solr-3.5.0
wget "http://search.maven.org/remotecontent?filepath=org/apache/solr/solr/3.5.0/solr-3.5.0.war" -O solr-3.5.0.war
unzip solr-3.5.0.war
cd WEB-INF/lib/
# check index version, see table below:
java -cp lucene-core-3.5.0.jar org.apache.lucene.index.CheckIndex /dspace/solr/statistics/data/index/
java -cp lucene-core-3.5.0.jar org.apache.lucene.index.CheckIndex  /dspace/solr/search/data/index/
# upgrade index version:
java -cp lucene-core-3.5.0.jar org.apache.lucene.index.IndexUpgrader /dspace/solr/statistics/data/index/
java -cp lucene-core-3.5.0.jar org.apache.lucene.index.IndexUpgrader /dspace/solr/search/data/index/
# check index version again, should be "version=3.5 format=FORMAT_3_1 [Lucene 3.1+]"

 

DSpace/Solr/Lucene versions and compatibility

DSpaceSolrLuceneUsed Lucene index versionSupported Lucene index versions
5.04.4.04.44.4 
4.04.4.04.44.4 
3.03.5.03.5

LUCENE_35

LUCENE_20, LUCENE_21, LUCENE_22, LUCENE_23, LUCENE_24, LUCENE_29, LUCENE_30, LUCENE_31, LUCENE_32, LUCENE_33, LUCENE_34, LUCENE_35
1.83.3.03.3??? 
1.71.4.12.9.3 (2.9.3 951790 - 2010-06-06 01:30:55)??? 
1.61.3.02.4-dev (2.4-dev 691741 - 2008-09-03 15:25:16)???  

Luke

https://code.google.com/p/luke/wiki/Compatibility

Java version

Minimum version of JVM required to run Luke 1.0.1 and earlier is 1.5.

Minimum version of JVM required to run Luke 3.x and 4.x is 1.6.

Lucene Java indexes

Luke 1.0.1 should be able to open indexes built using the following versions of Lucene-Java:

  • 3.0.x
  • 2.x (any version)

Starting with version 4.x Luke cannot open indexes created with Lucene 3.0.0 or earlier.

Starting with version 3.1.0 Luke releases will use the same numbering as Lucene releases, to avoid confusion.

Possible JIRA tickets to resolve (automated list)

This is the list of JIRA tickets ("New Features" and Improvements) currently scheduled for 5.0.  There is no guarantee they will all be completed in time for 5.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.

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Changes

The following changes have already been made to the codebase and will be released in 5.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 5.0 release.

New Features in 5.0

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

General Improvements in 5.0

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Bug Fixes in 5.0

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Organizational Details

Release Coordination

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

Release Team Leader

  • Peter Dietz (Longsight)

Release Team Members

  • Peter Dietz (Longsight)
  • Hardy Pottinger (U of Missouri)
  • Ivan Masár
  • Mark H. Wood (Indiana University)
  • Robin Taylor (University of Edinburgh)
  • Pascal-Nicolas Becker (Technische Universität Berlin)

All Release Team membership information is as of November 4, 2014. Please volunteer (by emailing Tim Donohue), if you are interested in joining the team!

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.

DateMilestoneWhat it means
October 06Deadline for feature pull requestsIf you wish to contribute features to DSpace 5.0, you must submit a pull request by this date.
October 08Weekly developers' meeting devoted to review of feature pull requests for 5.0The entire hour's meeting will be used to discuss proposed features submitted by the deadline.
October 15Weekly developers' meeting devoted to review of feature pull requests for 5.0The entire hour's meeting will be used to discuss proposed features submitted by the deadline.
October 31Feature freezeDSpace 5.0 is considered feature-complete on this date.  Only bugfixes will be pulled between this date and final release.
November 6Release Candidate 1 taggedA DSpace 5.0 Release Candidate will be available for wider testing.
November 10-21TestathonIntensive public testing of the 5.0 Release Candidate is invited.  The Release Team will focus on getting problems resolved.
December 1Release Candidate 2 taggedAn updated DSpace 5.0 Release Candidate will be available for wider testing.
Mid DecemberDSpace 5.0 is publicly releasedDSpace 5.0 is released for download and general use.

 

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

 

 

 

 


  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.