-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Rethinking severity scales #3306
Comments
We had some discussion on Slack about how we would want to collapse existing data to a 3-point scale. I offered these suggestions:
@jonfroehlich said that he was thinking of going with option 1, and I think that that sounds good! @jonfroehlich also brought up the need to not lose the old data that is more granular, either by saving the data in a separate table or otherwise. I suggested that if we are only going to use this for offline analysis, then saving database dumps for every city would be sufficient to have it saved for the future. Another thing I thought of while working on the new Validate page today, where we are visually showing a 3-point scale, even though that hasn't been implemented anywhere else yet: There is some extra logic that was added that needs to be removed when we switch to a 3-point scale, or our validations will be saving the wrong severity! There's a TODO in the code to help locate it. In |
I am pasting screenshots from a thread we had on Slack about the new severity scales. Topics include 2- vs 3-point scales, how the scale might differ for Curb Ramp compared to other label types, and whether to have a severity rating for the Missing Curb Ramp label type. I think that my summary of where we landed on some of these:
|
HI Again, I thought it made sense to continue here. An idea I had yesterday was to use: No issues, Minor Issues, Major Issues for both negative features - the surface problem, obstacle, and regular features: curbramp, crosswalk and ped signal labels. But that for negative features, the 'no issues' is greyed out. This option keeps the consistency well. But could also maybe allow during validation for people to change severity to no issues if they don't think something is an issue...Not sure about that piece, but at least as a whole i think this would be easy to train people on and result in more reliable severity data... Another approach could be to test out two different options with a small set of users? |
I think that if we want to go with a 2-point scale for SurfaceProblem/Obstacle, then this is a nice way to do that!
I think for this we would just have people mark "disagree" instead of changing the severity to "no issues".
I think that you and @jonfroehlich should find some time to sit down together and hash out what the appropriate (and feasible) approach should be! Hopefully before he leaves for vacation on the 22nd since it's at the front of our minds now! |
Interesting idea @yeisenberg! Thanks for sharing it. I need to think about it more... and unfortunately, with deadlines and planned travel, I'm not sure I'll get to this until mid-July (when Mikey will then be on travel). So, perhaps we go with the three-points scale that the students mocked up for now and change it later? |
Not sure what is easier? I just think the low, med, high is still too subjective but for sure can wait until after deadlines/travel. I can ask with others what they think. thanks |
We have long-discussed updating the 5-point Likert rating scale. There are multiple high-level issues here:
Yochai wrote a proposal about reframing the 5-point scales to 3-point to make it easier for the labelers:
He also supplied this handy chart to help us think through this change:
From my perspective, Yochai's proposal is quite interesting but is also oriented around capturing different types of information like "self-confidence in a label" than straight up severity assessments.
I do like simplifying and reoriented the ratings and the idea of capturing different types of ratings depending on whether it is an accessibility feature, accessibility barriers, and missing features.
For the accessibility barrier (what Yochai calls "negative feature"), I wonder if we want
So, that's like a three-point Likert scale.
Additionally, I could imagine collecting "self-confidence" scores for every label (not confident, somewhat confident, very confident); however, that's a lot of extra work. Just thinking outloud...
I do also want to note that across each city and label type, we do see different types of severity distributions. So there is definitely information being captured there:
There are some related tickets where we talk about this, including:
We also talked about validation workflows to validate severity/tags part of labels:
The text was updated successfully, but these errors were encountered: