OLD_FEDORA_HOME/server/config/fedora.fcfg
and find the value of object_store_base.
NEW_FEDORA_HOME/server/fedora.fcfg and change
the value of object_store_base the full path
of your old objects directory.
fedora.fcfg
file. Look for the value of
datastream_store_base.
NEW_FEDORA_HOME/server/fedora.fcfg and change
the value of datastream_store_base the
full path of your old datastreams directory.
c:\work\abc must be written as
c:\\work\\abc.
migration.properties) with the
following content, filling in values appropriate to your
environment:
# This is the directory where the analyzer's output files should be sent.
# If it doesn't already exist, it will be automatically created.
# If it already exists, it must be empty (to avoid accidental overwrites)
# To disable the above restriction, uncomment clearOutputDir=true below.
outputDir=c:\\fedora-migration
#clearOutputDir=true
# The Fedora 3.0 home directory.
fedoraHome=c:\\fedora-3.0
# The full path to the JDBC driver Fedora is configured to use.
# NOTE: The analyzer only uses the database to aid in looking up
# the location of FOXML. It will populate the initial paths in
# the database the first time it runs, if the necessary.
jdbcJar=c:\\fedora-3.0\\tomcat\\webapps\\fedora\\WEB-INF\\lib\\postgresql-8.2-506.jdbc3.jar
# Aspects of the original objects to ignore for the purpose of
# classification. This is optional. If unspecified, the generated
# content models will be the MOST SPECIFIC POSSIBLE. If
# specified, this property must consist of a space-delimited
# list of any of the following:
# OrigContentModel
# If specified, objects that have differing values in the original
# contentModel property may be assigned to the same content
# model if they are otherwise similar.
# DatastreamIDs
# If specified, only datastreams bound to disseminators will
# be considered important for classification. Objects that have
# differing sets of UNUSED datastream IDs may be assigned to
# the same content model if they are otherwise similar.
# MIMETypes
# If specified, the MIMETYPE of each candidate datastream
# will be ignored for the purpose of classification. Objects that
# have differing MIME types for the same datastream may be
# assigned to the same content model if they are otherwise
# similar.
# FormatURIs
# This works exactly the same as MIMETypes, but applies to
# the FORMAT_URI of candidate datastreams.
#ignoreAspects=OrigContentModel DatastreamIDs MIMETypes FormatURIs
migration.properties, enter the following:
java -jar analyzer.jar migration.properties
changeme:CModelN. You should
change these to use your own repository's namespace. You may
also want to change the identifier part of the PID
(e.g. myns:Journal).
info:fedora/ in the rdf:about
attribute. For example, change
rdf:about="info:fedora/changeme:CModel1" to
rdf:about="info:fedora/myorg:Journal".changeme:CModel1-BMech1, but
again, you should specify your own (e.g.
myns:Journal-BMech1).
migration.properties, you can minimize typing
by just using that file, and adding the necessary sourceDir
parameter as shown below.
# This is the directory containing the analyzer's output, and where the generator's
# results should be written.
sourceDir=c:\\fedora-migration
# The Fedora 3.0 home directory
fedoraHome=c:\\fedora-3.0
# The full path to the JDBC driver Fedora is configured to use
jdbcJar=c:\\fedora-3.0\\tomcat\\webapps\\fedora\\WEB-INF\\lib\\postgresql-8.2-506.jdbc3.jar
java -jar generator.jar migration.properties
# 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
java -jar transformer.jar migration.properties
C:\fedora-migration)