Hi,

I want to know if webforms would be a good choice for the following use case:

  • 6 organic groups with 50 users each (athletes).
  • Each of those 300 athletes need to fill out a daily form (to report hartfrequency, weight, how they feel, and complaints).
  • Twice a year they need to fill out a large form with 50 questions.
  • A (para)medical/technical staff needs to review the forms within the groups they are responsible.

So this would need:

  • results filtered by user
  • presenting the results on a timeline
  • comparing latest form submission to mean of previous form submissions
  • filled out forms (or a link) added to the userprofile

Is it reasonable to expect this from webforms? Are submissions nodes (like the questionnaire)?
Would it be better to create the questionnaire as a contenttype with CCK (or another module)?

Comments

quicksketch’s picture

quicksketch
he/him
commented

I like to recommend webform for cases where you'll need to create a large number of different forms for short periods of time. It's generally not the be solution to be used as a cornerstone of your site. Because of the requirements for displaying the results, and it seems like the forms will remain generally the same throughout the life of your site, I'd recommend using CCK instead. Some solutions already exist for making timelines against nodes, and you'll be able to use views to make most of the lists needed for your site.

Because webform submissions are not nodes, you'd have to implement a lot of this functionality from scratch or raw SQL queries. The node system is much better suited to deal with the amount of processing you're going to want on your results.

alldirt’s picture

alldirt commented
Status: Active » Closed (fixed)

Thanks for the clear answer.