The Avalon 6 Migration Report page shows the status of a currently running migration. It allows for administrators to easily view detailed information on the state of currently migrating Avalon objects from within the application.
Access to the Migration Report is limited to users in the Administrators group.
Going to the URL avaloninstance.com/admin/migration_report/ will take you to the Migration Report.
The live update button on the bottom tells the page to refresh the report every five seconds.
You'll notice as you first start importing that all of your media objects will jump to either "Failed" or "Waiting". Media objects in "Waiting" are waiting for the second pass of migration which will connect them with their masterfiles and derivatives. During the second pass these object will move to either "Failed" or "Completed".
You can drill down to an Avalon class type and see its items and basic migration information. This is a good place to check for errors during migration.
Clicking on an item brings up a detailed view of any datastreams that are attached to the item.
You can view the datastreams (including any images) below the header under Fedora 3 or Fedora 4. Viewing the datastreams from Fedora 3 is a live query that requires the Fedora 3 instance to be running and responding to requests. Once the Fedora 3 instance from your previous Avalon installation is stopped, this information will no longer be available from the Migration Report.
Not everything created in Fedora 4 for a migrated MediaObject will show in this report, such as access control and list_source objects (ordering via proxies).
Some migrated items won't have Fedora datastreams attached to them; these items that are migrated straight from the database and have limited details pages. After you run the avalon:migrate:db rake task, the db items will also show up in your migration report.