I also request a return of checkboxes (AKA tick boxes
) representing ALL values of the current field, as an alternative to the new/alternative methods. This is (was) a unique capability of MC that handles a range of needs not met by the other methods such as pane tagging or search/sublists.
Pane tagging is useful if there are just a few fields to tag. I use it for my photos, for instance. I set up 5 panes, for each of the photo library fields I regularly update: Album, Events, Keywords, People, Places. The 5 panes plus drag-drop, checkboxes, etc. make for fast visual tagging.
But for my music library I would need 31 PANES. (My monitor can't handle it, but could MC do this?) Instead, the method that works very well (used for years) is the Tag action window combined with a custom view and 3 view panes.
My music library has (at least) 31 fields per record to view and edit simultaneously. Usually there are 23 (stock and custom) editable fields to tag, and usually 8 read-only fields I need to see while tagging. Several fields are list-type, which display as multi-line, so it's quite a pile of data. Working with it efficiently was possible through .122, but not in later builds.
I tag this library by having a view designed just to drive the Tag window. The view has all the needed fields, with the columns arranged in the desired Tag window order. The Tag window is set to show all the fields in the view.
View columns are sized so I can see almost all the values (or enough for my task) while moving through the individual fields in the Tag window. This is important because what I put in some tags depends on what I see in other fields of the current and nearby records/rows (a judgment, not formula, so an expression won't help).
The Tag window is height-maximized in the left column, so it shows all 31 or so fields without scrolling -- very efficient to Tab through and update. Also, this provides max vertical space for list-type fields to display their master lists. (Which is why I also request that the lists revert to using the full available height to show values, not just show 25 or fewer as in recent builds.)
To navigate the 80-thousand record database while keeping the Tag window maximized (which covers the tree), the view has panes (usually 3) providing direct access to the fields and grouping levels that I need to navigate, such as Artists (grouping size 1) > Artists > Name (Artists is a custom list-type field).
To handle this situation, I hope Tag window tagging, especially of list fields, can be re-optimized regardless of what other methods MC might offer for other situations.