Heh, we already do, which is to say bliss uses the same API that the writer of Jaikoz created and open sourced. elsten software just donates some money to the project each year.

Given that this work is in building a Web based tag editor, the challenge would be the separation between the user interface and the underlying guts of the application.

I have been using Jaikoz (http://www.jthink.com/jaikoz/) for years, which is an excellent and really powerful Java-based desktop client for organising your music library. Maybe you guys could collaborate?

Some work in progress: http://i.imgur.com/GvraZ.png

I'm thinking I might release this in a read only form first. It is still fractionally useful that way. Then I will add editing, the ability to add columns for different tags and maybe a per file 'all tags' detail view.

I just added some clarification around this idea. The first step in this idea will be to implement a web based 'traditional' tag editor.

I was initially thinking that an extra top level page for 'files' alongside albums and artist would make sense for the tagging view. This would have to be paged. All tags would be shown in the traditional tag editor style spreadsheet interface.

Or, the tags could merely be shown on each album page. I just thought the former would be more powerful.

I currently also make use of StampID3 from NCH. Unfortunately it can be quite slow and the individual albums appear in a random order. If 'bliss' where you can access the the albums in either artist or album alphabetical order could be enhanced to take over the StampID3 functionality it would certainly be an improvement.

I think that kind of interface can be really useful for judging the numbers of assignments of existing genres/composers etc and re-assigning. As I said via email, I think it could be very useful for genre 'balancing' if the genres were drawn in a size proportional to their population.

That said, I see this idea as being 'track oriented' tag editing in the familiar way we think of music taggers now, e.g. MP3Tag et al. Your assignment idea is useful, but it's approaching the problem from a different angle. Maybe I misunderstand your UI suggestion?

I can envision substitution rules for the tags commonly used by players such as Sonos: Genre, Artist, Composer. You could support a file-browser type hierarchical interface. Tag -> Genre, AlbumArtist, Artist, Composer -> All Genres in my collection, All AlbumArtists in my collection, AllComposers in my collection -> All albums/tracks for a given Genre, .... etc. Then for instance dragging tracks and or albums from one genre to another could 1) change the genre in those elements as a one time substitution, or 2) create a persistent rule for the server daemon - user selectable. Like in my collection, I could use a persistent rule that substitutes Handel, for G. F. Handel, George Fredric Handel, etc. But other stuff is just classified incorrectly and would be a one time substitution. You could supply the ability to enter regular expressions for those that are technically oriented. But in many cases the substitutions could be derived from a drag and drop interface as described above.

Must have the ability to add/delete and set defaults for all tags based on rules. A perfect example is that unless Genre=Classical I do not want a composer on any track. If any track has composer in its tag and Genre not equal Classical, remove that tag entry.

Hey. I've had it in mind to have some simple tag editing such that album names and artist names can be edited inline in the Web UI. E.g. you click on the album name, it changes to a text box and you can edit the name.

In terms of knowledge of what a 'tag' is I want to bury that a little in the user interface. I'm not saying I wouldn't do it, but it would have to be some advanced view and not the default. I think other tools like music taggers do this job already.