Project

General

Profile

Bug #10447

Darktable selects all tags in a hierarchy

Added by Kenneth Ingham over 4 years ago. Updated over 4 years ago.

Status:
Incomplete
Priority:
Low
Assignee:
-
Category:
General
Start date:
05/07/2015
Due date:
% Done:

20%

Estimated time:
Affected Version:
1.6.3
System:
openSUSE
bitness:
64-bit
hardware architecture:
amd64/x86

Description

I use digikam to for tagging and metadata management. It writes metadata to sidecar (.xmp) files, which darktable appears to read. However, I have a tag hierarchy. For example, I might have the following tag:
Where/United States/New Mexico/Albuquerque/Old Town
If this tag is applied to a raw file, darktable does put the tag in the exported file (contrary to what is reported in feature request 10430, where it says this will not exist till 2.0). However, darktable also puts the following tags in the file that were not in the original:
Where
Where/United States
Where/United States/New Mexico/
Where/United States/New Mexico/Albuquerque
In other words, it is adding tags for all levels of the hierarchy. This is incorrect.

History

#1 Updated by Tobias Ellinghaus over 4 years ago

Kenneth Ingham wrote:

[...]

If this tag is applied to a raw file, darktable does put the tag in the exported file (contrary to what is reported in feature request 10430, where it says this will not exist till 2.0).

That ticket is about including everything from the sidecar. Stuff dt understands has been included forever.

However, darktable also puts the following tags in the file that were not in the original:
Where
Where/United States
Where/United States/New Mexico/
Where/United States/New Mexico/Albuquerque
In other words, it is adding tags for all levels of the hierarchy. This is incorrect.

Could you please share one such XMP file and an exported JPEG with us?

#2 Updated by Kenneth Ingham over 4 years ago

Here are a pair of files plus a screen shot of the exported file in showing the tags in digikam.

#3 Updated by Tobias Ellinghaus over 4 years ago

  • % Done changed from 0 to 20
  • Status changed from New to Incomplete

Since file uploads seem to be still broken right now I would like to ask you to put these somewhere else for the time being?

#4 Updated by Jan W over 4 years ago

I see the same issue and have put some files here: https://www.dropbox.com/sh/0tep4hvjn3b0dgo/AABwA_xw33dKGvgod8WSSagSa?dl=0
The ARW is the raw Photo straight from the camera. The xmp file is produced by digikam, containing the tags. The jpg is produced by Darktable. I have added the tag buildings|netherlands|amersfoort|hotel.

When I look at the jpg exif information I see the following output:

Subject : amersfoort, buildings, hotel, netherlands
Hierarchical Subject : buildings|netherlands|amersfoort|hotel

To me it seems the output is correct, and Darktable is correctly handling the tags and putting them in the jpg. Anyone care to confirm that?

#5 Updated by Tobias Ellinghaus over 4 years ago

To me this looks good, we add the lr:hierarchicalSubject with the whole shebang and all individual parts as dc:subject. When reading the resulting file we only import the lr:hierarchicalSubject and ignore the individual pieces. That's however not what the original report was about, that mentions that we also add hierarchical tags with substrings.

#6 Updated by Jan W over 4 years ago

You're right of course. The behaviour I'm seeing is that Digikam is tagging all the levels of the hierarchical tag in the darktable exported jpg. I was assuming this bug report applied to my situation because it is so much like my usecase (raw file + digikam tag + xmp --> darktable jpg --> digikam).
Apologies for the noise.

Also available in: Atom PDF

Go to top