Bug 507441 - Resume interrupted metadata sync
Summary: Resume interrupted metadata sync
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Maintenance-Metadata (other bugs)
Version First Reported In: 8.7.0
Platform: Microsoft Windows Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-24 12:57 UTC by HubMiner
Modified: 2025-07-24 13:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented 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 HubMiner 2025-07-24 12:57:07 UTC 
PROPOSAL: Create a queue mechanism for metadata-sync that survives app restarts.

STEPS:
* Media files are updated, resulting in "... files await synchronization".
* Click to start synchronization.
* While it is running, terminate DK process & verify it is completely shut down, aborting the sync before it is finished.
Start DK.

BEHAVIOR
Currently, DK is unaware that synchronization process was not completed, leaving XMP/media files in unknown state.
"Tools - Maintenance - Sync Metadata and Database" process is too heavy as it affects whole collections, running for very long time.

DK should save metadata sync in a queue and after a restart, it should resume XMP/media files synchronization process if the saved queue was not completed.

Extra nice to have: on a fresh start, put the remaining queue in a paused mode, so it can be resumed by clicking "... files await synchronization".

Extra extra nice to have: do not force media sync when shutting down DK.  Let users choose when to run it, since sync steps are saved.