But if so, there needs to be some criteria for what counts as an abandoned course, and this is where it all gets tricky.
If the creator has not been online for… how long? Weeks? Months? A year?
But the creator can very well be active and using the site, just don’t care about an old project. So how do we measure course creator engagement?
The last time the user logged in to the editing interface? The last time they added an entry or made a change? That’s problematic as well, maybe the course is finished, there is no need for additional levels, and with no obvious platform for feedback (I am not convinced about this new community forum as an alternative) how would they even know that something needs to be fixed?
On the other hand, if someone is active and is constantly developing and caring for their course, it wouldn’t be right for someone else to step in and make changes. (I’d be livid if someone could “fix” my course, and I suspect I’m not the only control freak in the house.) Suggestions? Absolutely. Changes? Absolutely not.
I could imagine a flagging system of suggestions, and if the creator doesn’t respond within a reasonable time (I don’t know how long that would be, two months?) then some public voting could be conducted.
But then again – who would be qualified to vote? And how many votes would you need for a change to come to effect? It would be easy to find users who can speak both English and Spanish and can therefore decide, if the correction is legitimate or not – but how many users are experts in for example Persian and Slovak? Should we need different numbers for different language pairs? That would complicate the scenario even more.
And how would the creator see that something is up? There is no messaging system – something could be added to the editing interface, maybe, but not much has happened on that front lately, (apart from the messing up of the database search.) If tickets come up, there needs to be an interface, where the creator can approve or decline the suggestion, mark it as done, and maybe even reply to the sender.
That all would be an awful lot of developing and coding for a “minor inconvenience” which can be “fixed” by ignoring.
I agree that this is an issue, and a big one at that. I’m just not sure that there is an easy solution. People are annoyed with good reason. But the solution needs to be quantifiable so that it can be implemented automatically, and I’m afraid, this one is just isn’t worth it.