https://bugs.kde.org/show_bug.cgi?id=402379
Bug ID: 402379
Summary: Moving location of RAW file causes loss of metadata
Product: digikam
Version: 6.0.0
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database-Mysql
Assignee: digikam-bugs-n...@kde.org
Reporter: kde.b...@meku.org
Target Milestone: ---
SUMMARY
After upgrading from DK5.9 to DK6.0, moving any RAW file to a new path can
cause loss of metadata.
Tested with DK6.0b3 (20181215)
STEPS TO REPRODUCE
1. Start with DK5.9 or earlier database, with RAW files in database (tested
with CR2 and RAF).
2. Enable metadata setting 'read from sidecar'
3. Disable metadata setting 'write to sidecar'
4. Apply any metadata to RAW, such as caption or tags.
5. Run DK6.0, and using DK6.0 interface move the location of any RAW file or
folder containing files to a new path within the collection.
OBSERVED RESULT
RAW files lose any metadata that is not saved to sidecar and lose any other
features such as groups.
In the database the RAW files at the new path are given new Image IDs even
though their uniqueHash is unchanged - the old Image IDs remain unused.
EXPECTED RESULT
RAW files re-use same Image IDs and keep all metadata and features, even if it
is not saved to sidecar.
ADDITIONAL INFORMATION
When 'read from sidecar' is used the Image records modification date is
collected from the sidecar file, not the RAW itself. If this modification date
does not match to the millisecond then the file does not match and a new Image
ID is created.
Coming from DK5.9 the modification date was stored with second accuracy only,
so the first time any RAW is moved it will trigger this bug.
--
You are receiving this mail because:
You are watching all bug changes.
