https://bugs.kde.org/show_bug.cgi?id=386059
--- Comment #3 from hardy.pub...@gmail.com --- Sorry I did not write the exact string in the OP. I shortened it to 1916 but it was a valid format. "YYYY:MM:DD HH:MM:SS". I attach another example screenshot. You can see why I concluded it is associated with PreviewDateTime. Anyway this can be closed because I think I know what's happened now. - I previously used Picasa which may have set DateTimeOriginal, CreateDate & PreviewDateTime to incorrect timestamp 1984:01:01 12:46:26. - Then I imported the image into digiKam which then records 1984 etc. in its database as expected. - Then I corrected the date to 1916 probably using digiKam for DateTimeOriginal and CreateDate but PreviewDateTime remains as 1984 because digiKam does not use it as you say. The metadata is written to the image but the digiKam database was not updated for some reason. - When I create a copy of the problem image, the database entry is correct 1916. etc. - If I Reread Metadata I get the correct 1916 date in the table view for the original image. I was mistakenly thinking that Refresh did this task. In summary, the database must have gotten out-of-synch with the image metadata but rereading fixes the problem. Problem solved. -- You are receiving this mail because: You are watching all bug changes.
