Expose the bliss database for integration with other tools
For example, it would be fantastic if you could configure your bliss installation to use MySQL for its central data store. That way you could perform your own data lookups and queries in lightning quick time, and also even write your own web front end to your music collection.
It'd be doubly amazing if you could tailor your own database table format so that it could be compatible with other things that can use MySQL as a data store, such as XBMC and others, though that might be nigh on impossible.
As you know there's http://bliss:3221/tagindex which returns the indexes of tags that bliss keeps, and http://bliss:3221/musicmodel that returns compliance. These aren't "API" though, they're really just debugging aids and might be withdrawn in future.
So I'll change the title/text to reflect the requirement for integration.
Matt Jenkins commented
An API would be OK, or maybe a way to export the database in a format that can be easily parsed and inserted into a MySQL (or similar) database would be acceptable. Even just a CSV export of the entire database would do...
I definitely will not move to MySQL.
The main reason is that developing against MySQL will introduce a lot of complexities in the way bliss is written. In addition, at runtime I suspect it will actually be slower than the current technology that bliss uses to store its data - https://github.com/jankotek/mapdb (actually an earlier version) although I haven't tested this. Writing the code to store to MySQL would just take too long.
Second, it would be better for bliss to expose an API that allows it to be integrated with other applications. Using the database is fraught because any changes to the database structure breaks the integration.
I suspect (although I might be wrong) that what you want is an API for integrating. If that is the case can we change the title of the idea?