My Idea is simple but fundamental: 1 Add the possibility to have multiple Databases - like one for every "collection" 2. By default have the database stored in the root directory of the collection (hidden) 3. keep a list of collections that can be switched on and off 4. Make the path of the db customizable for every collection - 5. and make it possible for multiple collections to share one db This would give a whole new sense to the word collection and enhance export-possibilities without changing a lot in digikams main behaviour. I could have small and big collections. Switch them on and off and have digikam start fast very fast if I'm interested in only a small part of my library. My List of Tags would be shorter as they would be collection-specific I could prepare collections that are just big enough to fit on a DVD and copy them by copying the folder. On another computer I could add the collection temporarily to show my photos and leave no traces (maybe a line) when i eject the DVD With 5.) It would be easy to make the default settings backward-compatible. I asume the advantage of having the database in a certain space is that you can locate it somewhere, where it's always and rapidly accessible. So the default setting for network-sources could still be to have the db stored locally. There could even be an "open with digikam" option for folders in the filemanager and digikam would open only the collection that contains that folder or ask if you want to start a collection with this one if there's no collection containing that folder. short: it's GrEaT i think! I'm using digikam 3.3 on Ubuntu 12.04 so I'd love to hear if this was alrdy implemented in 4.0 Greets :]
*** Bug 269993 has been marked as a duplicate of this bug. ***
I'm linking here to #125474 because the possiblity to merge databases seems a much-wanted feature and it's something that could be done in the same process with the idea proposed here. Greets
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
As you ask so kindly I will gladly do that. And it works okay for me. But in terms of easy Export i'd still really love it if Tags were possible to be marked as "private" so they wont be exported/saved into the file. (unlike discussed here they dont need to be separated by that property https://bugs.kde.org/show_bug.cgi?id=338048) THX and Greetings :)