Digikam XMP schema ?

[tosca]

Less than 15% of my pictures are online, and for them I keep the tags to minimum: http://www.marie-noelle-augendre.com/photos/tags.php
But I need a much more complete tags organization to manage many more pictures locally in Digikam.

Marie-Noëlle

2013/2/17 jdd <[hidden email]>

but I use mostly tags from piwigo online

http://dodin.org/piwigo/tags.php

jdd

--


Mes dernières photos sont dans ma galerie.
Connaissez-vous Image Fixe, le photo-club de Saint Jean du Gard ?
Et parcourez les Cévennes à ma façon avec Cévennes Plurielles,

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

[tosca]

Thanks for the detailed procedure: it might be handy, especially as it can be used as often as necessary.

Marie-Noëlle

2013/2/17 Jean-François Rabasse <[hidden email]>

Not to be nervous, I took the habit to do that on a copy of database,
and I/O access to the SQLite file can be enhanced when using a ramdisk.
Linux supports that very well, so :
 - backup /.../digikam4.db to ... digikam3.db.backup
 - copy the file to ramdisk, /dev/shm/digikam4.db
 - start DK with option : --database-directory /dev/shm
 - work...
 - when all is ok, satisfying results, no corruptions, no crashes, copy
   the ramdisk file back to original place /.../digikam4.db
   (Before shutting down the computer:-)
In case of problem, just forget, nothing is lost.

Regards,
Jean-François

 

--


Mes dernières photos sont dans ma galerie.
Connaissez-vous Image Fixe, le photo-club de Saint Jean du Gard ?
Et parcourez les Cévennes à ma façon avec Cévennes Plurielles,

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

[Martin (KDE)]

Am 17.02.2013 11:56, schrieb Jean-François Rabasse:

>
> For large operations (folders reorganisation, rereading metadata for many
> images, etc.) it's slow and I also happened to have problems, crashes or
> so. Not to be nervous, I took the habit to do that on a copy of database,
> and I/O access to the SQLite file can be enhanced when using a ramdisk.
> Linux supports that very well, so :
>  - backup /.../digikam4.db to ... digikam3.db.backup
>  - copy the file to ramdisk, /dev/shm/digikam4.db
>  - start DK with option : --database-directory /dev/shm
>  - work...
>  - when all is ok, satisfying results, no corruptions, no crashes, copy
>    the ramdisk file back to original place /.../digikam4.db
>    (Before shutting down the computer:-)
> In case of problem, just forget, nothing is lost.

The main problem with this: you have to do to much by hand. While this
is no problem for me, it is for my other users.

I have a simmilar setup but automated. I use shared computers so it is
more general - I copy my home folder from server to client at login and
back to the server at logout. Most clients use SSDs, so shared memory is
not that much faster. The server has a daily backup, so the risk to
crash my DB and loose everything is low.

The shared system is the reason I still use sqlite. Wireless clients
sometimes loose the connection (so digikam will fail with a centralized
DB server). An I want to use digikam with the local photos without even
been connected to my network.

Martin

>
> Regards,
> Jean-François
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

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