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

From Libopedia
Jump to navigation Jump to search
m
 
(138 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
<center>
 +
'''[[SUNScholar/Upgrading|Back to Upgrading]]'''
 +
</center>
 +
 +
{{DISCLAIMER}}
 +
 
==Introduction==
 
==Introduction==
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.
+
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.
 
 
Our next upgrade will be from DSpace version 1.7.2 to 1.8.2 in Dec 2012.
 
==Procedure==
 
Using an Ubuntu desktop the program "meld" is installed. "meld" allows you to compare two folders for differences.
 
  
So 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 appropiate.
+
==Instructions==
 +
===Step 1 - [[SUNScholar/Upgrading/DSpace/Release Notes|Read the release notes]]===
 +
===Step 2 - [[SUNScholar/Upgrading/DSpace/General Notes|View the general guidelines]]===
 +
[[Category:System Administration]]

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