Metadata should become it's own class

[Benjamin Kampmann]

For the MediaUri we already have our own class, why shouldn't we make our own class for Metadata as well?

This Metadata Class would be an observable, and keeps trac that no metadata is overwritten, can handle on its own that it still has empty fields and would have a unique ID (for e.g. the URI it belongs to) to be store- and cacheable.

That could be done in an easy way like this:
Inside this class is a dictionary containing the filled data and a list of still empty fields. Both are always kept up-to-date if a new request (an empty field) or metadata is added. On every change the Oberservers are informed.

That would it make much easier to handle the metadata and to keep trac that no metadata is overwritten...

[Florian Boucault (fboucault)]

Metadata should probably be models or part of models actually.

[Florian Boucault (fboucault)]

Part of the plan for Elisa 0.3.4.

Enjoy!

[Florian Boucault (fboucault)]

Work on Metadata deprecated that ticket.