Correct this is a data modelling question.
Based on the strengths and flexibility web2py I am trying to figure out how
to model the process I described.
Is it better to use separate tables for "issues", "objectives", "actions",
and "ranking" then use queries etc to link them together?
If so is it better to use smartgrid or write custom python code?
or as was suggested just recently
Use the wiki as content management and extend onto the the "star widget" to
allow voting and reporting.
The goal is to be able to show "Average ranking is x with xxxx members
voting"
My challenges as a new user / programmer is the "linking / reporting of the
data".
simple sample data
Issue table:
Issue_name, Issue_summary, created_by,
New School built, School is no longer large enough, Bob
Objectives table:
Objective_parent, Objective_name, Objective_summary, created_by
New School built, select Joe as architect, Joe has volunteered to assist
with project, Tammy
Action table:
Action_parent, Action_name, Action_summary, created_by
Select Joe as architect, Verify Joe's accreditation, Jenny
Ranking table:
Item_voted_on, ranking, who_voted, voted_comment
New school built, 5, Bob, I strongly suggest we move quickly
Verify Joe's accreditation, 5, sandy, I used Joe last year on our gymnasium
expansion
reporting
Issues by ranking
"New School built" has a current priority of 5 with 1 person voting
Objectives
"Select Joe" as architect has approval of NO VOTING RESULTS
Actions
"Verify Joe's accreditation" has approval ranking of 5 with 1 person
voting
This will be a dynamic / live report
Voting to be locked to 1 vote per issue with comments for a vote as an
option
All entries can only be edited by the person who created it or admin and
all changes logged
Thanks
Darin
PS thanks for forcing me to go back and clarify / rethink the application /
process. :)
On Saturday, June 1, 2013 6:30:49 PM UTC-5, 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.
