Bug 193970

Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Motivation: Dump data and be sure it can easily be read and imported later on (or parsed by another tool).

Ideally, data dump usually shouldn't be needed, as the preferred way for most "stable" user is automatic collection upgrade on software upgrade.

Still this has sometimes not been practicable (or didn't exist), especially when trying out early adopter versions a lot.
Like that, some users like me have stopped using the collection db extensively, as the point might come, where I'd eventually clean out .kde/**/amarok(|rc), as I don't know what all these ''rc''s are for. Even if I'd just leave collection.db where it is I'm not sure if this is causing any problems as the DB format changed.

While playing with the software, I thought that somehow it's a pity that I lost all those (though not many) ratings and labels I entered some day.

Thus, it'd be of great use to be able to dump the DB to a (yet to be defined) format.

Importing from this format would be the logical next step, though there need to be some mechanism for handling duplicates.


Oh. I just notice there is an "import collection" tool builtin nowadays, which probably performs all the black magic.

Still I think adding the ability to export to a flat file (json or something) is useful, especially if this format is properly defined somewhere. 

This doesn't need to be able to export everything which is stored, but a defined set of attributes.