hello all,
i am looking for a php/mysql based survey engine. the main requirement is that i need to be able to put our existing authentication protocol onto it, so that select authorized users can create and edit surveys (preferably through a web interface), and select authorized users can take them. i want the results to be stored in our mysql database and results retrievable by authorized users in a usable form. if such an engine costs (not a huge amount of) money, that is fine, too.
does anything like that exist? thankful for any leads.
i am looking for a php/mysql based survey engine. the main requirement is that i need to be able to put our existing authentication protocol onto it, so that select authorized users can create and edit surveys (preferably through a web interface), and select authorized users can take them. i want the results to be stored in our mysql database and results retrievable by authorized users in a usable form. if such an engine costs (not a huge amount of) money, that is fine, too.
does anything like that exist? thankful for any leads.
posted by:
|
SF Bay Area
|
-
Re: customizable survey engine?
Mon, October 8, 2007 - 3:35 PMDefine "huge amount of money".... I dont know if one exists but i can write you one :-) -
-
Re: customizable survey engine?
Tue, October 9, 2007 - 4:51 PMhaha.. i guess i can just continue to write individual surveys.. i'm just looking for a way to make the table structure, etc, as generic as possible so that i might be able to put a front-end onto it for users to customize their questions... it gets tricky once you get to different types of questions (i.e., in addition to radio buttons, checkboxes, textfields, different points assigned to different answers etc) -
-
Re: customizable survey engine?
Tue, October 9, 2007 - 7:06 PMWell i recently wrote something similar... What i did was to use two ORM classes... Survey and Question
survey table had.... well surveys and consisted of an id, title, instructions, and description. The question table consisted of 3 columns, an id, a type (which in my case was a lookup to another table but would work as an enum as well), the question (the actual text question), and the result. My result column was just a JSON object (so i could support questions like "if yes, describe in detail"). Of course they werent using the db directly for analysis. These were more like different types of comment cards.... Still you could still do anaylsis on this since you know the format - in this case JSON, so you could write methods to query and anlyze based on certain regex in the result columns and a question type column.
May or may not fit your situation. Good luck though!
-
-
