https://bugs.kde.org/show_bug.cgi?id=441749
Bug ID: 441749
Summary: Method to relocate data
Product: digikam
Version: 7.3.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Database-Maintenance
Assignee: digikam-bugs-n...@kde.org
Reporter: steve...@gmail.com
Target Milestone: ---
SUMMARY
I moved Digikam database from Lubuntu to Windows. Lubutu phots are on
removeable disk, Windows Internal disk.
I can't see a method in Configuration, or Database Maintenance, to easily
change albums to the internal disk.
STEPS TO REPRODUCE
1.
Add an album from removeable media
2.
Copy Data to folders on an internal disk
3.
Configure Digikam to use the folders on the internal disk
OBSERVED RESULT
Digikam will add a new album for the internal disk, even though the folders
have the same structure and contain copies of the same files.
EXPECTED RESULT
A single album containing the original data, referring to the files on the
target disk.
MY WORKAROUND
After digikam created the album for the internal disk I ended it. I then
modified the digikam.db file using Heidi SQL:-
a) Opened the albums table
b) Copied the internal disk volume id (to the clipboard)
c) deleted the internal disk album reord from the albums table
d) Pasted the volume id into the removeable disk data and changed that disk
from type 2 to type 1
e) Restarted digikam.
digikam then scanned the collections, unfortunately that is taking about the
same time as if I had just created a new database from scratch.
SOFTWARE/OS VERSIONS
Windows: 11
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
I would like digikam to own its data. ie If the database data differs from the
metadata in an image, the digikam data should take preference even if the file
modified date is earlier.
Some people may disagree, so it would be nice if there was a switch to allow me
to tell digikam to overwrite metadata on disk, or use it to update its database
--
You are receiving this mail because:
You are watching all bug changes.
