[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #25 from Ralf S --- Thanks Maik, you led me on the right path. I fiddled around with different orders and with [1] Xmp.lr.HierarchicalSubject, [2] Xmp.dc.Subject [3] Xmp.digiKam.TagsList everything seems to work like I want it, in both

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #24 from Maik Qualmann --- Lightroom will probably only change a metadata type e.g. Xmp.lr.HierarchicalSubject or Xmp.dc.Subject. digiKam writes its own XMP tags list in the metadata and reads them out again by default. However, since

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #23 from RS --- Thanks a lot for your explanation, Maik – what you describe is essentially what I had expected. Unfortunately reality doesn’t exactly match my expectations: I have checked 'Clean up the metadata from the database when

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #22 from Maik Qualmann --- The setting for cleaning up the database is in the digiKam settings under Metadata as a check box. If external tags are removed, they are otherwise not removed from the images in the database. This is intentional,

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 RS changed: What|Removed |Added CC||shopp...@ralfschmid.net --- Comment #21 from RS --- >>

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 Maik Qualmann changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #20 from Maik Qualmann --- Yes, this is the correct settings. Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #19 from Sebas --- Understood. So if I want to only write to sidecar for unsupported files I should enable: [X] Write to sidecar files: Write to XMP sidecar for read-only item only And to later read from it, I guess also: [X] Read from

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #18 from Maik Qualmann --- You can not remove tags in MOV files. DigiKam can not write to video files. You would have to activate sidecar and if this sidecar is then available, digiKam would not add the tags again because they will no

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #17 from Sebas --- I removed tags from MOV-files in Digikam, then removed the tags from database. Then, after starting with a new database due to the PNG-bug, the MOV-files came back with the tags attached ánd enabled again. -- You are

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #16 from Maik Qualmann --- If you remove metadata externally and digiKam should also remove it, you must enable the option in the metadata setting to clean up the database. This is a option and no longer depends on whether you have enabled

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 Sebas changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.0.0

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #13 from Maik Qualmann --- Git commit 6ed95813516deeaebfb0275625a892fedbb601c4 by Maik Qualmann. Committed on 12/04/2018 at 18:19. Pushed by mqualmann into branch 'master'. add function to remove all image attributes

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #12 from IWBR --- I've been doing some tests to determine the exact nature of this behavior. Let's say that some tag was removed from a group of pictures, so it no longer exists. Digikam does not remove that tag

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #11 from IWBR --- I understand there might be people who prefer to have a read-only picture library, and only using digikam's database to organize it. In the configuration menu, there are already a few checkboxes

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 Maik Qualmann changed: What|Removed |Added CC||iwannaber...@gmail.com

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 Nicofo changed: What|Removed |Added CC||nic...@tuxfamily.org ---

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #8 from Maik Qualmann --- No not yet. I will now make it for digiKam-5.9.0. Meanwhile, my idea is that if we do a full scan of the image, optionally delete all tags and comments from the image in the database

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 Steve Braun changed: What|Removed |Added CC|

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #5 from fa...@mereghettisnc.it --- (In reply to Maik Qualmann from comment #4) > *** Bug 383924 has been marked as a duplicate of this bug. *** Maybe you can enable the DB updating after a re-reading only for selected images. And maybe add

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 Maik Qualmann changed: What|Removed |Added CC||fa...@mereghettisnc.it

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #3 from Maik Qualmann --- I understand the problem. Yes, if a tag is no longer present, it is not deleted from the database. There are users who only store their metadata in the database. The database would be empty

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #2 from Sebas --- Yes that's not the problem in this bug. The problem is that rescanning a tagless file still keeps Digikam displaying the removed tags, so Digikam must be loading them from database. Please read

[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned

https://bugs.kde.org/show_bug.cgi?id=380876 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com