Bug 88174

Summary: Albums only sorted into Collection if collection is listed digikamrc
Product: [Applications] digikam Reporter: Achim Bohnet <ach>
Component: Albums-SortAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: sven.burmeister
Priority: LO    
Version: 0.7.0   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:

Description Achim Bohnet 2004-08-26 23:38:06 UTC 
Version:           0.7.0-cvs (using KDE 3.2.3,  (3.1))
Compiler:          gcc version 3.3.4 (Debian 1:3.3.4-7)
OS:                Linux (i686) release 2.6.7-ach-1-686

When moving digikamrc aside. I noticed that all album<->
collection relations where lost. Only exception was the
'buildin' collection Family.  Adding my created collection
name in digikamrc made digikam sort all albums into collection
again.

Would be nice if there would be some sort of recovery mechanism
could be implemented (e.g. check on album open if the associated
collections of the album are listed in the collection name list)
in case someone uses rm instead of mv.

Achim
Comment 1 S. Burmeister 2006-07-09 01:11:30 UTC 
I second this request. If one moves one's collection to another computer, including the xml-files in the diretories, digikam should take the collection-names from those files and add them to its list.

It is really unnecessary work to have to add those names again, one by one, if they are already in the xml-files, which are parsed while digikam is starting anyway.
Comment 2 S. Burmeister 2006-07-09 01:15:05 UTC 
I just noticed that even if one has a look at the properties of the album, i.e. the folder, the name from the xml-file is not shown as collection-name.

At least at that stage it should be read from the xml-file and added to the list of collection-names.
Comment 3 Mikolaj Machowski 2007-11-18 21:55:31 UTC 
Since collections are going away and bug mentions xml files (already dead for some time) I am closing this as WONTFIX.

If you cannot live with that feel free to reopen this bug.