Migration Configuration: a configuration file that brings the configuration of all the source, destination, and process plugins to make a migration. Process Plugins: a class defining how to transform data from the source to something that can be used by the destination or other process plugins you can find a full list of what comes with core in Migrate’s documenation.Destination Plugins: a class defining how to store the data received in Drupal 8.Source Plugins: a class defining the query, initial data alteration, keys, and fields provided by the source.You can find an example inside the Migrate Plus module. In Drupal 8, the concept of a migration has been abstracted out into the various parts that makes them reusable and feel more like “building with blocks” approach. Prepare: a function where you do all your data processing.Class Constructor: where you define your source, destination, and field mapping.The structure of the migration tends to be one big blob of logic (broken up by class functions of course) around a single migration. You can see an example of a Drupal 7 migration in the Migrate Example module. In Drupal 7 Migrations are strictly class-based. Since we have the 100 mile high view of what the end game is, lets talk a little about why and how this works. The added bonus is that you can use that as a starting point and modify them from there. Doing so would build out templated upgrade configurations that would move all data from Drupal 7 or Drupal 6 to Drupal 8. The proposed solution was to use the -configure-only method on the drush tool migrate-upgrade. Given they had field collections, entity references, and the fact that the Migrate Drupal module was still very much experimental for Drupal 7 upgrades, this didn’t pan out with a complete migration of their data. In fact, our client had started down the path of using Migrate Drupal to upgrade their site to D8. Also, the new automated migration system- Migrate Drupal-that came with core was particularly intriguing. I was particularly stoked in the fact that everything in Drupal 8 is considered to be an entity. Since this was one of our first Drupal 8 sites, I was the first to dig my hands into the migration system. Since our client had 65 content types and 84 vocabularies to weed through, our challenge was to build all those migrations into their budget and schedule. Our client, the NYU Wagner Graduate School of Public Service was no exception when they decided to move to Drupal 8. If you’ve come here, you probably want to learn how to speed up your migration development so you can move on to more fun aspects of a project. In the end, the completeness of the migration depends partly on how much time your client is willing to spend on building out migration for each piece of their content and settings. This process uses hours of development time and often has one developer dedicated to it for the first half of the project. One of the things that Drupal developers do for clients is content migration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |