<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">I thought the author wanted to cache images from NAS to a laptop while on LAN then work on the cached images while on a road and then sync the changes back to NAS when back home.</div><div dir="auto"><br></div><div dir="auto">It is a brilliant idea but I don't think digiKam can do that.</div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000" dir="auto"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Sveinn í Felli <sv1@fellsnet.is> </div><div>Date: 2019-09-19 3:32 a.m. (GMT-07:00) </div><div>To: digikam-users@kde.org </div><div>Subject: Re: [digiKam-users] Sharing Database/Collections </div><div><br></div></div>Þann 19.9.2019 08:49, skrifaði Martin Burnicki:<br>> Andrey Goreev wrote:<br>>> I do not think digiKam can do that...<br>> <br>> Shouldn't this work if the collection is in a cloud folder like<br>> Nextcloud (or Dropbox, FWIW)?<br>> <br>> If you make changes to photo or an album (i.e. just the file or photo)<br>> on one machine then the changes are synchronized to all machines that<br>> share these folders, and if you start DK next time it will detect the<br>> changes and update the local database accordingly.<br>> <br>> But of course this is only going to work if you write tags and other<br>> metadata to the image file or a sidecar file.<br>> <br>> If you have configured DK to *not* write metadata (tags etc.) to the<br>> files but keep them only in the DB you'd have to synchronize the<br>> database in a consistent way, which can be much harder.<br>> <br><br>IMHO it could be instructive to set up Nextcloud on a NAS over a LAN, <br>and try out how Digikam reacts to such synchronization - both databases <br>and image files. Probably I will test this kind of a setup, but not <br>until late October when time permits.<br><br>Nextcloud/OwnCloud has fine-grained access-controls for users/groups and <br>sharing, and has pretty advanced mechanisms for resolving conflicts in <br>case of simultaneous edits.<br><br>I presume that if using a synchronized database one would have to share <br>_all_ the files in each local collection _and_ the paths would have to <br>be the same on all devices, right?<br><br>Anything else obvious?<br><br>Best regards,<br>Sveinn í Felli<br></body></html>