[digiKam-users] database pointed at subset of same files in rearranged folders

[Ty Mayn]

thank you for this caution.  I view the retention of records that dont map
to a current loaded collection to be an asset and I would expect the
maintenance purge to be sufficient.
I would hope an automatic purge at some arbitrary time (such as 2 weeks
that you estimate) should have a dialog message to the user letting it be
known that the fateful hour has arrived  for removal. Somehow carrying that
out silently after some wait seems the worst of both worlds. It is better
to force an unmatched record to  the surface for the user to attend to it
or just keep it on standby
 I would welcome just a statistics page that would state  sequentially each
of the named collections with load and unload (or disconnect) dates and a
count of the retained records  that are unused in relation to those old
collection pathways and furthermore unmatched into the current loaded
collections. Then the user is aware and can  cleanse at will.
    It is interesting that cleanse has a toggle to be either album or tag
based. Albums are folder trees essentially and in that sense they can be
made to align with past named collections. But it would be nice to have a
Maintenance menu which can be collection centric...meaning that it can
offer a list of past loaded collections and allow the folder tree for each
collection to be retrieved and cleansed independently. Overlaps of
successive named collections could be problematic.  Maybe I am speaking too
soon (or too late) if such tool already exists somewhere.
    On the matter of what a scan does .... I would welcome a programmers
observation. As I have stated in this thread it appears to be an additive
only process that looks for new file items in the album tree and adds
records, but not  removing any record that has become unrepresented in the
file image collection.   The  menu says "scan for new items" insinuating
that it is on the lookout for new incoming images and  the cleanse tool is
right below.
     As I have stated in this thread I believe these "behaviors" need to be
named and explicit and they should be displayed  in the text menus where
there is ample  whitespace available.
      Although I would like to know the firm answer to these questions via
maillist, I would like to see a sort of enhanced Menu which divulges larger
hints about the consequences of powerful actions sitting behind the
checkboxes.  Some new users are in a candy store and others are just
surrounded by fear or at least curiosity.
Ty





On Sun, Feb 24, 2019 at 1:48 PM Andrew Goodbody <ajg02 at elfringham.co.uk>
wrote:

> On 23/02/2019 18:36, Ty Mayn wrote:
> >       Am i correct to think that the only actual deletion of a database
> > record (ever) is under Maintenance>PerformDatabaseCleansing?
>
> No. Records will eventually be deleted after a period of, I think, two
> weeks, if the target is no longer available. It is a long enough period
> that if you have a short term network failure, it will not immediately
> remove the data, but also it will not keep records around for ever if
> the files were deleted outside of digikam.
>
> I would guess that the scan also records those files that are not
> available. I am not sure what would eventually trigger the removal of
> the records once the time above has expired, but that could be the scan
> or it could be another house keeping process running periodically.
>
> Andrew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20190225/8344cfd4/attachment.html>