Posted by Haza on November 23, 2011 at 10:17am
8 followers
| Project: | Migrate |
| Version: | 7.x-2.x-dev |
| Component: | migrate_ui |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
| Issue tags: | Migrate 2.6 |
Issue Summary
Hi,
It would be great to display the group name of a migration on the migration dashboard (and when we use the "drush ms" command) to be able to quickly see and a migration use the group feature and what migration belong to wich group.
Comments
#1
The patch is attached.
Group is display on "admin/content/migrate" and also when using "drush ms"
A quick look on what it may look like :
What do you think about that ?
#2
Actually, what I always had in mind (but never got around to implementing) is visually grouping the migrations, something like this for drush ms:
Group: default Total Imported Unimported Status Last imported
BeerTerm 3 3 0 Idle 2011-11-26 11:54:04
BeerUser 4 4 0 Idle 2011-11-26 11:54:05
BeerNode 3 3 0 Idle 2011-11-21 17:38:18
BeerComment 5 0 5 Idle 2011-11-21 17:38:36
Group: wine Total Imported Unimported Status Last imported
WinePrep N/A N/A N/A Idle
WineBestWith 3 0 3 Idle 2011-11-21 17:38:15
#3
+1 on the grouping. i'd rather not see the list get any wider.
#4
Here a patch for migrate-status output.
I first tried with one drush table per group, but I end up doing it all in one table because IMHO that looks easier to read(all columns at the same width).
In the other side, I guess it is ok to have one more column on the web version at migrate_ui. We could have the grouped html tables(but yet it could be the same problem I mentioned on the last paragraph).
#5
btw, here a ignore-all-space-version of the patch for easier review.
#6
+1 on the grouping #5.
My suggestion for the "Migrate UI":
Add the group on all tabs "Overwiew" of the group, if needed.
#7
Committed to D6 and D7, thanks!
Leaving this issue open for the sake of migrate_ui...
#8
Tagging for 2.6.
#9
This was committed to the wizard_api branch, which is now merged to 7.x-2.x.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.