You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Excellent tutorial! Your explanation of how migrations work is very clear and complete. It not only documents how Migrate works for Islandora repo objects, but also how the nodes, files, and media make up the Islandora data model.
Running the following imported the nodes, files, and media:
But, no thumbnails were generated (in the Media tab only the Original File is listed), and it appears that the images have not been pushed into Fedora (I'm getting 404s for file UUIDs). All of my Islandora-provided Contexts are enabled as far as I can tell.
Also, when I tried to run the migration group via the GUI by executing the Media migration, it failed. I assumed that since the media migration config contains
I probably should have mentioned that my CLAW modules are all in a state suitable for testing Islandora-Devops/migrate_7x_claw#10, in case that might account for why thumbnails and the lack of pushing into Fedora. I can reset all those to master if you want and try again.
@mjordan I find that the linkages between Drupal and Fedora spring to life if I add --userid=1 when running the migrations via Drush - this causes Drupal to relay the correct bearer auth to Fedora. May not be an issue when using the web interface.
Excellent tutorial! Your explanation of how migrations work is very clear and complete. It not only documents how Migrate works for Islandora repo objects, but also how the nodes, files, and media make up the Islandora data model.
Running the following imported the nodes, files, and media:
resulting in:
👍
But, no thumbnails were generated (in the Media tab only the Original File is listed), and it appears that the images have not been pushed into Fedora (I'm getting 404s for file UUIDs). All of my Islandora-provided Contexts are enabled as far as I can tell.
Also, when I tried to run the migration group via the GUI by executing the Media migration, it failed. I assumed that since the media migration config contains
running the media migration would automatically fire the two dependencies.
The text was updated successfully, but these errors were encountered: