Hi fellow Django users,
I'm coming up on a phase of a project where I need to do a lot of work
with Forms and Manipulators. I've got some historical bits of old CMS
ideas that I'm trying to work with. I wanted to ask Django-users if
this approach seems reasonable, or if another approach would work
better. If anything this might be a good use-case for the new Forms
work but I'm building against 0.95 currently.
For various teams we've set up some default question types to display on
pages, such as:
- Multiple choice (radio buttons)
- Multiple choice (checkboxes)
- Short text input
- Long text input
- Likert scale series of questions
Typically we've had a data schema along the lines of this (not valid
Python or Django, but trying to be similar for ease of comprehension):
class Question:
content = Text
type = ForeignKey(QuestionType)
class Option:
question = ForeignKey(Question)
sequence = Integer # for ordering of options
content = Text
value = Char
From there we'd take the type and build the necessary HTML and form
elements to display to the user. User responses are stored in a
"response" table and references the question id and user id. The
response table schema is something like this:
Response:
user_id
question_id
answer = Text
answered = DateTime
session = Char
In the past, this has been sufficient and generic enough for us to allow
teams to build their own mini surveys. And we've been able to tie user
response data back into our programs if we need to customize or tailor
content based on responses (think "cosmo" quiz style questions with
appropriate feedback.)
So how does this system fit with Django, if at all?
On first glance at the FormField and Manipulators documentation I'm
having a little trouble seeing the solution. I'm trying to imagine
where all the pieces fall into place. Does this belong in its own app?
Or is each URL mapped to a different view that handles each question
(ie: /page/20100/ is the quiz, /page/20101/ is the result based on user
response)?
We do already have a Page model that has 1-to-many relationships to each
of Text, Graphic, or Media for a basic template based CMS. Adding
another reference to Question would be feasible. It would then simply
be up to the view to render the Question -- though on the POST side I'm
not sure how Django would catch the data in that case.
Any thoughts or guidance is appreciated. I'll be testing a few
approaches (I'm guessing) over the coming weeks.
Thanks,
Rob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
