Poll/Survey/Questionaire questions

[JohnSSmith]

I know I can create a survey using web apps, but I have some questions in regards to usage and collection. I also realise I can create an imaginary user and hide the name and email input fields.

1) Without extra code to set a cookie, am I correct in assuming that there is no way to stop people from voting twice or even more? I cant stop it based on email if I am going to use a generic email address, and even if I wanted them to enter an email address it does not look like I could stop them doing it more than once.

2) I assume that by using a generic email address it means it changes the actual choice in the database. In other words the value for their choice would change, and if 50 people submitted to the survey, I would onely ever have one value. Is that correct.

3) Collection of results - If I am correct in my assumption in (2) above, then I assume that the only way to collect the actual results, is to setup a workflow, receive the emails, and manually collate the data.

4) NOT using a generic email address - lets assume that I make everyone use a real email address and names. How do I collect the data from the survey without using a workflow and emails to collate manually as per (3) above?

Found the anser to #4 here - http://www.adobe.com/devnet/businesscatalyst/articles/creating_a_survey.html ,  although you would still need to actually download the report and do and if statement in excel to calculate numbers. There is no graph either so its not a real poll.

Answers to the other 3 would help, as although I am pretty sure I am correct, confirmation would help.

Thanks

[JohnSSmith]

Have I written this wong and nobody understands what I wrote?

If anybody could please confirm, or advise, it would be appreciated.

[mario_gudelj · Accepted solution]

HI John,

I'll try to address some of those questions, although, the web apps are not a good module for creating polls. There's no good module in BC for polls. Id' suggest you to find a hosted solution which can be easily integrated into BC using javascript. Anyway, here it is:

1 - Without extra code to set a cookie, am I correct in assuming that there is no way to stop people from voting twice or even more? I cant stop it based on email if I am going to use a generic email address, and even if I wanted them to enter an email address it does not look like I could stop them doing it more than once. <<<< If you look at our wishlist, the way it's been implemented is as follows:

- Every wishlist item is a web app item.

- All the votes are comments (uses comments module)

- The rule set on those comments is "Can comment only once"

Not sure how you're implementing the votes, but no other module support "only once" limitation.

2 - I assume that by using a generic email address it means it changes the actual choice in the database. In other words the value for their choice would change, and if 50 people submitted to the survey, I would only ever have one value. Is that correct. <<<< Not too sure what this is. Are they submitting comments or creating web app items. If they're creating web app items and you're logging in everyone under one email address your assumption is correct.

3 - Collection of results - If I am correct in my assumption in (2) above, then I assume that the only way to collect the actual results, is to setup a workflow, receive the emails, and manually collate the data. <<<< Since I'm not clear on no.2 I can only guess here, but is customers are submitting web app items, even though those will be created under the same user, they'll be separate web app items. But, some clarification would be helpful.

Cheers,

Mario

[JohnSSmith]

Mario

Thanks - you answered my questions even though you may not have realised it.

It now realise that I made it difficult, because I mention web apps and not Web forms. The result is still the same. If I use Web Forms and create an imaginary person with a Generic email address, and extend the DB to allow an answer to my questions, then the underlying data will change everytime someone posts and answer.

1) I see what you mean by the wishlist - it could be implemented that way if each person was logged in or using their own email address. Not really the way we would want to go. In essense we could use a blog as well with comments enabled.

2) Thanks - No it was creating a web app item, and not a comment - so yes  you did answer it.

3) I see what you mean.

At the end of the day I think a commercial arrangement with someone that provides a real poll service would make more sense than trying to fudge something - the client has already indicated they dont want to collate the information.

Thanks Mario

[Liam Dilley]

For me, bulding a survey type questionair you use two web apps for example.

- Use a generic auto (in the background) login to submit a web app item.

- Web app for the questions

- Web app for the submissions - peoples names and their answers.

You use the web app item add form and the layouts and pulling etc with some javascript/ajax etc.

That is the basics and it all depends on the needs, how the data is being used etc. To have a CRM element you ajax populate another form which creates a CRM customer of the person submitting the survey/questionaire. You can also set a username and password, assign them to the web app they submit instead of anonamouse login where you have those forms, have a fake "Next step" to the form which actually submits the custom web form, then logs them in in the background and then actually presents them with the web app item submit form with them logged in and it will get assigned to them. If they ever login in they could see their submissions etc.

You can build some powerful "cases" as well with double data submission to the web app item and also a case. You would do this as the web app items could be used to form results and even graphs BUT you would have cases attached the the customer for management.

Really complex to properly explain on a froum but all totally doable. Does need good knowledge of the system and very good jQuery skills but these can be pretty awesome stuff.

[JohnSSmith]

Thanks Liam

Unfortunately it is outside the expertise of the average business owner, and I get the feeling it wont be a one off request.

Maybe someone could take that code and sell it to BC

I remembered there had been a partner article on creating a survey, but after reading it as well as some forum questions, I had my above concerns about creating same without having customers/members use their name and email.

Most prefer an anonymous entry, as people don't like adding identification on contentious issues.

Simpler to use something external.

[Liam Dilley]

Either case is doable and I have done both options in some form or another for different things.
Not something you can sell to BC as its just use of what they offer with clever use of jQuery and UI Design.