Bug 431096

Summary: Adding new collection scans all existing collections for new items
Product: [Applications] digikam Reporter: S. Burmeister <sven.burmeister>
Component: Database-ScanAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: minor CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 7.1.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In: 7.5.0
Sentry Crash Report:

Description S. Burmeister 2021-01-03 09:36:42 UTC 
SUMMARY
If one adds a new (network) collection, digikam scans all (network [I only have network collections]) collections for new items before actually adding the new (network) collection to the albums view.

STEPS TO REPRODUCE
1. Have a large (network) collection (to make the effect visible)
2. Add a new (network) collection (in my case the first letter of the collection foldername is further in the alphabet compared to the existing collection, i.e. existing: Axxxxx, new Bxxxx, if that matters)
3. Check the scanning process and the albums view

OBSERVED RESULT
Looking at the logs of the server, digikam starts to scan the already existing collection Axxx.
The new collection does not appear in the albums view until digikam has finished scanning the "old" collection Axxx and starts scanning the new collection Bxxx. In my case it takes literally ours scanning the "old" collection which made me think that digikam is stuck when adding a new network collection, since the scanning process remained at 0% for more than 10 minutes.

EXPECTED RESULT
Only scan for new items in the newly added collection.

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
I set this bug to minor since digikam works and one does not add new collections every day. However, for people with large network collections this is a pretty time consuming/major bug.

If it matters:the network collections are on the same network drive (Z:), but ecist in different folders. The network drive is a Windows webdav network drive that points to a Nextcloud server.
Comment 1 Maik Qualmann 2021-01-03 10:51:12 UTC 
Yes, this behavior is by design. There is also the possibility that you have changed or deleted another collection, new name, new collection type. A full scan is necessary to have a clean state. Sorry, 10 minutes are completely unacceptable for a scan. I would consider a different connection for the network drives. I have already experimented with a kind of folder cache when scanning, but the gain on my network drives was very small. I will add it for testing after the digiKam-7.2.0 release.

Maik
Comment 2 S. Burmeister 2021-01-03 15:46:24 UTC 
A full scan "just in case" will always do the job, that's correct. I just hoped for a smarter solution which only acts on activities necessary instead of "just in case let's do everything".

And I do still  think it is irritating for the user that although the collection was added in the settings, it does not appear instantly (empty) in the albums view.Even if it only takes a minute, I would expect to see the collection instantly.

Feel free to close the bug, as I said it is "minor" if one knows how digikam works and that one just has to wait for the whole scan to finish.