Editing User:Ckeene/ep3 upgrade (section)

== First attempt to migrate data ==
# create dns/dhcp record for ep3m.lib.sussex.ac.uk (m for migration)
# create new archive:
## /opt/eprints3
## bin/epadmin create
## follow creation process (db bit works fine this time, but requires a decent password!).
# started to follow http://wiki.eprints.org/w/Migration
# downloaded and extracted toolkit
# run mkconfig.pl sussex
# cd /opt/eprints3/archives/ep3m
# cp -rp cfg cfg.orig
# copy cfg from toolkit to ep3m
# it works. But do we want this. The nice submission process of ep3 has been turned in to the uglyness that is ep2. 
# Though... how can we migrate just our changes, without migrating the ep2 default stuff?
# cd migration/mtoolkit
# ./export3data.pl sussex eprints > eprints.xml
# ./export3data.pl sussex users > users.xml
# ./export3data.pl sussex subjects > subjects.xml
# /opt/eprints3/bin/epadmin erase_data ep3m 
# /opt/eprints3/bin/import_subjects --verbose --force --xml ep3m subjects.xml
# /opt/eprints3/bin/import --verbose --migration ep3m user XML users.xml
# a number of warnings appear: 
#* Can't exec "NOTFOUND": No such file or directory at /opt/eprints3/perl_lib/EPrints/Plugin/Convert/ImageMagick/ThumbnailDocuments.pm line 73.
#* I suspect these should be ok
#* note http://www.eprints.org/tech.php/7265.html
# use ubuntu package manager to install imagemagick
# sudo /usr/sbin/apache2ctl stop
# sudo /usr/sbin/apache2ctl start
# /opt/eprints3/bin/epadmin erase_eprints ep3m
#* this did not resolve the issue (though /usr/bin/convert exists).
# sudo /etc/init.d/epindexer
# generate_views etc

This has produce a system with records from the ep2 imported. I have not yet tested to ensure they have migrated correctly, but progress has been made!

Migrating config: Migrating the config and wording (mkconfig.pl) looks useful for those who have made major changes. However we made a few changes, to wording, to allow LDAP user types, to add wording for bibtex import etc. So much of this has been over taken by EP3, and add to that the fact the migration basically reverts much of the superior ep3 setup back to a EP2 (e.g. the deposit process). At this stage I suspect I will not overwrite the ep3 cfg files with those from the migration tool. Instead customising ep3 as required. The tool is still useful however, as I can use the cfg files it produces (in its own directory away from the actual eprints installation) to cut and paste segments of code as required.