Bug 296864 - SETUP : Create interface for changing physical location or path of album
Summary: SETUP : Create interface for changing physical location or path of album
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Database (show other bugs)
Version: 2.6.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-27 09:23 UTC by Glenn Washburn
Modified: 2019-03-14 20:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Glenn Washburn 2012-03-27 09:23:52 UTC
The current problem is that if the digikam user want to move an album to a different path from the root of the device its currently on, or to a different device, digikam will show the album with a red 'x' indicating that the path does not exist.  The user could delete the album and create another using the new path, however I'm not sure if that has undesired side effects and it will potentially take a long time to scan all the album photos.

This is "easily" fixed (for a knowledgeable user) by updating the database by hand, namely the identifier column and/or specificPath column of the AlbumRoots table needs to be updated.  This should be allowed by the UI so that everyone has a chance to do this.

I suggest having an edit icon button which pops up a file chooser dialog for the user to select the new location of the album.  The FHS path should be all that is needed to figure out the needed column values.
Comment 1 Marcel Wiesweg 2012-07-08 12:29:32 UTC
What's the problem with moving the album by drag and drop from within digikam?
Comment 2 Maik Qualmann 2019-03-14 20:38:33 UTC
This problem is no longer reproducible. It is also possible to assign a new path or drive to a collection. I close the bug.

Maik