hi, i am just trying tracks out and i like it and the fact that it is web-based.
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. this is because i have many tasks i do which are parts of more than one project. when i have such a task, i don't want to have to a) create it twice or more - once for each project and b) check it off twice or more -- once for each project. i just want to say i'm done with that task and have all projects that task was a member of register the change. thanks. -- jeff stern / social sciences computing services sst 629 / 949-824-2326 / [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
