[digiKam-users] digikam as client server and mixed OS installation

[ccabek]

Hi,

I'm testing digikam for my family pictures. I hope someone has some hints
for me, how to set this up.

I run an ubuntu server with samba to share my pictures for my PC, my wife’s
notebook and also for streaming to our TV via DLNA. The PC and notebook use
Win10.
A lot of pictures are made with our mobiles and transferred via dropbox and
some self written scripts directly into my samba share. The second main
source is our camera.
I configured the albumroot with && for using linux and windows path. This
works, but I see some challenges.

*Desktop dependencies*
The dependencies to kde forces me to install a desktop environment and i
have to start x server to run digikam. The next step is actually done
manually (update album, face recognition). This is not good. I am looking
for a digikam backend without desktop dependencies where I can start cron
jobs to update the database. The features in maintenance would be
sufficient. Is something like this available? Is it easily possible to
extract the maintenance part and compile this?

*OS specific thumbnails*
The thumbnails are generated and stored twice in the database, because the
entries in FilePath and CustomIdentifiers are absolute and OS specific. When
my backend generates the thumbnails, the first client would do again. As far
i understood the db schema, it should be possible to use the same thumb
entry in two datasets in the tables FilePaths and Customidentifieres. This
would reduce the necessary storage. The second step is to automatically
generate a second dataset with OS specific path when albumroot has two
paths. Is this possible directly in digikam or has someone a storedprocedure
for that?

*database/network performance*
Especially when my wife uses digikam via WIFI, the reaction is too slow. We
have more than 100.000 pictures in our share. I was thinking about database
replication to each client, so that the db access is local and the
replication is asynchronous to the user interaction. Has someone experience
with that?

*export*
I did not check all export possibilities. I'm sorry if i missed the
following feature.
My idea is to export pictures based on tag combination (topic, person) and
ratings, comparable to a filter rule. I want to store these settings in a
list and also define the export path. For me it is a local path on my
server. Important for me is that the export is done as hardlink. This
reduces the storage space enormously. Is something comparable available or
planed? Or should I start my own plugin implementation?

That’s my wish list for the moment 😊.
I hope someone has ideas how to proceed.
Best regards,
Christoph






--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[brianr]

Several of us have asked for something just like that.  Add your vote to this
request:

https://bugs.kde.org/show_bug.cgi?id=254099



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[ccabek]

I gave my vote, but I think this will not really help.

Has someone ideas for my topic 2-4?



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[PackElend]

Hi there,

based on the welcomed straight answers :-) in regard of feature dev in [digiKam-users] either face recognition screen is buggy or I still don't understand it...

there are only two options:

1. get it added to GSoC/2019/Ideas - digiKam 
   
2. dev it yourself or find some support, respectively
   

   ...i'm always in favor to only use bugzilla as the main Agile project management tool. You have a file to create or already created, you build a patch against current implementation, and you attach file. It's simple, archived, and follow all QA requirement.

   @Gilles:
1.  is there any space where some idealist could find each other and try to do so under your supervision
2. could you tell where to there right spot in the source code for such enhancement?
   

here are the clarifying statement about the near future of digiKam

No. Personalty, i must for 6.1.0

1/ Finalize the internal plugins API for Genric, Editor, and BQM.

2/ Document the API

3/ Export the API for external contribution. Currently all plugins are inside digiKam project.

4/ Prepare the rooms for the new students.

Later 6.1.0 :

1/ Prepare new plugins interface as :

...

 * Database : We have already a tool named migration which can be a good candidate, but plenty of new ones can be written : backup, export, etc. Do not ask me to make the database engine as module yet, it's a tedious project.

Stefan

Am 11.01.2019 um 20:38 schrieb ccabek:

I gave my vote, but I think this will not really help.

Has someone ideas for my topic 2-4?



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html