https://bugs.kde.org/show_bug.cgi?id=416994
Bug ID: 416994
Summary: Unexpected handling of DateTimeOriginal and
DateTimeDigitized
Product: digikam
Version: 7.0.0
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: Metadata-Date
Assignee: digikam-bugs-n...@kde.org
Reporter: john...@downclimb.com
Target Milestone: ---
SUMMARY
I have scanned images in which Exif.Image.DateTime is set by the scanner to be
the time of scanning. I use Exiv2 commands to manually copy that to
Exif.Photo.DateTimeDigitized and also to set the original capture time in
Exif.Photo.DateTimeOriginal. It looks like this:
$ exiv2 -pt -g DateTime rj_20040709_063.jpg
Exif.Image.DateTime Ascii 20 2015:10:11 13:40:12
Exif.Photo.DateTimeOriginal Ascii 20 2004:07:09 00:00:17
Exif.Photo.DateTimeDigitized Ascii 20 2015:10:11 13:40:12
When the image is loaded into DigiKam, all seems fine. The Exif tab of the
metadata panel correctly shows both the Original and Digitized dates under the
photograph information. However, if I choose Item->Write Metadata to File (I'm
writing to sidecars only), then the photograph information shows the Original
date for *both* DateTimeOriginal and DateTimeDigitized.
If I configure Digikam metadata so that timestamps are not written to the
metadata, this behavior does not happen.
STEPS TO REPRODUCE
1. Configure DK metadata to write timestamps to metadata (I believe this is the
default)
2. Add an image to DK that has different times for Exif.Photo.DateTimeOriginal
and Exif.Photo.DateTimeDigitized
3. Perform the action Item->Write Metadata to File
4. See that the photograph information in the Exif tab of the metadata panel
shows the original date for both "Date and Time (digitized)" and "Date and Time
(original)"
OBSERVED RESULT
The digitized time is mistakenly overwritten by the original time.
EXPECTED RESULT
The digitized time should not be overwritten by the original time.
SOFTWARE/OS VERSIONS
Using the digikam-7.0.0-beta2-1-x86-64 AppImage on Pop OS! 19.10.
ADDITIONAL INFORMATION
This is annoying for those of us who obsess over metadata of scanned photos,
but since it may not matter for digital photos where original and digitized is
the same, and it seems that turning off timestamps in the metadata settings
avoids the problem, this is probably a minor bug.
--
You are receiving this mail because:
You are watching all bug changes.
