digikam default options

[Chris Green]

On Sat, Jan 14, 2017 at 08:44:09AM -0700, Andrey Goreev wrote:
>    Cerp
> 
>    I think Linux does not save "date created" for files on only keeps
>    "date modified" instead. So if you are using Linux and updated file
>    stamps you lost chronological order in the file browser (nautilus,
>    etc.) Windows keeps both "date created" and "date modified" as well as
>    its file explorer allows users to sort files by any date including exif
>    date taken.
> 
Linux has *three* times associated with a file (doesn't care what sort
of file):-

    chris$ lt baby1.jpg

    Times for file baby1.jpg
    2016-02-07  19:31:08.35 Modifed
    2017-01-14  15:32:55.71 Accessed
    2017-01-13  12:20:53.90 Status changed

(lt is a utility I wrote)


>    So if you are a Linux user you get harmed by digikam for not going
>    through all the options in the beginning. You can fix the dates using
>    exiftool (exiv2 will probably do that too) but that's at least 30 min
>    of your life you will never get back.
> 
I want a picture's "time" to remain with the picture whatever I do to
the file containing the picture, therefore it's completely pointless
IMHO to use the file system's times to indicate anything about the
image contained in the file.

If I copy the above image - baby1.jpg - the file system times for the
copy will be set to the date when I made the copy.  Only the times in
the Exif and IPTC metadata will be preserved and indicate when the
picture was taken.

Also, as I said in another comment, backup programs and such rely on
the Modified and Accessed times to decide whether a new backup should
be made.

-- 
Chris Green