[Digikam-users] Batch rename of albums best practice

[sleepless]

Hi Johnny,
Thanks for the explanations, it has been very informative and I am 
looking forward to your next contribution to the list.


For your information.
Don´t bother to much about it I am just playing around to see what I can 
do and to have some great answers around if someone asks. No important 
matters involved here.

One internal and one external drive has been correctly mounted. They are 
visible in nautilus I can move my files but not copy!??

ls by uuid works correct

ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 2011-09-03 20:33 
2647858c-17ed-4300-a47f-5bba897ba931 -> ../../sda5
lrwxrwxrwx 1 root root 10 2011-09-03 20:33 
3f9a4cff-e816-4fd3-837c-d7354a742235 -> ../../sda1


  ls by label does not. In my dayly setup it works, but not in the VM

ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 9 2011-09-03 20:33 VBOXADDITIONS_4.1.2_73507 -> 
../../sr0
jansen at jansen-VirtualBox:~$

there is definitly something wrong, but what...

Best regards,
Rinus


Op 03-09-11 16:52, Johnny schreef:
> 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.
>
>
>
>> 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?
>
>
>
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20110903/9f042897/attachment.html>