For me, that's the point of tagging: Eeasy sorting/classification. So what both ui and puke7 mention is the way I think of tags, and how I've been using them, besides adding more info to tracks.
http://img411.imageshack.us/img411/804/examplet.png > hmmm, FAVS might as well also be a playlist. Actually, all entries for each category could potentially be a playlist for rendered tracks, and/or entries pack for the real lazy (meemememememmeme)
But yeah, FAVS could be a playlist like it's now, but just bringnig it up for other "categories"
hehehe, houston categoring is a problem. I dunno what's the point with remixes/chiptunes/and ohcs, though I acknowledge (or I believe to know) the origin. Non chip battle, battles and ohbs.
As big categories for organization I'd only kept two major categories, eg: BIG BATTLE, and SMALL BATTLE (Terms can (and should be changed/not used))
* Big Battle = anything submitted to battles lasting more than one hour. Be it chip (nsf, sid, mods for winterchip/3xtheme) or amensin, renoise2.5, detroit, and any other big remix/allgear/surprise remix deallies, including vsts.
* Small Battle = any work submitted for a ohb.
Regardless of works submitted to either battle (like some n00bs submitting nsfs to detroit remix dealie XD) sub-organazing/displaying/categorizing (sp?) specific file formats could work (especially for winter chip+3xtheme) That way at least chiptune is taken off as category (though we all know those are "chip")
Remix = what's wrong with it? What if a remix is tweaked too much, to the point to remind people of chip works. What about "works" or "submisions" maybe too generic-plain-and broad :(
The categories/switches is nice since they'd only be displayed-parse when the user clicks on the category, so in that case space is not such a big issue, unless you want the ENTIRE catalogo of works by a BotBer.