Bug 441741

Summary:	Refresh won't import subfolders created by other software
Product:	[Applications] digikam	Reporter:	Steve Franks <stevef48>
Component:	Albums-TreeView	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	7.3.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:	7.4.0
Sentry Crash Report:

Description Steve Franks 2021-08-30 07:31:50 UTC

SUMMARY
I use years and months to organise my photos. i.e. 2021, contains 2021-01, 2021-02, 2021-03, etc. folders
I installed Digikam under Lubuntu on one of my PCs and it correctly imported my data, this morning I copied the Digikam files to my Windows Laptop, which has more data on it. When I refresh 2021, nothing happens - the process doesn't find the new folders for 2021-07 and 2021-08.
Importing those folders fails, because they are subfolders of 2021 which is already in the album.
STEPS TO REPRODUCE
1. 
Copy Digikam files to new PC
2. 
Create a new folder, containing photos using different software. I used iMatch, but I don't thinks that is the cause of this bug.
3. 
Refresh all ablbums, or the immediate parent of the folder you created. Digikam displays Thumbs and New Items progress bars.
When the bars close no new items are shown in the album tree.
OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 caulier.gilles 2021-08-30 09:25:50 UTC

Why did you close this file as not a bug without comment ?

Comment 2 Steve Franks 2021-09-01 15:46:09 UTC

(In reply to caulier.gilles from comment #1)
> Why did you close this file as not a bug without comment ?

I remembered that the original D: drive is external the laptop has internal D: drive. The volume IDs are different. I used Heidi SQL to change the volume type and ID, but still had to wait for a long time whilst didgikam scanned 160k files.
However, I'm still struggling to persuade digikam to use that data. It read the data, but then overwrote all my hard work removing old metadata when I chose the option to read/write sidecars.
If I selected to only write sidecars none of my RAW and video files had tags. 
The only possible bug is that digikam doesn't warn that the external drive is not attached.

Comment 3 Maik Qualmann 2021-09-01 20:31:48 UTC

You do not need to change the volume IDs manually because digiKam has now built in a function for this, see bug 441749. The change was also incorrect because digiKam scanned the collection again. The database is no longer usable, I hope you have one backup.

Maik