Bug 379049 - IPTC and XMP metadata not always read when adding a new album
Summary: IPTC and XMP metadata not always read when adding a new album
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 5.5.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-21 17:10 UTC by ulrich.demlehner
Modified: 2019-03-16 12:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 6.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ulrich.demlehner 2017-04-21 17:10:33 UTC
I'm just starting to manage my pictures with DigiKAM. My pictures are stored in separate subdirectories and I add them to DigiKAM by creating a new album for each subdirectory I'm adding. The pictures have EXIF, IPTC, and XMP metadata. What I see is that DigiKAM is always able to read and to display the EXIF data, but in approx 50 % of all cases, DigiKAM does not read and display the IPTC and XMP metadata. DigiKAM indicates in those cases that there aren't any IPCT or XMP metadata contained in the picture, but Irfanview is able to display the IPTC and XMP metadata in all those cases, so I'm quite sure that the metadata are really in the pictures. In most cases no picture in a specific subdirectory/album has IPTC or XMP metadata in DigiKAM, but I also have a subdirectory/album where some pictures in this subdirectory do have metadata and some do not.

Thanks for your support!

Ulrich
Comment 1 caulier.gilles 2019-03-15 10:32:12 UTC
Ulrich,

The 6.1.0 pre-release installer have been updated this morning. Please test and
report to see if you can reproduce the dysfunction:

https://files.kde.org/digikam/

Gilles Caulier
Comment 2 ulrich.demlehner 2019-03-16 11:18:21 UTC
Hi Gilles,

I have to confess that I do not see the reported problem currently in my data. I'm now running v5.9.0 of DigiKam and if I remember correctly, there was an update between my issue reporting and my current version. So it might be that the update already solved the problem or it might be that I had made a mistake back then. I simply do not know, I've lost track of the issue. Sorry for that!

Thanks for your support!

Ulrich
Comment 3 caulier.gilles 2019-03-16 12:30:54 UTC
Thanks for the feedback. So i close this file now.

Gilles Caulier