Details in import log

[GoogleCodeExporter]

(Continuing a discussion from an email thread.)

To assist in building external tools, it might be helpful for the import log to 
include much more information than it currently does and to include it in an 
easy-to-parse format. Some examples of what could be included:
- the path to the album/singleton
- action (e.g., asis, skip, duplicate, etc)
- duplicate path, if any
- details about the match (MBID, etc)
- distance
- cover art results
- values from plugins (genre, etc.)

It's my current feeling that the log syntax should be based on JSON or YAML 
(probably YAML) to facilitate trivial parsing.

Original issue reported on code.google.com by adrian.sampson on 12 Jan 2012 at 7:14

[GoogleCodeExporter]

Original comment by adrian.sampson on 19 Feb 2012 at 10:46

• Removed labels: Milestone-1.1

[untitaker]

Do not comment here, but on sampsyo/beets#141