Written by oddible the 29 Sep 09 at 17:53.

1) Provide a mechanism to better codify and search for Label Sets

a) a field for number of answers so people can find the 13 point Likert scale that someone else created for instance (~cringe~)

b) a catalogue to explore labelsets and

c) a field for descriptive keywords for each labelset rather than relying on the labelset names.

d) a Labelset search

1) Provide a mechanism to better codify and search for Label Sets a) a field for number of answers so people can find the 13 point Likert scale that someone else created for instance (~cringe~) b) a catalogue to explore labelsets and c) a field for descriptive keywords for each labelset rather than relying on the labelset names. d) a Labelset search

Written by izahn the 16 Oct 09 at 07:11.

I agree that label sets tend to become a problem. One way to address this is to have a system where each user manages their own set of labels. This could work as follows:

1) Each user has their own list of label sets

2) Have a global list of label sets that consists of the combination of all the individual user's label sets

3) Users can copy label sets from the global list into their personal label set list.

This way each user is not overwhelmed by the clutter of label sets that tends to accumulate, but can access the master list if they want to.

I agree that label sets tend to become a problem. One way to address this is to have a system where each user manages their own set of labels. This could work as follows: 1) Each user has their own list of label sets 2) Have a global list of label sets that consists of the combination of all the individual user's label sets 3) Users can copy label sets from the global list into their personal label set list. This way each user is not overwhelmed by the clutter of label sets that tends to accumulate, but can access the master list if they want to.

Written by izahn the 16 Oct 09 at 07:24.

I don't think time stamps are the way to go. Just calculate the actual time spent.

It's actually kind of complicated I think.

1) If presenting one-question-per-page, have a question attribute "record time".
2) If presenting one-group-per-page, have a question group attribute "record time".
3) Store the value in a field named "QUESTIONID_time" if survey is presented question-by-question or "QGROUP_time" if survey is presented group-by-group.

If you have these all turned on in question-by-question presentation mode then you've just doubled the number of fields in your data set. So I don't think this should be and option at the survey level, only at the group/question level.

A related request is to set time limits for questions/question groups. After the time limit has expired the survey moves on to the next question/question group.

I don't think time stamps are the way to go. Just calculate the actual time spent. It's actually kind of complicated I think. 1) If presenting one-question-per-page, have a question attribute "record time". 2) If presenting one-group-per-page, have a question group attribute "record time". 3) Store the value in a field named "QUESTIONID_time" if survey is presented question-by-question or "QGROUP_time" if survey is presented group-by-group. If you have these all turned on in question-by-question presentation mode then you've just doubled the number of fields in your data set. So I don't think this should be and option at the survey level, only at the group/question level. A related request is to set time limits for questions/question groups. After the time limit has expired the survey moves on to the next question/question group.