[Digikam-devel] [digikam] [Bug 309058] The digiKam database can't be synchronized with XMP sidecars.

[Kevin Dalley]

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

--- Comment #21 from Kevin Dalley <kevin at kelphead.org> ---
That's a good question.

I have tried changing the name of a tag which was used by about 100
files. It does take a little while at that level. Of course, a user
could modify the tags for every file. That could be slow.

Here are the options I see:

1. Use the code changes I suggested.
    Advantages:
        Much lower risk that database and files are out of sync.
    Disadvantages:
        Could significantly slow digikam.
        Repeated operations are even worse.

2. Use Maintenance Tool. Perhaps user could be warned when operation is
performed.
    Advantages:
        Users control when files are updated.
    Disadvantages:
        User has to remember to run Maintenance.
        User has to know what to run, and which direction. A
            very big disadvantage, I think.
        If database is read from out of date files, old tags     
            return, creating a lot of work for the user.

3. Use digikam Preferences to determine behavior from 1 and 2.

4. Allow users to specify behavior when operations are performed.

5. Modify MetadataSynchronizer so that synchronization is slower and
less painful for the user. This is easy to say, but more challenging to
implement.

6. A variation on 5. Keep a list of images which are out of sync, stored
in the database. Occasionally process a few. This method avoids having
the same image listed twice. Occasionally process some files.

I somewhat like 6, but I am not sure.

Any of these methods allow for the possibility of unsynchronized data.
Completely removing this risk requires a lot of work.

On 12/09/2013 02:49 PM, Gilles Caulier wrote:
> https://bugs.kde.org/show_bug.cgi?id=309058
> 
> --- Comment #20 from Gilles Caulier <caulier.gilles at gmail.com> ---
> Hi Kevin,
> 
> What's happen if a lots of images relevant of tags hierarchy changes
> needs to be updated ? This can take a while to process. To update
> files as well can decrease digiKAm performance a lots until files
> update is done. Do you tried in production ?
> 
> I know that Aperture or Lightroom put all changes in a list to play
> when users can do it (for ex when he don't use application in
> workflow). This is the goal of Maintenance tool in digiKam. End users
> run it at the most adapted moment...
> 
> Best
> 
> Gilles Caulier
>

-- 
You are receiving this mail because:
You are the assignee for the bug.