What to do when a dance is wrong

[cranhandler]

User enters dance.

Dance is incorrect.

Civilian notices dance is incorrect. What can the civilian do?

My proposal: implement a "broken" tag. This tag jumps to the top of any list of tags.

The tagger enters a couple words about what's wrong missing ladle ricochet in A1 or spelled choreographer wrong or there is no B2 in this dance?

These words are visible to other users (so another caller can see spelled choreographer wrong and call the dance anyway, or see no B2 and choose not to call it

The dance owner gets an email saying somebody noticed an issue in your dance. It was [words]. Can you log in and resolve the issue? If we don't hear from you in 1 week, admins may edit your dance or make it private.

http://contradb.com/dances/129 SHOWS

A1	hey, gentlespoons lead passing left
A2	neighbors gyre meltdown and swing
B1	long lines forward
	gentlespoons roll away neighbors with a half sashay on the way back (roll right to left)
	mad robin, gentlespoons in front for 8 (CCW around current neighbor, facing partner)
B2	progress to new neighbors
	circle left 3 places for 6
	partners swing for 12

Per video of dance owner calling, and per choreographer text confirmation, http://contradb.com/dances/129 SHOULD SHOW

A1 | hey, gentlespoons lead passing left | at last pass, ladles ricochet back to neighbor A2 | neighbors gyre meltdown and swing B1 | long lines forward   | gentlespoons roll away neighbors with a half sashay on the way back (roll right to left)   | mad robin, gentlespoons in front for 8 (CCW around current neighbor, facing partner) B2 | progress to new neighbors   | circle left 3 places for 6   | partners swing for 12

[dcmorse]

Great ideas!

• Yes and: implement it as a 'flag broken' button right up with 'copy dance': take you to a separate screen, and you can enter the text (about a [3])
• Yes and: implement it as a 'suggest edit' button right up with 'copy dance': it opens up the dance editor with a fresh copy of the dance, with a 'summary of changes' line too. The dance is marked private by default, and when Person2 saves it, a new button appears on Person1 dance show page: [Review Edit by Person2]. They click it and the dance editor opens up yet again, with Person1's edits loaded. It'd maybe be possible even to highlight the differing fields, but let's not go nuts.

[cranhandler]

Item 1: I don't think it belongs front and center. Dances with issues will happen uncommonly, and we don't want to encourage over zealous reporting. Simply including it among possible tags (making it the trial balloon of tags?) should be the Goldilocks level of visibility.

Item 2: this sounds like vigilante justice, and is too likely to cause inter user dissention. Enough characters to explain the issue is educational without being pushy.

Ideally the user understands and fixes the issue. Or, the user doesn't log in, and admins fix the issue. I think we need to have admins be the sheriffs, not assorted users

[dcmorse]

Regarding Item2: Yeah, but we as adminstrators sure would like to see Item-2, even if it's admin-only for the people suggesting the changes. It'd make these chet situations easier. If the item goes unaddressed for a week or something, we just accept our proposed changes. Bam! Only one hard touch per dance. Labor saving!

[cranhandler]

This is largely resolved by https://github.com/contradb/contra/issues/364

But some dances remain broken for users who have not yet selected a preference. Until we implement tags, switch them to private and mark here for future audits.

• [ ] Danner's Trip to IHOP http://contradb.com/dances/378