Wrong user translation suggestions
The duo team have been great at quite promptly adding suggested translations that were missing and reporting back via email. But I haven't been keeping track of all suggestions, and am wondering if they would notify you of a suggested translation that they disagree with and don't add. I'd be fine with that and would see it as a potentially useful learning exercise. Anyone know? Anyone had an email saying their suggested translation was not accepted? I know I made at least one suggestion that I subsequently realised was erroneous but then didn't know how to undo the suggestion.
They only reply to suggestions they now accept and add to the database. It's a big enough job on this Chinese course! We can't expect them to reply to our errors too.
I think they read them very quickly and just filter out the ones that are wrong, so I wouldn't worry about sending them a false report of an error. I know I've sent in a few by mistake.
I disagree with this on the basis of having had extended discussions on the forums here with course contributors about this exact thing. First of all, the contributors have complained about being swamped with wrong or junk submissions.
Second of all, if the backend is developed properly, it would take a few clicks for them to reject a submission. The emails that go out to show you that something was accepted are already automated so it wouldn't add much burden to the site to also auto-generate emails for rejected submissions.
This would then inform the user who submitted it that it was rejected so that they could (a) learn something about the language and (b) refrain from submitting the same report in the future. In the long-run, this could save a lot of time of course contributors.
Also, if people see their sentences are repeatedly being rejected they might get more cautious about submitting them in the future. Perhaps the email informing the user could explain this in a gentle way, thanking them for their contribution but explaining to them that it's important not to overwhelm the team, and to only report things if they're absolutely sure that they are proper translations.
In situations where the rejection was not clear-cut, the backend could allow a "reject without email" button so as to avoid frustration or controversy.
I think this would both improve user experience and help the course contributors to get more done with less work.
Yeah, you're right, and your suggestions are great, but there is still no need to worry about something that can't be undone. I have probably made a few erroneous reports (in good faith, and would love an automated message about the rejection, in order to improve my reporting habits) but I don't think that people mostly making good reports sometimes messing up is the reason the teams are swamped by bad reports. For every time I mess up, I do feel that I owe the team a bunch of good reports helping them improve the course. But if everyone felt like that the good reports would vastly outnumber the bad ones. If that's not the case, others are behaving differently.