| Summary: | Metadata lost on face tag change | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | kde |
| Component: | Metadata-Xmp | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/-/commit/d74734341cb855c15a8f639fbf2fafe786227c01 | Version Fixed/Implemented In: | 9.0.0 |
| Sentry Crash Report: | |||
|
Description
kde
2026-01-01 23:31:52 UTC
Do you use XMP sidecar ? Exiv2 or ExifTool metadata backend ? These metadata fields are initially presented without a hierarchy and, according to the metadata standard, should only contain individual keywords. If your other program has stored a path here, that's incorrect. [EXIF::Windows Keywords] [XMP::Subject] [XMP::Last Keyword XMP] Maik Please note that faces stored in WLP do not have a path. digiKam will only assign the face to the People/ directory if it already exists there; otherwise, it will use the hierarchy found in the image. Please provide a sample image. Maik (In reply to Maik Qualmann from comment #3) > Please note that faces stored in WLP do not have a path. digiKam will only > assign the face to the People/ directory if it already exists there; > otherwise, it will use the hierarchy found in the image. > > Please provide a sample image. > > Maik Though I read this before in the documentation, I still can't understand what it means. Clearly, on an initial scan, nothing exists in the People/* section but still, most of my face tags are there. Only a couple names were wrongly assigned to other locations. In all cases, modifying the face tag should not remove the standard tag from the image, at least, without asking first... As for the sample image, do you have a location I could use to send it privately as it shows real people and that I couldn't post it publicly. Finally, about your assessment that [EXIF::Windows Keywords] (behind the scene, XPKeywords) shouldn't contain hierarchy, let me argue that, as also highlighted for the WLP face regions tags, this tag is an EXIF extension by Microsoft so, I figure, the use Microsoft does of it should be truth doesn't it? (In reply to caulier.gilles from comment #1) > Do you use XMP sidecar ? Exiv2 or ExifTool metadata backend ? Almost forgot. In that specific case, I was using ExifTool. Git commit a2a66c07ec873ff5c64b9a44338db0bdc2397e12 by Maik Qualmann. Committed on 02/01/2026 at 20:53. Pushed by mqualmann into branch 'master'. check/use an existing tag path for the face in the image Related: bug 392008, bug 416213 FIXED-IN: 9.0.0 M +2 -2 NEWS M +2 -0 core/libs/database/item/scanner/itemscanner_p.h M +24 -5 core/libs/database/item/scanner/itemscanner_photo.cpp https://invent.kde.org/graphics/digikam/-/commit/a2a66c07ec873ff5c64b9a44338db0bdc2397e12 I'll test the behavior of Exif::XPKeywords tomorrow on a Windows machine. Note that ExifTool itself no longer recommends using XPKeywords, partly due to the encoding in UCS2. You can see my email address in the bug tracker if you log in, unless you reply via email (which you shouldn't). Maik Git commit d74734341cb855c15a8f639fbf2fafe786227c01 by Maik Qualmann. Committed on 03/01/2026 at 20:28. Pushed by mqualmann into branch 'master'. Exif.Image.XPKeywords can be created as a tag path property FIXED-IN: 9.0.0 M +1 -1 NEWS M +33 -3 core/libs/metadataengine/dmetadata/dmetadata_tags.cpp M +1 -2 core/utilities/setup/metadata/namespaceeditdlg.cpp https://invent.kde.org/graphics/digikam/-/commit/d74734341cb855c15a8f639fbf2fafe786227c01 It is now possible in the advanced digiKam metadata settings to disable the existing entry for Exif.Image.XPKeywords and create your own with the tag path property. According to AI, Microsoft never used hierarchical tags in the Photo Editor. I can't find any examples of this online either. Even with the current Explorer, keywords are stored as individual strings, regardless of whether any separator is used. You can now create Exif.Image.XPKeywords or Xmp.dc.Subject yourself so that digiKam can read and write tag paths. Maik (In reply to Maik Qualmann from comment #9) > It is now possible in the advanced digiKam metadata settings to disable the > existing entry for Exif.Image.XPKeywords and create your own with the tag > path property. > > According to AI, Microsoft never used hierarchical tags in the Photo Editor. > I can't find any examples of this online either. Even with the current > Explorer, keywords are stored as individual strings, regardless of whether > any separator is used. > > You can now create Exif.Image.XPKeywords or Xmp.dc.Subject yourself so that > digiKam can read and write tag paths. > > Maik I juste sent to the sample pictures. And you are right that except for the the separator, no structure was present to mark this as hierarchical but still, it seems to be read as such by other softwares like DigiKam and Synology Photo Station since the hierarchy is correctly imported in both softwares. This being said, how can I get myself out of this trap without having to go one by one over thousands of pictures and retag the person and make sure the original "Sent To/Person/John Doe" tag is maintained? |