Bug 252406

Summary:	"Import EXIF" does not update cached Metadata
Product:	[Applications] digikam	Reporter:	bugzilla
Component:	Plugin-Generic-GeolocationEdit	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	caulier.gilles, frederic.coiffier
Priority:	NOR
Version:	4.5.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description bugzilla 2010-09-26 11:41:40 UTC

Version:           1.4.0 (using KDE 4.4.4) 
OS:                Linux

I use the Metadata->Import EXIF functionality regularly to copy the EXIF information from the first used image back to the generated panorama (which in my case does not have any EXIF written).
Unfortunately, this action does not update the cached Metadata of the panorama which still shows up as having no metadata at all. Especially when trying to add geolocation information later, it will fail for this image because it has no EXIF at all.
"Import EXIF" therefore should update the stored metadata for the selected picture after completition.

Reproducible: Always

Steps to Reproduce:
Take a picture without metadata, import EXIF from another picture

Actual Results:  
The picture itself has the EXIF added, but digiKam still shows no EXIF

Expected Results:  
digiKam should update its metadata cache to reflect the new EXIF

OS: Linux (x86_64) release 2.6.34.7-0.3-default
Compiler: gcc

Comment 1 caulier.gilles 2010-09-26 14:32:03 UTC

It must through digiKam kipi interface. Perhaps we have forget to bring digiKam DB with metadata changes done by the plugin...

Gilles Caulier

Comment 2 Marcel Wiesweg 2010-09-26 15:24:13 UTC

Gilles, what would be the KIPI API method to call for this purpose?

Comment 3 caulier.gilles 2010-09-26 19:28:31 UTC

Marcel,

Has you can see there, i use this method in plugin :

http://lxr.kde.org/source/extragear/graphics/kipi-plugins/metadataedit/plugin_metadataedit.cpp#335

In digiKam kipi interface, look what's done :

http://lxr.kde.org/source/extragear/graphics/digikam/utilities/kipiiface/kipiinterface.cpp#152

All sound fine for you ? 

Gilles Caulier

Comment 4 Marcel Wiesweg 2010-09-29 10:16:14 UTC

I see. 
This currently triggers a "normal" rescan, as if the modification date changes. For some cases, like reported here, it will be appropriate to have a full rescan, as done by "Reread metadata from file" in the menu.
But in other cases, this will not be appropriate, for example when the JPEG lossless plugin only has rotated the image and (probably) calls refresh to update the thumbnail.

Comment 5 caulier.gilles 2010-09-29 10:22:23 UTC

So, perhaps a new kipi interface method must be designed for this task in case of plugin need to rescan indeep metadata. Fine for you ?

Gilles

Comment 6 Marcel Wiesweg 2010-09-29 17:35:51 UTC

Yes, sounds good. I would propose at least two distinct cases: Image data changed (JPEG lossless, batch tools) and metadata changed (metadata edit, GPS correlator). Not sure if there are other use cases of this method.

Comment 7 Marcel Wiesweg 2010-09-29 17:38:48 UTC

correcting myself, the GPS correlator of course works changing attributes, as does the time adjust plugin.

(Another related need, thinking of batch plugin or raw converter, would be to indicate the relation of images (xy.jpg is produced by raw conversion from xy.mrw) , now that we have lossless editing.)

Comment 8 Frédéric COIFFIER 2014-09-13 20:16:39 UTC

Problem still present in digiKam 4.2.0.
When I import EXIF, if I do not manually "Reread metadata", nothing happens (no date change, no new title or other metadata). So, Import EXIF could appear useless...

Comment 9 Frédéric COIFFIER 2014-11-21 08:14:16 UTC

Still present in digiKam 4.4.0.

Marcel, Gilles : Any news about this problem ?
Could you set it as CONFIRMED ?

Comment 10 caulier.gilles 2016-07-06 16:26:59 UTC

GPSCorrelator is not a kipi plugins anymore. It have been integrated as well in digiKam core.

This file still valid using last digiKam 5.0.0 ?

Gilles Caulier

Comment 11 caulier.gilles 2016-11-26 09:47:24 UTC

This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release ?

It available at this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

Comment 12 caulier.gilles 2020-08-03 05:01:13 UTC

digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier