...
A Sample Migration From 5→6
Step 1: Export from 5.1.
...
x
Make sure that your Fedora 5 instance is running. Also be sure that you are using the latest version of the import export tool. Then run the following command:
| Code Block | ||
|---|---|---|
| ||
java -jar fcrepo-import-export-1.0.0-<latest-version>.jar \ --dir my-fcrepo-5.1.1-export \ --user fedoraAdmin:fedoraAdmin \ --mode export \ --repositoryRoot http://localhost:8080/rest \ --resource http://localhost:8080/rest \ --binaries \ --versions |
...
| Code Block | ||
|---|---|---|
| ||
java -jar fcrepo-upgrade-utils-<latest-version>.jar \ --input-dir my-fcrepo-5.1.1-export \ --output-dir my-fcrepo-6-home \ --source-version 5+ \ --target-version 6+ \ --base-uri http://localhost:8080/rest |
NOTE: The "base-uri" option is the URI of the Fedora 5 repository we are migrating from, not the Fedora 6 repository we are migrating to.
Step 3: Fire up Fedora 6
| Code Block | ||
|---|---|---|
| ||
java -Dfcrepo.home=my-fcrepo-6-home -jar fcrepo-webapp-<latest fedora 6 version>-jetty-console.jar --headless |
...
You can force Fedora to reindex your content on startup by starting it with the following argument: -Dfcrepo.rebuild.on.start=true
Why are the properties on my migrated binary descriptions showing up under "Other Resources"?
This can occur in a Fedora 5 to 6 migration if the "base-uri" option provided to the fcrepo-upgrade-utils does not match the URI of the Fedora 5 instance from which the data was migrated. Generally, the "--base-uri" option should match the "--resource" option from the export command. The "base-uri" is used to identify Fedora resource URIs in the export in order to convert them to the correct format in Fedora 6, it is not the URI of the server to eventually migrate to. If the base-uri does not match a subject URI in the export, then the URI will be left untouched and Fedora 6 will interpret it as an external URI rather than a Fedora managed URI.