Quote:
Originally Posted by kiwidude
As for where this mapping translation takes place, I wonder whether we can get away with waiting until set_metadata. The situation that comes to mind is the edit metadata dialog, which of course has the ability to display custom column values. Maybe it is a special case. I would have thought you would have to get the metadata object updated into custom columns by when the Download Metadata button has finished so it can refresh the dialog contents (which are not yet persisted)?
|
set_metadata already quite happily sets custom columns, so there would be no problem providing a method to merge the 'named' information into the custom columns in the mi structure.
We would also need to change update_from_mi in the single metadata dialog to update the custom widgets, which it currently does not do. This would be a pain because of the number of changes, but the intellectual difficulty is low.
EDIT: looking at the code, I think updating the custom widgets from an mi structure is straightforward. Add one method to a base class then add a loop over the mi structure that passed an mi structure instead of a book_id.