Bug 490107 - Summary log report on the results of the album scanning process
Summary: Summary log report on the results of the album scanning process
Status: RESOLVED DUPLICATE of bug 392801
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 8.4.0
Platform: unspecified All
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-11 12:39 UTC by Peter
Modified: 2024-07-11 13:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2024-07-11 12:39:26 UTC 
It would be useful...
If multiple users share a digiKam database (for example: a family), it would be helpful if the application generated a summary report of the changes at the end of an album scan. After a scan is complete (100%), users can never be sure what has changed (unless they were the ones who added the images to the collection).
Since the scan process always runs, the information about what changed must exist somewhere. However, digiKam doesn't inform the user about what was added or removed from the collection.
Would be useful information:
- Element location
- Element name
- Added or removed
Comment 1 Maik Qualmann 2024-07-11 13:03:05 UTC 

*** This bug has been marked as a duplicate of bug 392801 ***