fix(dates): resolve IFD0 ModifyDate as a last-resort capture date #181

Merged

cameron merged 1 commits from fix/modifydate-fallback into master

2026-10-17 04:10:57 +00:00

Author	SHA1	Message	Date
Cameron CordesandClaude Opus 5.5	5c410b09d9	fix(dates): resolve IFD0 ModifyDate as a last-resort capture date Scans, edited exports and some downloads carry only EXIF DateTime (exiftool: IFD0:ModifyDate). The kamadak ingest path already takes it as the capture date, but the exiftool resolver didn't ask for it, so the date_utc drain resolved those rows to fs_time and then (rightly) refused to overwrite their tag-sourced legacy date. 147 prod rows sat on the legacy convention forever, re-running exiftool every tick. ModifyDate is now the lowest-priority tag, and only from IFD0 — XMP / QuickTime ModifyDate is an edit or mux time, not capture. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-17 00:03:17 -04:00

Author

SHA1

Message

Date

Cameron CordesandClaude Opus 5.5

5c410b09d9

fix(dates): resolve IFD0 ModifyDate as a last-resort capture date

Scans, edited exports and some downloads carry only EXIF DateTime
(exiftool: IFD0:ModifyDate). The kamadak ingest path already takes it
as the capture date, but the exiftool resolver didn't ask for it, so
the date_utc drain resolved those rows to fs_time and then (rightly)
refused to overwrite their tag-sourced legacy date. 147 prod rows sat
on the legacy convention forever, re-running exiftool every tick.

ModifyDate is now the lowest-priority tag, and only from IFD0 — XMP /
QuickTime ModifyDate is an edit or mux time, not capture.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-17 00:03:17 -04:00