Bug 376020

Summary:	Moving of photos within the fuzzy search corrupts database
Product:	[Applications] digikam	Reporter:	PaulK <PaulKerner>
Component:	Database-Similarity	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, mario.frank, metzpinguin
Priority:	NOR
Version:	5.5.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:	https://commits.kde.org/digikam/c000a498d1776a5242206915773c41497786fafe	Version Fixed In:	5.5.0
Sentry Crash Report:

Description PaulK 2017-02-04 23:05:44 UTC

I execute a fuzzy search to find duplicate photos. Photos are correctly identified and shown in the result list. As the photos are in different folders they are shown accordingly in the result list which is grouped by folder.

When I drag a photo onto the other to group them the GUI shows a correct execution with the group icon. However, in the folders view the moved photo is neither in the original nor in the destination folder though the counter of the original folder is counting the photo. It seems that in the database the photo has been moved but not in the file system. On linux level the photo is still in the original folder.

Comment 1 Maik Qualmann 2017-02-05 11:35:17 UTC

This behavior is actually correct. Grouped images are not moved but are only linked in virtual form, the images remain in their original folders.

Maik

Comment 2 Mario Frank 2017-02-07 14:48:33 UTC

Paul,
I second Maik. If you would move the image into the other folder, the image would really be moved and vanish from source folder. Grouping is just an image relation that is established.

This seems to me as a feature request in the way: Add option to group an image to another image and move it to the same folder.

Is this what you expect?

Comment 3 Mario Frank 2017-02-28 13:05:24 UTC

Git commit f58fc11f651c84cae37a758a40ec18be1229b8b1 by Mario Frank.
Committed on 28/02/2017 at 13:02.
Pushed by mfrank into branch 'master'.

Added an option in context menu to group an image with another one and move it to the album of the target image at the same time.
Though the problem described in 376020 is no bug, I think this use-case can save users some work.
FIXED-IN: 5.5.0

M  +2    -1    NEWS
M  +26   -2    app/dragdrop/imagedragdrop.cpp

https://commits.kde.org/digikam/f58fc11f651c84cae37a758a40ec18be1229b8b1

Comment 4 Mario Frank 2017-02-28 14:47:06 UTC

Git commit c000a498d1776a5242206915773c41497786fafe by Mario Frank.
Committed on 28/02/2017 at 14:44.
Pushed by mfrank into branch 'master'.

If two root albums have the same name in file system, they are not distinguishable as for both albums the header states Albums/albumnane.
But since all albums have a label, this one is better suited as albumname as the user specifies the album himself.
FIXED-IN: 5.5.0

M  +2    -1    NEWS
M  +6    -1    libs/album/album.cpp
M  +13   -12   libs/album/album.h
M  +13   -0    libs/database/collection/collectionmanager.cpp
M  +6    -0    libs/database/collection/collectionmanager.h

https://commits.kde.org/digikam/c000a498d1776a5242206915773c41497786fafe