[Digikam-devel] [Bug 115726] New: Possibility to have more than one digikam folder

[Carsten Schlipf]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=115726         
           Summary: Possibility to have more than one digikam folder
           Product: digikam
           Version: 0.7.4
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: cs yeap de


Version:           0.7.4 (using KDE 3.4.3 Level "b" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15-default

It would be great, if the user could specify multiple digikam root folders, each containing different and/or same albums. If the user launches digikam, it checks, which root folders are available and merges the contents of the albums it finds in these root folders to the albums.

E.g. the user has a root folder (a) ~/photos and another (b) /mnt/server/photos. Folder (a) contains the albums family and holiday containing the pictures:

family
  pic111.jpg
  pic112.jpg
holiday
  pic121.jpg
  pic122.jpg

Folder (b) contains the albums family and conference_trip containing the pictures:

family
  pic211.jpg
  pic212.jpg
conference_trip
  pic231.jpg
  pic232.jpg

If digikam is launched while both folders are available it shows this album structure:

family
  pic111.jpg
  pic112.jpg
  pic211.jpg
  pic212.jpg
holiday
  pic121.jpg
  pic122.jpg
conference_trip
  pic231.jpg
  pic232.jpg

If digikam is launched while folder (b) is not available it just shows the contents of folder (a).

It would also be great if digikam could provide a possibility to transfer the images to other root folders without losing the meta information like tags. E.g. via a context menu like 
Files -> move to -> Location a
                 -> Location b
         copy to -> Location a
                 -> Location b


USE CASE 1:

The user uses digicam mainly from a my notebook and has some images stored on it. However he can't store all images on the rather small notebook harddisk and therefore he stores some on a network folder on a server but he also wants to be able use digikam with all images stored locally when he meets his friends and wants to show his latest pictures.

USE CASE 2:

A small graphic design company needs a photo database, but it should be current and should also be able to access files on notebooks of external workers when they are in the office.

USE CASE 3:

The user stores all his images on his harddisk. After several months he runs out of disk space and buys a new hard disk. Now he has the old images on the old harddisk but wants to store the new images on the new hard disk.