Moving VITAL foxml1.0 and datastreams to fedora3.0’s foxml1.1

We referred to official Fedora migration documentation for this task, below is just a blow by blow of what we actually did. To get the official doco go to the Fedora Site

  • We moved data store from VITAL (ie /opt/vtls/vital/store to the server new server running fedora3.0)

*Note: Make sure that this store directory containing all of the objects and data streams to be transformed is owned by the user that will be running the transform commands on the fedora3.0 server.

If not you will get a null pointer exception/unexpected error when running the transform command below.

  • We amended fedora.fcfg file to point to the new data that we just copied over, changed object_store_base and datastreams_store_base values.
  • Downloaded official migration software from Fedora Migration
  • Made migration.properties file as per migration doco at Fedora Site
  • Ran analyzer jar file:
java -jar analyzer.jar migration.properties

Output:

user@localhost:/opt/fedora/server/config$ ls /home/user/fedora-migration/

bdefs.txt cmodel-11.xml cmodel-14.members.txt cmodel-16.xml

cmodel-3.members.txt cmodel-5.xml cmodel-8.members.txt bmechs.txt

cmodel-12.members.txt cmodel-14.xml cmodel-1.members.txt cmodel-3.xml

cmodel-6.members.txt cmodel-8.xml cmodel-10.members.txt cmodel-12.xml

cmodel-15.members.txt cmodel-1.xml cmodel-4.members.txt cmodel-6.xml

cmodel-9.members.txt cmodel-10.xml cmodel-13.members.txt cmodel-15.xml

cmodel-2.members.txt cmodel-4.xml cmodel-7.members.txt cmodel-9.xml

cmodel-11.members.txt cmodel-13.xml cmodel-16.members.txt cmodel-2.xml

cmodel-5.members.txt cmodel-7.xml nocmodel.txt

  • Opened each cmodel xml file and change value of the PID attribute to match our institutions PID eg change changeme:CModelN to uon:CModelN

*Note we think that if the <param name=”pidNamespace” value=”changeme”> in the fedora.fcfg file is “changeme” then the analyser is probably using that namespace to create the models. Try changing this value to the PID of your institution before running the analyser if you don’t want to have to edit these file manually, this has not been confirmed just a suspicion.

  • Added the following to migration.properties file:
# This is the directory containing the analyzer's output, and where the generator's
# results should be written.
sourceDir=/home/user/fedora-migration
  • Ran generator jar file:
java -jar generator.jar migration.properties

OUTPUT:
INFO: Writing stylesheet for objects with content model uon:CModel13
INFO: Writing stylesheet for objects with content model uon:CModel2
INFO: Writing stylesheet for objects with content model uon:CModel7
INFO: Writing stylesheet for objects with content model uon:CModel11
INFO: Writing stylesheet for objects with content model uon:CModel4
INFO: Writing stylesheet for objects with content model uon:CModel10
INFO: Writing stylesheet for objects with content model uon:CModel8
INFO: Writing stylesheet for objects with content model uon:CModel3
INFO: Writing stylesheet for objects with content model uon:CModel16
INFO: Writing stylesheet for objects with content model uon:CModel15
INFO: Writing stylesheet for objects with content model uon:CModel1
INFO: Writing stylesheet for objects with content model uon:CModel12
INFO: Writing stylesheet for objects with content model uon:CModel6
INFO: Writing stylesheet for objects with content model uon:CModel5
INFO: Writing stylesheet for objects with content model uon:CModel9
INFO: Writing stylesheet for objects with content model uon:CModel14
INFO: Wrote stylesheet for nocmodel.txt, nocmodel.xslt
INFO: Wrote stylesheet for bmechs.txt, bmechs.xslt
INFO: Wrote stylesheet for bdefs.txt, bdefs.xslt
INFO: Generated stylesheets and bMechs for 16 data object content models.

  • Updated the migration.properties file.

Added the following:

# Whether to run the transformer in "dry run" mode or not.
# In dry run mode, transformation will be tested but no changes will be written
dryRun=true
  • Ran the transform.jar
java -jar transformer.jar migration.properties
  • Changed the dryRun to false and re-ran the transformer.jar
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s