[Digikam-devel] [Bug 103201] Wish: easy transport of albums, including tags, comments, etc.

[Thorsten Schnebeck]

------- 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=103201         




------- Additional Comments From thorsten.schnebeck gmx net  2006-04-05 18:56 -------
My 2 Euro cents:

I think the current way to store pictures in a strict album tree while using a database is no longer necessary and I think its a restriction that can be overcome.

Part of the the database should be the path to a picture and a hash ID. The database should be part of ~/.kde/share/apps/digikam/ and not part of an export or backup. Todays harddisks are big enough to store really huge database files or if sqlite failed to do so digikam can also support a "real" sql service

To exchange (this means duplicate) photos between digikam users its fine also to exchange digikams own metadata like Rating, Tags or allocation of CMS infos.
This exchange should be based on embedded metadata like XMP or EXIF. I dont think it is a good idea to squeeze it into limited IPTC structure better create a own tag. Of course this need exellent r/w metadata support. There is hope that exiv2 improves in a nearer future.

One problem is in my concept the integration of photos on removable media. A  photo on a CD,DVD or CF-card on a Linux system can have the same name but different content. That why I think a unique hash value as content ID is necessary to identify those structures.

To speed-up the handling of such a ID structure this maybe leeds to a caching system like digikam already uses for thumbnails. 

Bye

   Thorsten