Bug 282728 - Importing photos with "Date based subalbums". The folder name "date" is wrong
Summary: Importing photos with "Date based subalbums". The folder name "date" is wrong
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: 2.3.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-25 08:39 UTC by jonas karlsson
Modified: 2017-08-16 06:14 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.0.0


Attachments
Jpg file (77.71 KB, image/jpeg)
2011-09-25 11:42 UTC, jonas karlsson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jonas karlsson 2011-09-25 08:39:26 UTC
Version:           2.1.1 (using KDE 4.6.2) 
OS:                Linux

I am importing jpeg files taken on diffrent dates. Alle files are imported into a single date folder - The date of today. 

I looked in the EXIF of the jpg files and fields "Date and Time (original)" are correct. I attached one of the jpg files. 

Reproducible: Always

Steps to Reproduce:
Import the attached jpg file. 

Actual Results:  
imported the photo into the date of today

Expected Results:  
imported the photo into a subfolder based on the date the photo was taken.
Comment 1 jonas karlsson 2011-09-25 11:42:22 UTC
Created attachment 63950 [details]
Jpg file
Comment 2 bubukind 2011-11-28 02:28:34 UTC
Can confirm this behavior. 

Applies to both subfolder creation and filenames when using a user defined file name for the photos like "[date:yyyy-MM-dd]_#.[ext]" 

Version: 2.1.1
Comment 3 bubukind 2011-11-28 02:33:08 UTC
Digikam seems to use the file system "changed" information instead of the exif data which seems to be a good fallback but only IF exif is not available. 

Another set of images which I imported today also imported to a wrong date but not the date of today but the date they were last copied with a method not preserving the changed time.
Comment 4 caulier.gilles 2011-11-28 06:17:19 UTC
It's reproducible with 2.3.0 release ?

Gilles Caulier
Comment 5 bubukind 2011-11-28 15:41:24 UTC
Checked out the package version 2.3.0 from ppa:philip5/extra and behavior stays the same.
Comment 6 Teemu Rytilahti 2013-12-05 01:05:16 UTC
Is this still reproducable?
Comment 7 Teemu Rytilahti 2014-01-02 08:40:45 UTC
This is reproducible when the use meta data option is unchecked. Per default digiKam uses the timestamp of the file or in the case of gphoto2 cameras the information reported by gphoto2. Not a bug so to say, if you want this behaviour, enable use file metadata from settings -> cameras -> behaviour.

There's also a bug in handling of that setting which is fixed in 4.0. In the meanwhile, adding UseThemeBackgroundColor=true to [Camera Settings] section inside digikamrc works as a temporary solution.