Difference between revisions of "SUNScholar/Upgrading/Repository Software"

From Libopedia
Jump to navigation Jump to search
m
 
(111 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Introduction==
+
<center>
{{WARNING}}
+
'''[[SUNScholar/Upgrading|Back to Upgrading]]'''
 +
</center>
  
As a rule at Stellenbosch University library we only upgrade to DSpace during the Dec/Jan long holiday. We also run one version behind the latest version because we do not have expert Java and Web 2.0 skills in-house. So we stay just behind the bleeding edge.
+
{{DISCLAIMER}}
  
Our next upgrade will be from DSpace version 1.7.2 to 1.8.2 in Dec 2012.
+
==Introduction==
==Procedure==
+
Stellenbosch University Library tries to stay one major version behind the current DSpace version because we do not have expert java programmers to fix bugs. So we stay super stable by staying one version behind the latest version. We let those with expert programming resources fix bugs in the latest version while we enjoy the stable benefits of the previous version.
[http://www.ubuntu.sun.ac.za/wiki/index.php/Main_Page Using an Ubuntu desktop], the program "[http://meldmerge.org meld]" is installed. "meld" allows you to compare two folders for differences.
 
 
 
To do a comparison, the working version is copied to my desktop and the new version is extracted to my desktop as well.
 
 
 
Using '''meld''' I investigate all the differences and update the new version with new settings as appropriate.
 
 
 
When I am satisfied that the new version has most of my customisation from the old version, then I test on my development server.
 
 
 
I do more debugging on the development server as needed and then finally activate it on the production server and test.
 
 
 
On the production server we test for a couple of days. We let users know in advance that the production server will be offline for this period.
 
 
 
'''Please note:''' Radical changes between versions of DSpace make upgrades a very time consuming and risky process. Prepare yourself well in advance on a development server.
 
==Backup Databases==
 
Type the following to backup the databases. <font color="red">'''This must done before attempting any upgrades.'''</font>
 
==Database upgrades==
 
This should be the 1st step of the upgrade process.
 
 
 
Each version of DSpace has changes to the database. To do database upgrades use the '''psql''' command. An example follows:
 
psql -U dspace -f /home/dspace/dspace-1.8.2-src-release/dspace/etc/postgres/database_schema_17-18.sql dspace
 
Before doing database updates, check that you have made a backup of the database. ''[http://www.pgadmin.org pgadmin]'' is a good program to use for this.
 
  
==References==
+
==Instructions==
*https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.7.x+to+1.8.x
+
===Step 1 - [[SUNScholar/Upgrading/DSpace/Release Notes|Read the release notes]]===
*https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.6.x+to+1.7.x
+
===Step 2 - [[SUNScholar/Upgrading/DSpace/General Notes|View the general guidelines]]===
*https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.5.x+to+1.6.x
+
[[Category:System Administration]]
 
 
'''[[SUNScholar/Upgrading|Back to Upgrading]]'''
 

Latest revision as of 11:13, 28 May 2016

Back to Upgrading

WE CANNOT ACCEPT RESPONSIBILITY FOR ANY DATA LOSS OR CORRUPTION
BEFORE PROCEEDING, DO EXTENSIVE TESTING ON SPARE INFRASTRUCTURE
*** YOU PROCEED AT YOUR OWN RISK ***

Introduction

Stellenbosch University Library tries to stay one major version behind the current DSpace version because we do not have expert java programmers to fix bugs. So we stay super stable by staying one version behind the latest version. We let those with expert programming resources fix bugs in the latest version while we enjoy the stable benefits of the previous version.

Instructions

Step 1 - Read the release notes

Step 2 - View the general guidelines