All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
Warning |
---|
This page is under construction. Please, ignore it for now. |
Info |
---|
These instructions are valid for any of the following upgrade paths:
For more information about specific fixes released in each 4.x version, please refer to the appropriate release notes: DSpace Release 4.1 Notes |
Note |
---|
In the notes below |
...
[dspace-source]/dspace/modules/jspui/src/main/webapp/
[dspace-source]/dspace/modules/xmlui/src/main/webapp/
[dspace]/config
[dspace-source]/build.properties
). As this is a minor upgrade, your previous 4.x build.properties file should work fine. However, you may want to double check your settings. Any settings changed in this build.properties
file are automatically copied over to the final dspace.cfg
file during the "Build DSpace" process (in the next step). For more information on the build.properties file, see "The build.properties Configuration Properties File" section of the Configuration Reference documentation.Build DSpace. Run the following commands to compile DSpace:
Code Block |
---|
cd [dspace-source]/dspace/ mvn -U clean package |
You will find the result in [dspace-source]/dspace/target/dspace-[version]-build.dir
. Inside this directory is the compiled binary distribution of DSpace. Before rebuilding DSpace ("package"), the above command will clean out any previously compiled code ("clean") and ensure that your local DSpace JAR files are updated from the remote maven repository.
$CATALINA_HOME/shutdown.sh
script. (Many Unix-based installations will have a startup/shutdown script in the /etc/init.d
or /etc/rc.d
directories.)Update the DSpace installed directory with the new code and libraries. Issue the following commands:
Code Block |
---|
cd [dspace-source]/dspace/target/dspace-[version]-build.dir ant update |
psql --user [dspace-dbms-user] -f [dspace-source]/dspace/etc/postgres/database_schema_4-47.sql [dspace-database]
sqlplus [dspace-dbms-user]/[database password] [dspace-source]/dspace/etc/oracle/database_schema_4-47.sql
NOTE: [dspace-dbms-user] will be the value of db.username
in config/dspace.cfg
. The database password will be the value of db.password
. [dspace-database] will be the part of db.url
following the last slash.
psql --user [dspace-dbms-user] -f [dspace-source]/dspace/etc/postgres/database_schema_4-48.sql [dspace-database]
sqlplus [dspace-dbms-user]/[database password] [dspace-source]/dspace/etc/oracle/database_schema_4-48.sql
NOTE: [dspace-dbms-user] will be the value of db.username
in config/dspace.cfg
. The database password will be the value of db.password
. [dspace-database] will be the part of db.url
following the last slash.
[dspace]/config/modules/oai.cfg
file. They have been reinstated in DSpace 3.1 or above. Please see DS-1461 for more info.[dspace]/config/modules/oai.cfg
file. Please see DS-1479 for more info.Refresh Browse and Search Indexes. Though there are not any database changes, it is a good policy to rebuild your search and browse indexes when upgrading to a new release. To do this, run the following command from your DSpace install directory (as the dspace user):
Code Block |
---|
[dspace]/bin/dspace index-discovery -f |
If you're still using Lucene (you disabled Discovery): If you are using Lucene for search/browse, you will also need to refresh Lucene indexes by running the following command:
Code Block |
---|
[dspace]/bin/dspace index-lucene-init |
Deploy Web Applications. If necessary, copy the web applications files from your [dspace]/webapps
directory to the subdirectory of your servlet container (e.g. Tomcat):
Code Block |
---|
cp -R [dspace]/webapps/* [tomcat]/webapps/ |
See the installation guide for full details.
...
If you're affected by
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Code Block | ||||
---|---|---|---|---|
| ||||
/* NOTE, you'll need to run this code in two stages: in SQL Developer, first run the query below, then cut/paste the results back into a new query, and run that query */ SELECT 'UPDATE metadatavalue SET text_value = ''http://hdl.handle.net/'||handle||''' WHERE metadatavalue.metadata_field_id = '||metadata_field_id FROM metadatavalue JOIN metadatafieldregistry USING(metadata_field_id) JOIN handle ON handle.resource_id = metadatavalue.item_id WHERE metadatafieldregistry.element = 'identifier' AND metadatafieldregistry.qualifier = 'uri' AND handle.resource_type_id = 2 AND to_char(text_value) = 'http://hdl.handle.net/XXXXX' ; |
If you previously upgraded DSpace from 1.8.x to 3.0 and you use Oracle as your DBMS, you may be affected by
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Code Block | ||||
---|---|---|---|---|
| ||||
UPDATE item SET discoverable=1 WHERE discoverable IS NULL; |