[Digikam-users] Batch rename of albums best practice

[Johnny]

sleepless <sleeplessregulus at hetnet.nl> writes:
> If you could elaborate a bit about what happens in each step, it would be a
> great learning experience.
I added some comments to the steps now.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: digikam_rename_albums_workaround.txt
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20110903/e88faabc/attachment.txt>
-------------- next part --------------

> and how to stop the sqlite session? could not think of something else than
> control c.
Try '.exit'.

> I have something similar at hand at the moment, wrestling with the setup from
> virtual box, it refuses to read from existing database.
> I pointed in digikamrc to the place where db exist, in my normal setup db works
> with my pictures in the path /media/FOTO/FOTO/ARCHIEF/
> but it kept stubbornly saying: path FOTO/ARCHIEF/ not found, so it looks like
> it uses a reletive path and doesn know about the base media/FOTO (which is the
> mounted drive called ¨FOTO¨.)
> any ideas?
I don't use any virtual boxes, the only guesses is that the /FOTO folder
is duplicated, although this may of course be correct. 
In digikamrc, try to verify that the correct path is set at all proper
locations, try a 'find and replace' /old/db/name to /new/db/name and
ensure you use absolute paths.

EDIT: It seems digikam edits the digikamrc file when opening
digikam. Therefore it is probably futile to edit this
directly. Exploring the database, there is a table 'albumroots'
containing a field 'identifier' that seems to be the uuid to the disk
and a 'specificPath' identifier that locates the proper folder on that
disk; in your case the FOTO/ARCHIEF part. It seems that for some reason,
the 'identifier' field pointing to the disk is not picked up correctly
when you run digikam from your VM. 

Use the 'sqlite3 /your/digikam.db' and run 'select * from albumroots;'
and you will see your fields. You can take note of the uuid, '.exit'
sqlite3 and 'ls -l /dev/disk/by-uuid' from the shell, look for your
uuid, see which disk it mounts as (e.g. 'sdd7' or similar). If you do
'ls -l /dev/disk/by-label' you can see if this is your drive labelled
'FOTO'. If this is correct, make sure it is mounted. 

If the above works fine from the VM, I think it should work?

-- 
Johnny