I really think we need to improve the upgrade documentation and ant
targets for 1.5.2....
Begin forwarded message:
On Mar 8, 2009, at 12:02 AM, Zico wrote:
On Sun, Mar 8, 2009 at 6:01 AM, Diggory Mark <[email protected]>
wrote:
ZIco,
DSpace is generally upgraded in place, there are important things
that need to happen to your postgres database and search indexes.
I recommend reviewing the details here for the appropriate version
you are using.
http://www.dspace.org/1_5_1Documentation/ch04.html
Thanks Mark for your quick reply. I went through the doc, there..
just one confusion. They didn`t talk about my archived files, that
means, those assetstore.tar.gz , config.tar.gz. Where will i put
those and also when? Before building postgresql or after postgresql?
Yes, this is because the instructions for upgrading have you leave
your data "in place" as configured in your [dspace]/config/
dspace.cfg and run the installation on top of it. Its assumed they
are in
[dspace]/assetstore
[dspace]/bin
[dspace]/config
[dspace]/logs
[dspace]/lib
[dspace]/search
where [dspace] is the location of your running installation of
dspace (by default usually /dspace or C:\dspace)
The documentation doesn't do a great job of talking about resolving
the changes to your dspace.cfg which you may have made. And the
documented example of copying changes from the [dspace-source]/cdspace/
config/dspace.cfg into your [dspace]/config/dspace.cfg is not the best
way to merge or manage your customizations to this file in relation to
the new dspace.cfg reorganization that Tim Donohue did in 1.5.1.
And I do not recommend using the approach outlined in step 5 for
"Updating dspace.cfg". I approach the upgrade process differently in
this case. I actually work before hand to take my own [dspace]/
config/... and copy any modifications I have made there in my
dspace.cfg, inputforms, customized emails and submission workflow
configuration, migrating them into the [dspace-source]/dspace/config
because they are usually smaller changes than migrating all the new
[dspace-source]/dspace/config/.. fiel by hand into [dspace]/config.
Likewise, I prefer to use the newer dspace.cfg because its been
reorganized into sections and when you go to upgrade to the new
maintence release (1.5.2) your going to have to deal with merging the
difference yet again. This makes the documentation instead look like...
Change 1 (remove steps 5-10) because we are not going to copy in this
direction. Instead we will be doing the following:
#
5. Update dspace.cfg in [dspace-source/dspace/dspace.cfg to contain
any customization you've made in [dspace]/config/dspace.cfg Copy
these important properties that youu may have changed in your
original config...
dspace.dir = /dspace
dspace.url = http://localhost:8080/jspui
dspace.hostname = localhost
dspace.name = DSpace at My University
db.name = postgres
db.url = jdbc:postgresql://localhost:5432/dspace
db.username = dspace
db.password = dspace
mail.server=smtp.myu.edu
mail.server.username = myusername
mail.server.password = mypassword
mail.server.port = 25
mail.from.address = [email protected]
feedback.recipient = [email protected]
mail.admin = [email protected]
alert.recipient = email-address-here
assetstore.dir = ${dspace.dir}/assetstore
# Specify extra asset stores like this, counting from 1 upwards:
# assetstore.dir.1 = /second/assetstore
# assetstore.dir.2 = /third/assetstore
# Specify the number of the store to use for new bitstreams with
this property
# The default is 0 (zero) which corresponds to the 'assetstore.dir'
above
# assetstore.incoming = 1
5b.) pay attention to important package name changes when copying
customizations in the authentication stack and search configuration.
plugin.sequence.org.dspace.eperson.AuthenticationMethod changes to
plugin.sequence.org.dspace.authenticate.AuthenticationMethod
and review any changes to your browse or search configuration.
5c.) and review any changes to your browse or search configurations.
(We can go into more detail here about these changes).
8. Merge any changes you have made in input-forms.xml. You'll need
to merge in your changes to both files or hand copy them into place.
I would recommend we start talking about using tools like sdiff or
Eclipse to manage merging the differences in these files...
http://www.gnu.org/software/diffutils/manual/html_mono/diff.html
10. Merge all your changed email files into the new [dspace-source]/
config/emails and adjust the new "registration_notify" email
template if you have boilerplate text you want to include.
13. Update DSpace Update the DSpace installed directory with new
code and libraries. Inside the [dspace-source]/dspace/target/
dspace-1.5-build.dir/ directory run:
cd [dspace-source]/dspace/target/dspace-1.5-build.dir/;
ant init-configs update
This approach allows us to treat the "[dspace-source]/dspace"
directory as the "Configuration" for our dspace instance, this
includes "config", "modules/**" UI customizations, and any addons we
may be maintaining. By placing this dspace project under SCM, we have
an immediate mechanism for users to begin managing and tracking the
changes they make to their configuration and it is a natural stepping
stone in the process they will use for doing more adventurous
customizations to there dspace installation, this means we are not
maintaining two different strategies for users to manage their
configuration.
-Mark
p.s. I hope that in the future we have a better solutions for managing
such configuration files: In 2.0 we need to stop maintaing site/
community/collection specific configuration in [dspace.cfg] and
instead store it in the repository with the community/collection, this
should include:
a.) submission forms
b.) email templates
c.) search/browse UI configuration
d.) controlled vocabularies
e.) news feeds
f.) almost all the properties identified above.
~~~~~~~~~~~~~
Mark R. Diggory
http://purl.org/net/mdiggory/homepage
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
