This year I had an honor to present at BADCamp and talk about development of Feeds_Migrate module. I am very grateful to James Dixon, Youri van Koppen and Lucas Hedding who put a lot of work to make demo for this presentation possible in a very short timeframe.
FEEDS UI + MIGRATE ENGINE = DREAM MIGRATIONS AND IMPORTS
Here are some notes that came out of the presentation
- It is important to have issues/tasks small and well defined so a developer can grab one issue, work on it and submit a patch.
- Migration that we are defining in Migrate module contains "pre-coded" data source, and therefore it can have button "execute" http://dev-feeds8.pantheonsite.io/admin/structure/migrate/manage/default/migrations. If these migrations will have button Edit, more work needs to be done to make sure that we will not break migrations defined in .yml files
- Migrations that are defined via Feeds_Migrate module do not have data source, therefore the CANNOT have button Execute. I propose that we have a special migraiton group called "Feeds Migration Mappers" and do not have button "Execute" on feeds in this interface. Logical url for such group would be /admin/structure/migrate/feeds_mappers and it is great to have this tab as seen on page http://dev-feeds8.pantheonsite.io/admin/content/feeds-migrate
- Feeds Mappers are used in Feed Importers http://dev-feeds8.pantheonsite.io/admin/content/feeds-migrate and have buttons Import(execute), rollback, etc. I think that terminology Mappers and Importers are very good names. We might call them feed mappers, migration mappers, or just mappers, or feed migraiton mappers :)
Looking forward to doing more with this module.