[Contrib: Evaluation System] Scale values in the database

[Will Humphries]

Yeah, currently scale_option_index defines what option is first, and the 
eval tool's reporting logic adds 1 to that number when assigning a 
numeric value for the purpose of reporting. So it's important that 
anyone trying to export from the db be aware of that need to increment. 
My patch won't change that assumption, which is nice for anyone who is 
already exporting eval results. scale_option_index 0 is still going to 
be worth 1 point, but when a student takes an evaluation, any scale with 
reversed=true will be rendered with scale_option_index=0 showing up last 
instead of first.

I'll get a JIRA and patch made soon.

-Will

On 8/7/13 1:31 PM, Nicola Monat-Jacobs wrote:
> Thanks Will, I'm glad I wasn't imagining that this came up.
>
> I think its more that folks think that 
> EVAL_SCALE_OPTIONS.SCALE_OPTION_INDEX is a value for responses that 
> they can export when it seems to me that its more just about display 
> order.
>
> So it's not that the first option is "always worth 0" its more that 
> SCALE_OPTION_INDEX defines what option is first (aka 0th place) and 
> there is no column that defines what the option is "worth".
>
> Nonetheless, I think there are folks who might be interested in your 
> patch. Can you make a JIRA for it?
>
> Thanks,
> Nicola
>
>
> On Wed, Aug 7, 2013 at 10:22 AM, Will Humphries 
> <Will.Humphries at tufts.edu <mailto:Will.Humphries at tufts.edu>> wrote:
>
>     The first scale option is always worth 0, and the last is always worth
>     N-1 in the db (for N options). When means are calculated, the first
>     option is worth 1, and the last is worth N.
>
>     We had a request at Tufts to support the reverse of that - first
>     option
>     displayed worth N points for reporting. The way I did that is to add a
>     boolean field to eval_scale called Reversed, with a checkbox in the
>     Create/Edit Scale UI to set it.
>
>     If a scale has reversed set to true, the scale options will be
>     displayed
>     in reversed order when previewing an item/template, or taking an
>     evaluation. So the option worth N points is displayed on the left/top.
>
>     I also added an admin setting that controls whether the Reversed
>     flag is
>     available system-wide. That's controlled by a checkbox in the
>     Administration page.
>
>     If anyone else is interested in this functionality, I'm happy to
>     create
>     a JIRA and submit a patch.
>
>     -Will
>
>     On 8/7/13 12:59 PM, Nicola Monat-Jacobs wrote:
>     > Folks -
>     >
>     > I remember someone mentioning that they had issues with scales and
>     > their database values. For example, Strongly Agree is always 0
>     in the
>     > database, no matter if its displayed on the right or left for a user
>     > and they wanted it to be 4.
>     >
>     > I'm not seeing any JIRAs or threads on the list about it.....was
>     this
>     > only ever discussed at the conference? I could have sworn I remember
>     > it coming up before.
>     >
>     > Thanks,
>     > Nicola
>     >
>     >
>     > _______________________________________________
>     > evaluation mailing list
>     > evaluation at collab.sakaiproject.org
>     <mailto:evaluation at collab.sakaiproject.org>
>     > http://collab.sakaiproject.org/mailman/listinfo/evaluation
>     >
>     > TO UNSUBSCRIBE: send email to
>     evaluation-unsubscribe at collab.sakaiproject.org
>     <mailto:evaluation-unsubscribe at collab.sakaiproject.org> with a
>     subject of "unsubscribe"
>
>     _______________________________________________
>     evaluation mailing list
>     evaluation at collab.sakaiproject.org
>     <mailto:evaluation at collab.sakaiproject.org>
>     http://collab.sakaiproject.org/mailman/listinfo/evaluation
>
>     TO UNSUBSCRIBE: send email to
>     evaluation-unsubscribe at collab.sakaiproject.org
>     <mailto:evaluation-unsubscribe at collab.sakaiproject.org> with a
>     subject of "unsubscribe"
>
>