The webform module provides a very similar feature to this module. There are several others as well: surveys, qforms, multiforms.

One of the 7 principles of the Drupal project is collaboration. Would you consider merging your project into that one and collaborating with it's authors?

Otherwise, it would be great if you could document on the project page what makes this module different and also link to that module so that people can make a good decision about which one to use.

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

I forgot one more - http://drupal.org/node/1136296

johngriffin’s picture

johngriffin commented

Hi Greg,

You're right, there are a few survey modules out there, but none of them scratched our itch so we decided to do our own. I think there's a possibility of releasing this as a D7 version of surveys, as we have similar missions, but other than that I think the differentiators are:

- This is essentially a back-end for form_builder - providing entities to store surveys, questions and responses

- We need a pool of re-usable questions for our purpose, so that's built into the architecture

- We will be adding conditional logic at some point (show/hide questions based on other question responses)

- We're storing responses in such a way that should allow us to do statistical analysis later on.

- It's written for D7, using entities.

Using webform is out because:

a) we want to use the form_builder UI
b) we want to store our responses in a particular format in entities
c) we want re-usable questions

Because of these points, its easier for us to just roll our own than try to extend anything else.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

The only one that looks actually different to me is having a pool of re-usable questions and using entities (though probably one of the other solutions is also using entities at this point).

Please state these differences clearly on the project page and link to other solutions where you can.

johngriffin’s picture

johngriffin commented
Status: Active » Closed (works as designed)
greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Closed (works as designed) » Needs work

@johngriffin - could you update the project page a bit to link to some of the other solutions and say "In contrast to those, this one..."

johngriffin’s picture

johngriffin commented
Version: » 7.x-1.0-alpha1
Status: Needs work » Closed (fixed)

Hi Greg,

Project page has been updated with the following copy. Hope to do a comparison table at some point, but not likely to have time in the near future.

Another survey / form module? Why?

  • This is essentially a back-end for form_builder - providing entities to store surveys, questions and responses
  • We need a pool of re-usable questions for our purpose, so that's built into the architecture
  • We will be adding conditional logic at some point (show/hide questions based on other question responses)
  • We're storing responses in such a way that should allow us to do statistical analysis later on.
  • It's written for D7, using entities.

There are several other modules available that are in the business of allowing you to create forms, the most popular being Webform. Others include Surveys, QForms, Multiforms. They're all different so we recommend reviewing them all before deciding which is best for your use case.