Currently, you select an image and the keywords are displayed, you select a 2nd image the keywords not present in it are grayed out but the keywords of this image are not displayed.
It would be good, if we could visualize all the keywords of the selected images and put in gray those which are not used in all these images.
This makes it possible to make changes to several images at the same time.
Cool idea, I voted. But as the devil’s in the detail:
How to avoid the maximum amount of displayed keywords with grey and white ones to be assigned on all images, so that all selected images at the end have every single keyowrd of the group? I tried that with Excire and the result really is not always predictable. Especially when I need to remove assigned keywords. Syncronizing them appears to be a dark art…
If the keyword is white, it is attributed to all selected images, if it is gray it is only attributed some images.
Currently by making a right click on a grayed keyword we can attribute to all selected images.
Common keywords assigned, now I need specific keywords for only few of the selected images. If that right-click would allow me to tick the appropriate keywords used in the selection for each image separately, it could be a benefit.
If I understand well this, for me, on Mac, it’s already working like that: I select one image with 3 keywords displayed, then another image with 2 commons keywords, one new and one from first image not in. I have the 4 keywords, 2 as commons and 2 in gray which are not in all images.
Keywords with one image:
In Photo Mechanic there is a possibility to “Replace” or “Add”. So, Add vill keep the integrity of already present keywords and “Replace” will wipe all the present keywords and replace them with whatever I decide to put there instead. There are just two check boxes and easy to forget to change. I have made a few mistakes both with PM and even more with FotoWare Fotostation forms. In PM I haven´t found any safety net and I wonder if the history can be of any help in Photolab since it´s “Image centered” and I guess can´t handle cases like this. You can´t roll back a batch update in a SQL database either just transactions.
The only way seems to be making a backup before one starts to batch update.