[Digikam-devel] [Bug 236730] Collection path is interpreted differently

[dotCOMmie]

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





--- Comment #5 from dotCOMmie <bugs dotcommie net>  2010-05-18 16:10:55 ---
On 05/18/2010 08:39 AM, Marcel Wiesweg wrote:
> https://bugs.kde.org/show_bug.cgi?id=236730
>
>
>
>
>
> --- Comment #4 from Marcel Wiesweg<marcel wiesweg gmx de>   2010-05-18 14:39:39 ---
> Before I see a partition with the UUID f9ac797c-1967-4036-939e-af81366e0e3e
> and now there is one 8d105535-4ef2-4f44-8c45-7cb245fe8167.
>
> The question is which one is correct and in how far your partition layout
> changed.

I have 2 disk partitions home and root.
9aea5987... is sda3
f9ac797c... is crypt_LUKS of sda3 which is /home/USERNAME
8d105535... is sda1 the root partition.

This partition layout has not changed in several years. The question is how did 
digikam work before with specificPath of /media/Pictures was it taking this 
relative to the mount point?

>
> To make it work for you, I recommend to take the old database and only change
> identifier and specificPath manually.
>

That is what I did.

Now the question from all of this. Digikam does not have a way of editing the 
collections only adding new ones and removing old ones. If digikam had this 
feature there would not be a need to dabble with the DB to fix this issue. This 
would be of particular interest for less experienced users.

Further more there seems to be dependance between image metadata (comments, 
rating & etc) and the album. If an album were to break (say recovering from
dead 
disk) there does not seem to be a trivial way of rebuilding this short of 
manually hacking away at the Album roots table. This seems like a great way for 
a user to loose important data. It would be nice for digikam on creation of a 
new album to check for image hashes and compare them to the existing ones (in 
DB) and relink meta-data based on hashes.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.