[Digikam-devel] [digikam] [Bug 331695] Misleading menu entry may lead to unintentionall purging of all tags

[Michal Sylwester]

https://bugs.kde.org/show_bug.cgi?id=331695

--- Comment #7 from Michal Sylwester <msylwester at gmail.com> ---
I think there are several use cases that behave differently...
I think IPTC handling was written to not touch unknown tags (don't remove all
tags, just those being changed). However in my experience with XMP the old tags
are removed (this is empirical, not from code...).

There are some strange scenarios where synchronization of metadata is not
behaving the way I would expect, but tags in my files are quite a mess, so I
haven't reported them as I think sometimes this could be the reason... Also I'm
not 100% sure how some operations are supposed to work.

Normally I keep metadata in sync with db. Normal tagging is straightforward, I
add a tag, click apply, it's metadata is updated.
2 examples where it's not read/written:
1. When file is tagged outside digikam, it seems to detect the change (file
seems to be reloaded), but tags are not updated until manually running "reread
metadata..."
2. When tag is deleted (right click on tag, "delete tag"), it's gone from
digikam but metadata is only written after manually triggering "write metadata"
(my workaround: first manually remove the tag from all images - this will
update the metadata, and only then really delete the tag itself)

-- 
You are receiving this mail because:
You are the assignee for the bug.