While we have (if we do say so ourselves-) a nice UI for viewing field mappings and their statuses, in the context of the large migrations we typically do the latest field mappings are in our development environments and not easily shareable with the rest of the project team. We've found it more effective to layout source and destination fields in a shared Google spreadsheet, where we can teleconference and review mappings, updating live as we go. To populate those spreadsheets, I propose exporting field mapping info to a CSV file which can be imported into a spreadsheet. We already have the drush migrate-destinations command, so I plan on adding a --csv flag to that.

And, yes, what would be REALLY cool is to import changes made in the spreadsheet back into Migrate module mappings. That will probably have to wait for #1123538: UI for defining migrations....

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Fixed

Committed the following changes for D7 and D6:

  • The migrate-descriptions command has been renamed to migrate-mappings (since mappings are what it's really about).
  • The --csv option produces the output in comma-separated form.
  • The --full option adds the destination and source field descriptions (the result is generally going to be too wide for interactive use, it's primarily for use with --csv).
  • The Done and DNM/Do Not Migrate groups are sorted to the end, on the assumption that other issue groups representing open issues are more interesting.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.