Handling of Picture Date in Library files
As I was resetting my installation I thought it would be efficient to re-use the previously created libraries to feed my newinstallation (Batch import through CLI).
Unfortunately I noticed that the library didn't keep the orignal picture date information.
While the original import worked, the new one used the "last modified" date, thereby redating 25% of my pictures (older files and Whatsapp saves) to yesterday.
eg. a picture of November 2019
Original file:
/volume1/Famille/Photos/valerie/2019/2019-11/4c4f9182-2a93-4f26-823c-e56660a45924.jpg
Nicely processed the first time to:
/library/929bfd93-4e28-890c-9dbdb4078edc/2019/2019-11/4c4f9182-2a93-4f26-823c-e56660a45924.jpg
After import of that library file in new Immich instance, it became:
/library/b2611dfa-39c4-78b7673f4aab/2023/2023-04/4c4f9182-2a93-4f26-823c-e56660a45924.jpg
And is displayed under April 29, 2023 😦
Something to be done about this?
PS: I changed the Immich settings not to create a subfolder per day, that's requested behaviour.4 Replies
It uses the last modified date initially, after it processes the picture it should change to the correct date
I think that my issue is that the original picture didn't have a timetag in the file. The original modified date was still correct but the "immich modified date" wasn't anymore.
Not sure if I can check that theory somehow
If you run exiftool on the image you can see what's in the exif data
Indeed exiftool shows 000000 as original date
I have indeed the problem with 2 cases:
- Old pictures where the dates are 'wrong'
[IFD0] ModifyDate : 0000:00:00 00:00:00
[ExifIFD] DateTimeOriginal : 0000:00:00 00:00:00
[ExifIFD] CreateDate : 0000:00:00 00:00:00
- Recent Whatsapp receptions where there is no exif date
In both cases, Immich uses the last modifed to process the picture, but modifies the last modify (without registering exif info)