Skip to content
- Solution Overview (8:23)
- The basic steps to any migration are followed: export data form source platform, map data from source to target model, be able to refine the data as needed, and then ingest to the target platform.
- Islandora’s Solution Components (9:13)
- Where Islandora fits (10:38)
- What are the steps (12:11)
- Create two ContentDM exports (standard XML and custom XML). Create a map for how the data should go from ContentDM custom XML to MODS crosswalk schema. If you need alternate assets for maps, these are now prepared. In Islandora, make a request for the crosswalk and staging of MODS XML on the staging server. You then have a choice of whether you go ahead and run the ingest directly or whether you download the MODS file to perform some data clean-up operations before doing so. Once the ingest has been run, review it. It is possible to perform iterative refinement (the steps can be repeated). Once it is perfected, make the request on your production server and run the actual final migration.
- Who does what? (13:55)
- Demo (15:29)
- There is quite a bit of discussion about what he is going to show before he actually gets around to really demoing anything. The actual demo begins at (22:30)
- Q&A (36:52)
- What time frame do archives usually use for this migration? (36:52)
- Is there a record count limit for a ContentDM collection to ingest into Islandora? (37:47)
- Dublin core does not easily allow for the authorities to be incorporated like MODS does. Do you go about adding authorities to MODS prior to migrating the metadata or do you default to a local authority instead? (38:25)
- How does the migration tool work with the Islandora book batch, which requires that individual MOD files be created for each image file? (40:38)