I have a main folder with source images. I have different subfolders (sub collections) with output images. The thumbnail view offers the possibility to see similar images (source and outputs) together (View/Include Album Sub-tree). OK. I can group these images. Perfect. But when I look at a subfolder from which some images have been grouped to images in another (sub)folder these images do not appear anymore. This is like I had moved these images from their original (sub)folder to another. In that case the grouping is OK. But I should always see my images in their original folder (or collection).
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier
@Philippe digiKam 8.0.0 is out. This problem still valid with this release ? Best regards Gilles Caulier
Philippe, What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Note: bundle is now based on Qt 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier
Philippe, any feedback here ?
Maik, What's about this file ? Grouping do not move files physically on the disk. It's only a junction between items on the database. Right ? Gilles
Yes, that's correct. This is also the problem: if images from a group are moved manually to other albums, they will no longer be displayed because the group is closed and the leader is somewhere else. Therefore, there's a function in the album context menu to repair hidden items. So, if the leader and the sub-items are in different albums, the group will then be dissolved. Maik
Hi Maik, If the files are moved within digiKam, the database must change safety the group hierarchy. I can understand that it's not yet possible if the move is done outside digiKam. In fact the file checksum used as UUID must be used to link file in the group. If the UUID is store in the digiKam XMP namespace, we will able probably to backup groups in the metadata and solve this issue : https://bugs.kde.org/show_bug.cgi?id=460064 Gilles