Bug 267800

Summary: Keywords from IPTC-Metadata are not imported
Product: [Applications] digikam Reporter: Marco Tedaldi <marco.tedaldi>
Component: Database-MigrationAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles
Priority: NOR    
Version First Reported In: 1.4.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 7.0.0
Sentry Crash Report:

Description Marco Tedaldi 2011-03-06 16:06:42 UTC 
Version:           1.4.0 (using KDE 4.5.1) 
OS:                Linux

My sqlite db got corrupted (I've been using it over nfs, so I won't complain). All the keywords and tags had been saved to the metadata of the images.
I've set digikam to use MySQL as a backend this time and imported all the images (about 50000 images in one directory tree). There have been no errors reported on import. But no keywords show up in the database nor in search nor shown on th single image. If I look at the IPTC metadata I see, that the keywords are there.
On the MySQL-Database the table "Tags" is empty!

Reproducible: Didn't try

Steps to Reproduce:
Take a folder structure with images that have the keywords in iptc tags. Use MySQL as backend (Did not try to reproduce it with sqlite until now)

Actual Results:  
No Keywords are imported

Expected Results:  
Keywords should be imported and show up for filtering and adding to new images

I'm running this under ubuntu with a gnome desktop. Images reside on a NFS-Server in my LAN. MySQL-Database runs on the server as well.
I fear that I might loose my IPTC-Keywords if digikam tries to write metadata to the images.
Comment 1 Marco Tedaldi 2011-03-06 16:44:46 UTC 
Could be the same issue as https://bugs.kde.org/show_bug.cgi?id=258409 "Tags and TagsTree table is empty after DB migration from sqlite to mysql"
Comment 2 caulier.gilles 2011-03-06 18:20:11 UTC 
Yes, it's the same issue. I recommend to update digiKam to last 1.9.0 release and try again.

Gilles Caulier

*** This bug has been marked as a duplicate of bug 258409 ***
Comment 3 caulier.gilles 2019-12-30 06:55:42 UTC 
Not reproducible with 7.0.0 beta 1.