This is one of the ongoing "fun" parts of running a DSpace-based
repository - ensuring local changes get applied to future versions of
One way DSpace allows for fairly straightforward control of upgrades
is the employment of the <dspace-source>/jsp/local directory, where
any changes that one makes to the jsp's can be retained, provided
major changes weren't made between versions of DSpace.
For things such as input-forms.xml, your local changes should be able
to be easily retained. It is likely that you could just use the same
exact file from version to version, or just add back in your custom
input forms/fields to the new version's file.
A more complex, but very very awesome, way to manage upgrades is by
using a Subversion repository. At GMU, we have all of our DSpace code
stored in a repository with all of our customizations. Subversion
allows us to not only track our local changes, but "roll back" to
previous stable versions if something goes wrong. When a new version
is released, we can download that and "merge" the new code from the
vendor into our code. It's a rather intelligent system that can do
most of this merging automatically, at least with smaller version
changes (1.4.1 to 1.4.2, for example). This really isn't the place to
document running a Subversion repository, but know that it is a very
nice way to manage DSpace code.
I've documented using Subversion for our local installation, but
should eventually adapt those instructions for a larger audience.
It's one of those things where there was so much trial-and-error
involved in learning the process that it's difficult to go back and
remember exactly what I did to overcome mistakes. :)
I hope this helps in some way.
Digital Repository Services Librarian
George Mason University
On Oct 26, 2007, at 11:35 AM, Henry, Roberta wrote:
> Hello all,
> We would like to customize our Dspace to include a location field
> in the upload form by editing the XML. If we do, will our
> customization be wiped out by future updates. A local library has
> had this problem, so we thought we'd ask.
> Robin Henry
> Library Technical Services Specialist
> Sam White Library
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> DSpace-tech mailing list