VULab Survey Question Types

Tue Dec 9 20:01:57 UTC 2008

Hey Blake,

I think it would be great to automatically capture user environment  
information for each survey.   Internet connection is another  
important attribute for user testing.  Also, what about any assistive  
technologies?

-Daphne

On Dec 9, 2008, at 11:37 AM, electBlake wrote:

> Jess,
>
> I do agree that I don't see it saving a lot of time as I will have  
> to develop the system smarter but like you said, it doesn't seem all  
> that controversial. I am trying to think if there is anything  
> specific to a usability type surveys that would be could include,  
> even if just in the planning stages now for integration farther down  
> the line.
>
> Maybe...We can add something to capture the platform information of  
> the visitor. Screen Resolution, Operating System, Browser, etc.etc.  
> I was thinking of adding this as a "question" but maybe we'd just  
> like to have it gather/save for every survey result?
>
> Thanks,
> Blake
>
>
> On 9-Dec-08, at 11:49 AM, Jess Mitchell wrote:
>
>> Blake,
>>
>> From my experience with Viewsflash this looks like a pretty  
>> straightforward list of question and answer types.  I'm curious to  
>> see if your consolidation at the bottom buys you much time, but it  
>> also seems uncontroversial.
>>
>> Do you have them listed in order-of-priority and therefore  
>> development? 1-5?  If so, that too looks good to me.
>>
>> Best,
>> Jess
>>
>>
>> ~~~~~~~~~~~~~~~~~~~~~~
>> Jess Mitchell
>> Boston, MA, USA
>> Project Manager / Fluid Project
>> jess at jessmitchell.com
>> / w / 617.326.7753  / c / 919.599.5378
>> jabber: jessmitchell at gmail.com
>> http://www.fluidproject.org
>> ~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>>
>> On Dec 9, 2008, at 10:46 AM, electBlake wrote:
>>
>>> Hello All,
>>>
>>> Blake here from Toronto/VULab WEB, and if you haven't herd - we  
>>> are making the switch to a proper php framework (EXCITING!). We  
>>> are looking at CodeIgniter.com and CakePHP.org, but that isn't why  
>>> I'm calling on you this morning.
>>>
>>> Due to the dramatic (positive) change that a framework will bring  
>>> to VULab, we will be re-engineering the survey design tool/process  
>>> (nearly) from the ground up!
>>> I want to start by isolating the types of questions we want to  
>>> offer as well as isolating the importance of each. Once we have a  
>>> list of question types we can agree on, we can develop them into  
>>> VULab working down the list from most important to optional  
>>> questions. You should consider what type of information you'd want  
>>> to gather if you were conducting a usability test.
>>>
>>> VULab currently uses the phpESP survey design tool so I'll outline  
>>> what is included there and then I'll give me opinion on types/ 
>>> priorities.
>>>
>>> One thing that should be noted is that a question "type" can span  
>>> different "implementations". For example, a Boolean type of  
>>> question could be implemented as a True or False, or a Yes or No,  
>>> or even an Apples or Oranges. I'll distinguish between the types  
>>> of questions and the implementations below.
>>>
>>>
>>> phpESP Current Question Types:
>>>
>>> Boolean Question Type
>>> This is a question type whose answers could resolve into a 1 or 0.
>>> Implementations:
>>> Yes/No
>>> Text Input Question Type
>>> This is a question type whose answers are stored as text.
>>> Implementations:
>>> Text Box
>>> Essay Box
>>> Numeric
>>> Single Option Question Type
>>> This is a question type whose answer is chosen from a list and is  
>>> specific to one option.
>>> Implementations:
>>> Radio Buttons
>>> Dropdown Box
>>> Multiple Select Question Type
>>> This is a question type whose answer can be 1 or more options from  
>>> a given list.
>>> Implementations:
>>> Check Boxes
>>> Date Question Type
>>> This is a question type whose answer is a specific date.
>>> Implementations:
>>> Date
>>> Rating Question Type
>>> This is a question type whose answer is a number within a selected  
>>> scale.
>>> Implementations:
>>> Rank.
>>>
>>>
>>> As I see it, we can consolidate a few of these and prioritize them  
>>> as follows for VULab
>>> Note: Single/Multiple types have been combined.
>>>
>>> Boolean Question Type
>>> This is a question type whose answers could resolve into a 1 or 0.
>>> Implementations:
>>> Yes/No
>>> Text Input Question Type
>>> This is a question type whose answers are stored as text.
>>> Implementations:
>>> Text Line Box
>>> Multi Line Box
>>> Numeric
>>> Multiple Option Question Type
>>> This is a question type whose answer can be 1 or more options from  
>>> a given list.
>>> Implementations:
>>> Check Boxes
>>> Radio Buttons
>>> Dropdown Box
>>> Rating Question Type
>>> This is a question type whose answer is a number within a selected  
>>> scale.
>>> Implementations:
>>> Rank/Scale (Definable Start/Finish)
>>> Date Question Type
>>> This is a question type whose answer is a specific date.
>>> Implementations:
>>> Date
>>>
>>>
>>> Are there any other question types that we should consider? Is  
>>> this an appropriate prioritizing? ANY input is much appreciated.
>>>
>>> Thanks!
>>> Blake
>>> _______________________________________________________
>>> fluid-work mailing list - fluid-work at fluidproject.org
>>> To unsubscribe, change settings or access archives,
>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work

Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
daphne at media.berkeley.edu
cell (510)847-0308

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20081209/bf2f83c4/attachment.htm>