https://bugs.kde.org/show_bug.cgi?id=479182
--- Comment #3 from Ritesh Raj Sarraf <kde-b...@researchut.com> --- (In reply to Maik Qualmann from comment #2) > What is a “remote storage” to you, an FTP/HTTP server? Or a mounted SMB > share? You can add images of a mounted SMB share using “Add images” via the > import tool. > > Maik That's exactly what my current setup is like. My Pictures collection is on a remote SMB storage with 2 different ROOTS * Main * TO_ENCODE Main holds all the images. TO_ENCODE is where I dump all my images, filter/classify, and then import into Main. Both Collection ROOTS are smb mounted from the very same Samba server. When I import via the Camera Devices interface, I get the nice UI to organize. TO_ENCODE is emulated as Camera Device. And so, when I import to Main, I get the nice organize window. To downside is that, even though both the remote storages are on the very same samba server, the imports are inefficiently done over the network. Note: Both the collections are marked "Remote Storage", though I'm not sure if DigiKam really treats it any different than local storage. I was only testing the `Import from remote storage` feature, with the wishful hope that it would overcome the inefficient performance I've explained above. And in doing that I noticed this anomaly. I believe you could have consistency about imports, providing the same feature for all Import types, whether Camera Device and/or Remote Storage. -- You are receiving this mail because: You are watching all bug changes.
