Versions Compared

Old Version 9

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 10

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add a "Significant Changes" section to top of Upgrade docs to call out major changes in 6.0

...

Legacy Search (based on Lucene) and Browse (based on DBMS) is no longer included in DSpace 6.0 or above
Note

In the notes below [dspace] refers to the install directory for your existing DSpace installation, and [dspace-source] to the source directory for DSpace 5.x. Whenever you see these path references, be sure to replace them with the actual path names on your local system.

Note
title

 

Table of Contents
minLevel2
outlinetrue
stylenone

Release Notes / Significant Changes

DSpace 6.0 features some significant changes which you may wish to be aware of before beginning your upgrade:

...

  • The legacy search engine (based on Apache Lucene) and legacy Browse system (based on database tables) have been removed from DSpace 6.0 or above. Instead, DSpace now only uses Discovery (based on Apache Solr) for all Search/Browse capabilities.

...

...

  • , supporting WebDAV / SOAP / RPC API, has been removed from DSpace 6.0 or above. We recommend using REST or SWORD (v1 or v2) as a replacement.

...

 

...

  • The build.properties configuration file has been replaced by an enhanced local.cfg configuration file. The new local.cfg allows you to easily override any configuration (from dspace.cfg or modules/*.cfg files) by simply copying it into your local.cfg and specifying a new value. It also provides enhanced configuration options as detailed in the Configuration Reference documentation. The old build.properties file is no longer used nor supported.
    • WARNING: As part of adding this new configuration scheme, many of the configuration settings in DSpace (primarily those in modules/*.cfg files) had to be renamed or prepended with the name of the module. This means that 5.x (or below) configurations are no longer guaranteed to be compatible with 6.x. If possible, we recommend starting with fresh configs (see below), and moving all your locally customized settings into the new local.cfg file.

...

Backup your DSpace

Before you start your upgrade, it is strongly recommended that you create a backup of your DSpace instance. Backups are easy to recover from; a botched install/upgrade is very difficult if not impossible to recover from. The DSpace specific things to backup are: configs, source code modifications, database, and assetstore. On your server that runs DSpace, you might additionally consider checking on your cron/scheduled tasks, servlet container, and database.

...