| Summary: | Problem reading Excire Foto software tags from JPEG files | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | LarsE <ristretto17> |
| Component: | Metadata-Xmp | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/commit/fce51f439ef2a2d4c577e0ace4d79857fd40ea51 | Version Fixed/Implemented In: | 7.5.0 |
| Sentry Crash Report: | |||
| Attachments: | JPEG file with Xmp.dc.subject and Xmp.excire.hierarchicalSubject element to reproduce this issue | ||
|
Description
LarsE
2021-12-25 10:37:57 UTC
Created attachment 144854 [details]
JPEG file with Xmp.dc.subject and Xmp.excire.hierarchicalSubject element to reproduce this issue
Your problem is understanding how digiKam reads tags or other metadata. You expect all metadata tags to be read. This is not the case, however, if digiKam finds tags, the list is no longer processed. When I position the new entry with Xmp.excire.hierarchicalSubject at the top, the metadata is read. Remember, we cannot read all tags, this would completely break the workflow for other users. Many proprietary programs only write one metadata tag and leave the other possible tags unused or old. Maik Hi Maik, thanks for your quick reply and your explanation which I really appreciate! Great to hear that the import is possible, I didn't try to change the order, since it was not clear to me, that as soon as one active definition matches, all other active definitions will be skipped. That's indeed a pity, since I therefore need to refresh once, switch the sequence and refresh once again. What do you think, would it be possible to allow (as an option, not per default, to ensure compatibility for existing workflows as you explained) that all activated items are taken into account when reading the metadata? Since the user has the possibility to switch off unneeded items, I would assume that such change might be safe and a big improvement (OK, at least for my workflow ;-). Best wishes, have a pleasant x-mas time and a happy new year. Cheers, Lars. (In reply to LarsE from comment #3) > Great to hear that the import is possible, I didn't try to change the order, > since it was not clear to me, that as soon as one active definition matches, > all other active definitions will be skipped. That's indeed a pity, since I > therefore need to refresh once, switch the sequence and refresh once again. I just checked as you suggested and found, that the tags that were already assigned before (Xmp.dc.subject) are completely replaced by the Excire tags (Xmp.excire.hierarchicalSubject) during the second refresh. I thought they would be added... Well I think my suggestion may be quite beneficial in such situations ;-) Git commit fce51f439ef2a2d4c577e0ace4d79857fd40ea51 by Maik Qualmann. Committed on 25/12/2021 at 14:35. Pushed by mqualmann into branch 'master'. add option to read entire list for tags FIXED-IN: 7.5.0 M +1 -1 NEWS M +38 -18 core/libs/metadataengine/dmetadata/dmetadata_tags.cpp M +19 -4 core/libs/metadataengine/dmetadata/dmetadatasettingscontainer.cpp M +3 -0 core/libs/metadataengine/dmetadata/dmetadatasettingscontainer.h M +25 -7 core/utilities/setup/metadata/advancedmetadatatab.cpp M +1 -0 core/utilities/setup/metadata/advancedmetadatatab.h https://invent.kde.org/graphics/digikam/commit/fce51f439ef2a2d4c577e0ace4d79857fd40ea51 (In reply to LarsE from comment #4) > I just checked as you suggested and found, that the tags that were already > assigned before (Xmp.dc.subject) are completely replaced by the Excire tags > (Xmp.excire.hierarchicalSubject) during the second refresh. I thought they > would be added... Well I think my suggestion may be quite beneficial in such > situations ;-) If tags have disappeared after the 2nd run, then you have activated the option to clean up the database by reading metadata. With the new option to read all tags from the list, this no longer matters. Maik (In reply to Maik Qualmann from comment #6) > If tags have disappeared after the 2nd run, then you have activated the > option to clean up the database by reading metadata. I was looking for such option, but didn't find it... Thanks for your hint! > With the new option to read all tags from the list, this no longer matters. OMG, kudos & thanks a million for implementing the suggestion so quickly! Lars. Git commit 81418a0c19ab7e775380296e0b14c9f3d88a3d1e by Maik Qualmann. Committed on 25/12/2021 at 16:46. Pushed by mqualmann into branch 'master'. add register extra namespace "excire" M +1 -0 core/libs/metadataengine/engine/metaengine.cpp https://invent.kde.org/graphics/digikam/commit/81418a0c19ab7e775380296e0b14c9f3d88a3d1e |