Revise Service Satisfaction Rating System (2SP)

[mattsayre]

speedupsanjose.com uses an All/Negative/Neutral/Positive rating system. This has multiple advantages over the older method that speeduplouisville uses (star rating). The benefits include ease of visualization on a map, filter selection ease. and the rating itself includes less ambiguity. This Issue is to revise the start rating system with the All/Negative/Neutral/Positive rating system.

[ryanrolds]

What do we think about not adjusting the existing the database values in this PR and making that a 1SP ticket?

@khutchison can we get a 2-3 of example UIs that you would like to model it after? My only ask is that we have a "null" and be the default. I can go either way on strong positive/negative in addition to positive/neutral/negative (minimum, IMO).

[khutchison]

@ryanrolds that would be great. my thoughts: speedupsanjose's is good because it has fewer stars than ours and they are labelled with satisfaction values.

I think it is good to include strong positive/negative since it allows people to express some nuance between displeasure and outrage. So down to five stars from seven, we label the stars, and if they don't select anything it registers as null (so we don't have to clutter up UI with an additional default option). Thoughts?

[khutchison]

Note that while speedupsanjose collects data with 5 options on the speed test, the map filters show only "All" "Negative" "Neutral" or "Positive". So if we decided to show satisfaction as a map filter, it shouldn't be a problem to do it with our existing ratings system.

[ryanrolds]

Can we use a series of smiley faces or thumbs up/down and neutral?

[ryanrolds]

Or even with buttons rather then stars as I don't think stars a fitting iconography.

[khutchison]

thumbs.pdf