Bug 161922 - calendar view/digikam date does not update when exif dates changed externally
Summary: calendar view/digikam date does not update when exif dates changed externally
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Dates (show other bugs)
Version: 0.9.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-10 21:15 UTC by Rich Lott
Modified: 2016-07-15 19:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0


Attachments
Settings for changing the date and time in digiKam (31.76 KB, image/png)
2008-05-24 14:19 UTC, Andi Clemens
Details
screenshot of problem (418.80 KB, image/png)
2008-05-25 20:51 UTC, Rich Lott
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rich Lott 2008-05-10 21:15:48 UTC
Version:           0.9.2-final (using 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.4~gutsy1~ppa2)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.20-15-generic

I took some photos, downloaded them to Digikam, viewed calendar view and it was there that I noticed the dates were 11 May, not 10 May. This was because I had my camera set to the wrong date.

So I quit Digikam, and used the jhead command to adjust the exif dates back to the 10 May. In Digikam, the exif sidebar for the photos now shows the date as 10 May, but in the calendar view the images are still listed under 11 May.
Comment 1 Andi Clemens 2008-05-24 14:18:59 UTC
When I change the date of an image in the EXIF header, I have two entries: "date and time (modified)" and "date and time (original)".

DigiKam seems to take the original time which will not change (well it did not on my system). So when you want to change the date and time for some images, you should do this directly in digiKam:

1. select the images you want to change
2. from the menu select Image->Metadata->Edit EXIF
3. Go to the date and time tab and edit the settings (I will add a screenshot to show you the settings needed)
4. After that, the database will be updated and the date view is correct again.

This should fix your "problem"...
Comment 2 Andi Clemens 2008-05-24 14:19:31 UTC
Created attachment 24921 [details]
Settings for changing the date and time in digiKam
Comment 3 Rich Lott 2008-05-25 20:51:08 UTC
Created attachment 24936 [details]
screenshot of problem

I've attached a screenshot of the problem (for clarity's sake, but I think you
understood anyway)

I appreciate your help, but I was really reporting it as a *bug* that should be
fixed, it actually doesn't bother me much (in this instance) that digikam shows
the image on the wrong date.

Also, a quick fix is to externally rename the folder, eg. append a _, then
digikam will have to reindex the files as it thinks it's new.

I might try the digikam GUI for changing the dates if I need it in future, but
it really should work interoperably with other software, so I do hope that
someone is interested in fixing this (albeit non urgent!) bug at some point.

Rich.
Comment 4 caulier.gilles 2008-05-25 21:00:11 UTC
Rich,

What the problem with your screenshot ? date is the same in Exif viewver from the right and Exif editor dialog...

Gilles Caulier
Comment 5 Rich Lott 2008-05-26 00:57:42 UTC
It is a bit of a spot the difference, I admit!

The problem is that despite what you've pointed out (and -not shown- that the file mtime is also the same date), digikam lists it under 11 May, (see bottom left red circle) instead of 10 May. See original bug report above.

thanks.

Rich
Comment 6 Andi Clemens 2009-10-09 13:33:53 UTC
Rich,

can you still confirm this bug in digiKam-0.10 or digiKam-1.0.0-betaX ?
Comment 7 Rich Lott 2009-10-12 22:09:56 UTC
Hi Andi

I'm running the latest LTS Ubuntu, i.e. Hardy, and according to

http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg1266275.html
"There are no Digikam 0.10.0 packages for Hardy."

I couldn't find a ppa deb archive anywhere, and I'm not really up for 
compiling it as I suspect that would be a beast of a job. Willing if you 
say it's easy...

So can't confirm.

Many thanks for your interest, though!

rich


Andi Clemens wrote:
> https://bugs.kde.org/show_bug.cgi?id=161922
>
>
>
>
>
> --- Comment #6 from Andi Clemens <andi clemens gmx net>  2009-10-09 13:33:53 ---
> Rich,
>
> can you still confirm this bug in digiKam-0.10 or digiKam-1.0.0-betaX ?
>
>
Comment 8 caulier.gilles 2011-12-13 12:52:12 UTC
Rich,

This entry still valid with 2.x release ?

Gilles Caulier
Comment 9 caulier.gilles 2013-11-28 22:49:43 UTC
Rich,

We need a fresh update here. Do you tried digiKam 3.x release ?

Gilles Caulier
Comment 10 caulier.gilles 2015-06-30 08:07:45 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 11 caulier.gilles 2016-07-15 19:04:42 UTC
With digiKam 5.0.0, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier