problem mirroring pics and database with rsync

[Mark Alford]

I have digikam-0.10.0 in Fedora 10.

I got digikam working on my desktop machine, and I then mirrored
all the picture files and the digikam4.db database file to
a directory (with the same pathname) on my laptop, using rsync.

On my laptop I did digikam -> Settings -> Configure Digikam and made sure that
the directory where the digikam4.db file is located is there in the "database
file path" box.

But if I run digikam on my laptop, I don't see any albums
in the left panel, just "My Albums".
How do I tell it to go and open up that digikam4.db file
and show me the pictures?

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Markus Spring]

See what I experienced some months ago:

Yesterday I exchanged my laptops hd for a higher capacity one and was more than
astonished that my primary collections of images didn't show up any more.

sqlitebrowser to the rescue: after adding another directory on the new disk for
testing purposes I found the differing UID's of the partitions to be the reason
for this behaviour. After exchanging the old for the new UID, the primary
collection was available again.

hope this helps

Markus
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Mark Alford]

Fantastic! Now it works. Many thanks.

It seems to me that hard-wiring the UUID of the partition inside the
database is an unfriendly thing to do. Will this be fixed when bug 175923
is fixed?
Perhaps if digikam finds that the UUID doesn't match the
database pathname it should emit some sort of error message and offer to
update the UUID to match the pathname.



PS: for the benefit of naive users like me, here are the explicit commands to
modify UUID entry in digikam4.db database:

sqlitebrowser digikam4.db
click on "Browse Data" tab
Table should be "AlbumRoots"
under "identifier" double click on "volumeid:..."
modify the UUID value
click on "apply changes"
File -> save changes
File->exit

In Fedora 10 the correct UUID for the
partition can be obtained by looking in /etc/fstab

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Markus Spring a écrit :
> See what I experienced some months ago:
>  
Me too, when i change the pc.
I think that to answer to Mark, he must have a specific database file on
each pc. On the laptop he gives a specific directory for the digikam
database file, and he rsync only images files. The first time he runs
digikam on the laptop, digikam will create the database file using the
metadata which are in the images.

But why to store UUID?



_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Markus Spring]

Mark Alford schrieb:
> It seems to me that hard-wiring the UUID of the partition inside the
> database is an unfriendly thing to do. Will this be fixed when bug 175923
> is fixed?

What you can do is set the 'identifier' field to a url-encoded path like this

volumeid:?path=%2Fhome%2Fspringm%2FBilder

where the field 'specificPath' has the value '/'

This helps in my case that I can have synchronised databases on my laptop and
desktop computer.

My proposal would be to make this behavior the default instead of using the UUID

Markus

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Mark Alford]

On Thu, 14 May 2009, Markus Spring wrote:
> What you can do is set the 'identifier' field to a url-encoded path like this
> volumeid:?path=%2Fhome%2Fspringm%2FBilder
> where the field 'specificPath' has the value '/'

OK, that is an elegant solution in the current version of digikam.

I would like to suggest to the developers that they make digikam friendly to
people like us who mirror/synchronize their photo collections on different
computers. For example:

1) Allow the user to manipulate the volumeid and the specific path fields
from within digikam itself (under "Settings" presumably), so we can "help"
digikan to find our photos

2) Emit some kind of warning if the volumeid in the database can't be found
and even offer to change it to one of the existing volume ids.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

On Thursday 14 May 2009 18:10:52 Michel Pottier wrote:

> But why to store UUID?

To identify remote collections.

m.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Markus Spring]

Mikolaj Machowski schrieb:
>> But why to store UUID?
> To identify remote collections.
For this purpose it is valuable. The problem arises from the fact that it is
used as default and cannot easily be influenced by the user

Markus
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users