Manage inappropriate answers (add flagging, automatic hide, manual show/hide)

[xcompass]

A concern was raised about giving staff the ability to remove answers from the pool that they consider to be inappropriate.

[idoroll]

This should potentially include a flagging mechanism.
I did not anticipate this being an issue, but apparently it is.

[lenglund]

Instructors will have to manually deal with the flagged answers.

[jleong-openedx]

LMS View

• display clickable flag icon/image next to each rationale by other students
• allow some way to undo this flagging (if I made a mistake)

Studio View (also applies to LMS view for staff only)

• display clickable "Manage Flagged Answers" button (similar to existing "Staff Debug Info" button)
• display list of flagged answers with counts and status (shown or hidden), with scroll bar, on-click of "Manage Flagged Answers" button
• display clickable "show/hide" text next to each displayed flagged answer
• remove the appropriate response from the pool on-click of "hide"
• add back the appropriate response on-click of "show"

Other

• set threshold of 5 flags to auto-hide answer

[idoroll]

LMS view - should students be asked to confirm flagging? Studio view - will instructors have a chance to see (and vet) all rationales, not only flagged ones? Probably worth doing.

…

On Wed, Aug 23, 2017 at 4:05 PM, jleong-openedx ***@***.***> wrote: LMS View - display clickable flag icon/image next to each response by other students - grey out and disable clickability of flag on-click Studio View (also applies to LMS view for staff only) - display clickable "Manage Flagged Rationales" button (similar to existing "Staff Debug Info" button) - display list of flagged responses, with scroll bar, on-click of "Manage Flagged Responses" button - display clickable "x" image/icon next to each displayed flagged response - remove the appropriate response on-click of the corresponding "x" — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKEQMPwSqSUuwn_kA8fI4zYp9aeS4TwFks5sbLArgaJpZM4HX7hN> .

[lenglund]

Brought up at brown bag session. Concern is that instructors do not have time to monitor all answers, so crowd-sourcing this to students may make sense. However, no one at the brown bag had actually experienced this as a problem IRL.

[idoroll]

I would think that we can implement flagging twice = removal. Better err on that side. In a MOOC setting, so many answers, okay to remove a few innocent ones. In edge setting, I am less concerned about flagging.

…

On Thu, Nov 9, 2017 at 2:32 PM, Letitia ***@***.***> wrote: Brought up at brown bag session. Concern is that instructors do not have time to monitor all answers, so crowd-sourcing this to students may make sense. However, no one at the brown bag had actually experienced this as a problem IRL. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKEQMOT1HlVwhkM5XNP9QaniNU7PkFJDks5s032IgaJpZM4HX7hN> .

[jleong-openedx]

@idoroll We should bring that up for discussion at our meeting (with Letitia, Pan, and Derek) on January 10.

[lenglund]

Instructor/instructional team preference seems to be: allow students to mark answer as inappropriate, automatically remove this answer after hitting a set threshold (we determine), but allow instructional teams to also show/hide answers in the pool manually (e.g., provide UI that shows any flagged answers, their show/hide status, and a way to switch between).