On 7 Dec 2006, at 23:23, jeff stern wrote: > however, one thing i would like to suggest for a future version > (requiring, no > doubt a change in the underlying database schema): > > it would MUCH more helpful to me, the user, if actions-to-projects > were modeled > as a many-to-many relationship (i.e., a lattice > http://en.wikipedia.org/wiki/Concept_lattice), NOT just a many-to-1 > relationship > (simple hierarchy). > > thus, i could label an action with more than 1 project that it > belonged to.
Could you give me a concrete example (without giving away any secrets, of course!) of an action that might belong in more than one project? I'm finding it difficult to think of any of my actions that belong in more than project, but that might because you're using projects in a different way than me. We've discussed various ways to handle classifying data on the mailing list and forum, including subprojects, tags and so on, but I'm still thinking about the best way to handle these things. To be honest, the database issues aren't as tricky as the way you actually display the data and allow the user to interact with it. cheers, bsag -- but she's a girl - the weblog of a female geek http://www.rousette.org.uk [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
