pfarrell Wrote: > On Sat, 2005-11-05 at 10:55 -0800, ovonrein wrote: > > pfarrell Wrote: > > > The key problem is that any hierarchical structure fails for > > > classical music. > > You lost me with this one. I had thought that > > Composer/Work/Artists/Movements > > pretty much covers all bases. I am not too bothered mixing singers > and > > conductors in the Artists component. > > Its all personal preference. You like Composer/Work/Artists/Movements > where I would tend to prefer: /Genre/Composer/Artist/Work/Movements > > But I really don't want it to be hierarchical. > > -- > Pat Farrell > http://www.pfarrell.com
It looks as though people are comfortable with a hierarchical method of browsing their collections. There's no reason one couldn't implement it on the server by searching the database for the appropriate tags, while presenting it to the user as if it's a redundant hierarchy. In other words, why not present it so you can choose Composer/Work/... or Artist/Composer/...? Each level of the heirarchy just becomes a term and-ed to the SQL query. -- Iain Bason ------------------------------------------------------------------------ Iain Bason's Profile: http://forums.slimdevices.com/member.php?userid=2178 View this thread: http://forums.slimdevices.com/showthread.php?t=17877 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
