Darin, I'm a newbie also and Web2py plug-in wiki may do the job.
If not, off the top of my head the data model roughly seems to be as follows. I could have misread the concepts, but here's a general idea. auth_user table (web2py automatically creates this. It would be like PersonTable if not already automatically created by w2p) 1. first_name 2. last_name 3. etc. ISSUE table 1. Issue_name 2. Issue_summary 3. created_by PROPOSED-SOLUTIONS table 1. issueID (from ISSUE table) 2. proposedSolutionDescription SOLUTION-COMMENTS table - need to let people make arguments, counter-arguments, and follow-up comments. One person is allowed to have multiple comments per issue 1. personID (from auth_user) 2. proposedSolutionID (from PROPOSED-SOLUTIONS table) 3. solutionComment VOTE table 1. issueID (from ISSUE table) 2. personID (from auth_user) Don't need a ranking table as this will be calculated on the fly via smartgrid in controller. I merged ACTION AND OBJECTIVES table into PROPOSED-SOLUTIONS so they can be individually voted on. db._common_fields.append(auth.signature) ## adds signature fields to all tables. Automatically inserts who populated field, when created, and when last edited Alex On Saturday, June 1, 2013 4:30:49 PM UTC-7, Darin Lawson Hosking wrote: > > I am new to web2py and python programming so bear with me. > > As a learning project (career change) I am trying to build a useful app > based on my current skill set. > > I Would like to know if I am going in the right direction or is there an > easier way? > > This a synopsis of what I want to model. > > Lets look at the process. > > 1. List of issue's. > Everyone places weight / ranking on each issue > > 3. Weighting is based on a scale from 1 - 5 > Average the weighting and develop a stack ranking=(average score) > "with" (count votes) "participants" > > 4. Objectives is a child of Issue table. > (comments, ranking, discussions etc..) > > 5. Action is a child of objectives > (comments, ranking, discussions etc..) > > Develop a checkpoint / dashboard to monitor the activity votes/posts etc.. > (possible social signals aka twitter, google news, etc..) > > Question is should I go with separate table for each or what would be the > most robust for future expansion? > > Such as > DB = Issues > DB = Objectives > DB = Actions > DB = Ranking > > if so how do I do the linking etc.. > I have messed around with the > "Field<https://127.0.1.1/examples/global/vars/Field> > ('obj_parent', type='reference major_issues', notnull=True, > label=T<https://127.0.1.1/examples/global/vars/T> > ('Obj Parent'))," > but not quite understanding how to move forward with the views / reports > aka do I use smartgrid vs a query etc.. > > Please be gentle :) I have been using web2py for 2 days. > > Thanks in advance > Darin > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
