<div dir="auto">I add my comments to the wish report but we would like to get some answers to understand what is necessary to make it happen <div dir="auto"><br></div><div dir="auto">Thx<br><br><div data-smartmail="gmail_signature" dir="auto">Sent from a fair mobile </div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, 1 Dec 2018, 22:46 Stefan Mueller <<a href="mailto:stefan.mueller.83@gmail.com">stefan.mueller.83@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Great 😊<br><br><div data-smartmail="gmail_signature">Sent from a fair mobile </div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, 1 Dec 2018, 21:53 <<a href="mailto:digikam@911networks.com" target="_blank" rel="noreferrer">digikam@911networks.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Done:<br>
<br>
<a href="https://bugs.kde.org/show_bug.cgi?id=401622" rel="noreferrer noreferrer noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=401622</a><br>
<br>
sknahT<br>
<br>
vyS<br>
<br>
<br>
On Sat, 1 Dec 2018 09:43:19 +0100<br>
Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" rel="noreferrer noreferrer" target="_blank">caulier.gilles@gmail.com</a>> wrote:<br>
<br>
> The mailing list is not the right place to propose technical<br>
> solution to this problem.<br>
> <br>
> In the long time, mailing list contents is dissolved.<br>
> <br>
> Please use bugzilla instead. We have a dedicated session for this<br>
> topic, with many entries talking around multi-users support :<br>
> <br>
> <a href="https://bugs.kde.org/buglist.cgi?bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bug_severity=wishlist&bug_severity=task&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Database-Multiusers&product=digikam&query_format=advanced" rel="noreferrer noreferrer noreferrer" target="_blank">https://bugs.kde.org/buglist.cgi?bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bug_severity=wishlist&bug_severity=task&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Database-Multiusers&product=digikam&query_format=advanced</a><br>
> <br>
> Note : we use bugzilla to explain the future project to students.<br>
> All the project story is here. It's very important.<br>
> <br>
> Thanks in advance<br>
> <br>
> Gilles Caulier<br>
> <br>
> <br>
> <br>
> <br>
> Le ven. 30 nov. 2018 à 23:03, <<a href="mailto:digikam@911networks.com" rel="noreferrer noreferrer" target="_blank">digikam@911networks.com</a>> a écrit :<br>
> <br>
> > On Fri, 30 Nov 2018 20:14:20 +0100<br>
> > Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" rel="noreferrer noreferrer" target="_blank">caulier.gilles@gmail.com</a>> wrote:<br>
> > <br>
> > > Hi,<br>
> > ><br>
> > > The multi users setup require severals works in digiKam database<br>
> > > interface.<br>
> > ><br>
> > > Outside the fact that you need to use a remote Mysql Database,<br>
> > > this needs a lock mechanism to prevent concurrents access to the<br>
> > > contents. Of course this want mean a to share the same database<br>
> > > contents (collection) between users.<br>
> > ><br>
> > > A first approach is to work like shared document between Words<br>
> > > we users can change contents. A lock mechanism is done to open<br>
> > > document in RW for the first people, and in Read only for all<br>
> > > others. This less powerful but this simplify the workflow to<br>
> > > manage. A versionning system is also required in this<br>
> > > configuration.<br>
> > ><br>
> > > They are some files already open in bugzilla about this topic.<br>
> > > We will need to found a new student to work on this project next<br>
> > > summer. <br>
> ><br>
> > If you could add to each table:<br>
> ><br>
> > * owner_id , it could be digikam until a later time that it<br>
> > could/would be upgraded to actual users<br>
> > * group_id, it could be digikam until a later time that it<br>
> > could/would be upgraded to actual groups<br>
> > * location, it could be null until used<br>
> > * date & time of last add/edit<br>
> ><br>
> > Then most of the multi-user stuff could be done by mysql/mariadb:<br>
> > the record locking, the reads, the writes...<br>
> ><br>
> > Then as you dedicate more resources, things could be integrated<br>
> > within DK at later time to make it more transparent.<br>
> ><br>
> > sknahT<br>
> ><br>
> > vyS<br>
> > <br>
> > ><br>
> > > Best<br>
> > ><br>
> > > Gilles Caulier<br>
> > ><br>
> > > Le ven. 30 nov. 2018 à 09:30, Stefan Müller<br>
> > > <<a href="mailto:stefan.mueller.83@gmail.com" rel="noreferrer noreferrer" target="_blank">stefan.mueller.83@gmail.com</a>> a écrit :<br>
> > > <br>
> > > > Good morning Leo,<br>
> > > ><br>
> > > > I'm gonna face the same problem, so I mentioned in<br>
> > > > [digiKam-users] Use digiKam with a NAS and MariaDB<br>
> > > > < <br>
> > <a href="http://digikam.1695700.n4.nabble.com/digiKam-users-Use-digiKam-with-a-NAS-and-MariaDB-tp4707031p4707346.html" rel="noreferrer noreferrer noreferrer" target="_blank">http://digikam.1695700.n4.nabble.com/digiKam-users-Use-digiKam-with-a-NAS-and-MariaDB-tp4707031p4707346.html</a> <br>
> > >, <br>
> > > > where it is a bit off-topic.<br>
> > > ><br>
> > > > I haven't got the chance yet to pursue that topic. That could<br>
> > > > be just the right place.<br>
> > > ><br>
> > > > I'm wondering if the new plug-in model would allow to<br>
> > > ><br>
> > > > - intervene SQL queries to an NAS based database<br>
> > > > - do authentication against e.g. an LDAP server<br>
> > > ><br>
> > > > stefan<br>
> > > > Am 30.11.2018 um 02:02 schrieb Leo Gaspard:<br>
> > > ><br>
> > > > Hello world!<br>
> > > ><br>
> > > > I have tried IRC to bother the fewest possible people, but it<br>
> > > > looks like #<a href="mailto:digikam@irc.freenode.net" rel="noreferrer noreferrer" target="_blank">digikam@irc.freenode.net</a> is dead, so let's try<br>
> > > > here. Sorry for the noise! (Note: I am not subscribed to the<br>
> > > > list, can you please keep me in the Cc: list?)<br>
> > > ><br>
> > > > I am considering using digiKam, but as my use case is kind of<br>
> > > > peculiar, I thought I would first ask whether you think I have<br>
> > > > chances of succeeding at what I'm trying to do.<br>
> > > ><br>
> > > > Context: I'm trying to setup a shared photo database with my<br>
> > > > family for all our photographs. Photos will be shared over<br>
> > > > NextCloud, and hopefully digiKam would be used to both tag<br>
> > > > them and synchronize the tags. Now, the photo database is<br>
> > > > kind of huge, and not all computers are able to download it<br>
> > > > in full. In addition, not everyone has the same taste for<br>
> > > > photos, so I think it'd be better if everyone only had write<br>
> > > > access to their own directory, and read access to others'.<br>
> > > ><br>
> > > > My currently imagined solution:<br>
> > > > * Each user puts their pictures in their write-for-them<br>
> > > > read-for-all folder in Nextcloud<br>
> > > > * Everyone runs a digiKam instances. Tags are synchronized<br>
> > > > either through MySQL or by just adding the SQLite database to<br>
> > > > the Nextcloud<br>
> > > > * digiKam is setup to directly fetch the photos from WebDAV<br>
> > > > from the Nextcloud instance<br>
> > > ><br>
> > > > So my questions are:<br>
> > > > 1. Do you have advice on whether to pick MySQL or<br>
> > > > synchronize the SQLite database over Nextcloud? (I will have<br>
> > > > linux, windows and mac clients)<br>
> > > > 2. Does digiKam handle well-enough collections on read-only<br>
> > > > folders? 3. What do you think about the overall idea?<br>
> > > > 4. Bonus question: Ideally users could also have their own<br>
> > > > private databases that are not shared. Does digiKam handles<br>
> > > > properly switching between two databases, ideally with one<br>
> > > > that includes the other?<br>
> > > > 5. Trick question: If an answer is no, is there any project<br>
> > > > other than digiKam that could handle these requirements and<br>
> > > > that you would know about?<br>
> > > ><br>
> > > > I've searched a bit the manual and didn't find much about<br>
> > > > these questions, and I must say I'd rather request an opinion<br>
> > > > from someone knowledgeable before starting the setup, that<br>
> > > > will likely be kind of long and complex, especially if done<br>
> > > > with MySQL. Sorry if the questions are already answered<br>
> > > > someplace I didn't find!<br>
> > > ><br>
> > > > Cheers, and thank you for digiKam that looks like some nice<br>
> > > > piece of software!<br>
> > > > Leo<br>
> > > ><br>
> > > > <br>
> ><br>
> ><br>
> > --<br>
> > sknahT<br>
> ><br>
> > vyS<br>
> > <br>
<br>
<br>
-- <br>
sknahT<br>
<br>
vyS<br>
</blockquote></div>
</blockquote></div>