Bug 133094 - exif-changes by external prog has no affect inside digikam
Summary: exif-changes by external prog has no affect inside digikam
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Exif (show other bugs)
Version: 0.9.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-27 22:37 UTC by Christoph
Modified: 2017-08-13 07:27 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 1.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph 2006-08-27 22:37:06 UTC
Version:           0.9.0-beta1 (using KDE 3.5.4 Level "a" , unofficial build of SUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15.11-default

when I modify the exif- or iptc-information of pictures, which are allready in the digikam-database, with an external programm (e.g. image exiftool), digikam will not show these changes, nor after actuating the pic neither after restarting digikam.

with all external programms which are able to show these changes will be shown correctly, in every operating system
Comment 1 Christoph 2006-08-30 10:39:29 UTC
This problem also occours on manipulationg tags from outside digikam.

Is digikam storing such information in its database? So it should compare allways these information with that inside the pic
Comment 2 Marcel Wiesweg 2006-08-30 17:26:29 UTC
File name, date, comment, rating and of course the tags are stored in the DB.
All other file metadata (right side bar metadata tab) is read directly from the image file.
What EXIF/IPTC field are you referring to?
Comment 3 Christoph 2006-08-30 18:01:35 UTC
Keywords; seems to be the field where the tags are also stored in file by digikam if not existing there

If needed I can create example txt-files with exifimagetool, one befor manipulating and one after manipulating the datas by digikam ...
Comment 4 caulier.gilles 2006-08-30 18:05:32 UTC
Note: later 0.9.0, i propose to duplicate in database the most important informations from Exif/markenote about photograph to perform search into (like lens, aperture, exposuremode, camera model, etc.). There is another file in B.K.O about this subject.

But this is for later than 0.9.0 to unbreak database structure.

Gilles
Comment 5 caulier.gilles 2008-12-04 16:07:04 UTC
All main image metadata are now hosted in digiKam 0.10.0 database.

Somebody can test if this entry still valid with digiKam for KDE4 ?

Thanks in advance

Gilles Caulier
Comment 6 caulier.gilles 2008-12-05 09:19:30 UTC
Andi, Marcel,

can you check if this problem still exist with digiKam 0.10.0, else we can close this file too...

Gilles
Comment 7 Andi Clemens 2008-12-05 09:51:59 UTC
I just checked it with 0.10.
I changed the author name in IPTC as well as some other information. It works fine.
Only tags will not be updated, you need to synchronize your images then.

Andi
Comment 8 caulier.gilles 2008-12-05 11:13:06 UTC
Andi,

Tags are now stored in XMP by priority, not IPTC, duing lack of string size and char encoding as UTF8 with IPTC

Gilles

Comment 9 Dahaniel 2009-06-15 20:52:06 UTC
I can confirm this bug for 0.10. 
Tags added from another program do not show up under the thumbnail or using the filters but do appear in the metadata sidebar.

The database entry is not being updated even when I refresh or hit "Sync Metadata with Database".
Comment 10 thdox 2009-06-19 22:42:48 UTC
I confirm this bug on digikam 0.10.0 on Ubuntu 9.04
If I update (out of digikam, using either exiftool or exiv2, I've tried both) the comment/legend of a picture, it is *not* updated in legend field of legend/tag right tab.
It *is* updated in metadata right tab.
Comment 11 Marcel Wiesweg 2009-07-31 20:59:33 UTC
This problem is fixed for 1.0. The "Sync Metadata with Database" has been given a more correct name (Write metadata to images) and an action "Reread metadata from images" has been added. This action triggers an update using exactly the same code as if the image was newly added.

Referring to the original report: digikam will not automatically reread the metadata all the time; after modifying with an external program the rereading must be manually triggered.