https://bugs.kde.org/show_bug.cgi?id=499616

--- Comment #6 from Michael Miller <michael_mil...@msn.com> ---
> Hi Mike
> 
> One reason is the work on different projects. It's important for me to
> separate the projects to prevent from mixed data.
> As examples:
> Face recognization data must not cross the projects boundaries.
> Also different projects may have the same tags, but on a search only tags of
> a specific project have to be used.
> Checking for similarities must not cross the the projects boundaries.
> 
> One thing is the work on image libraries of different clients ... it's
> almost like that.
> Im working on image libraries of my wife, on my own photo libraries, on a
> stable diffusion image library and on some voluntary web-projects. So I've
> got different sources - my own with a large amount of pictures on different
> local drives, the others on USB-drives or on the network with more or less
> speed (between 20MB/s and 1GB/s).

Hi Daniel,
Thanks. I think I understand why you want to unload the collection to get
segmentation between projects.  

One idea is to use different DBs for each collection.  Instead of re-using the
same digiKam DB, SQLite makes it easy to have multiple DBs.  This would
eliminate the need to rescan the collection whenever you swapped them.  You
could create a "digiKamDB" folder on your local drive, and then create
subfolders for each instance of the digiKam DBs that correspond to a
collection.  You could also create DBs on the same media as the collection, but
performance may suffer depending on the speed of the media.

In Preferences->Database you can select a different digiKam DB.  Keep in mind
that if you use SQLite, you'll need to store the DBs in different folders for
each collection.

To swap DBs, you would select a new database in Preferences->Database, and then
restart digiKam.  I know it's not an ideal solution, but it's something you can
do now while the rest of the team and I consider better options. It will
definitely be faster than rescanning large collections, and it will give you
the collection segmentation you're looking for.  One caveat is that when you
remount the removable storage it needs to be in exactly the same path it was
before.

Cheers,
Mike

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to