TextMatchEditCheck is an existing experimental check that we've been using for testing / demos, mostly as an example of a non-AI pseudo tone check ("unfortunately").
It lets you configure rules in its config section in MediaWiki:editcheck-config.json for what to search for, which it internally calls replacers. Despite the name, the only action it allows you to take is to delete the matched content.
Stories
As a technical contributor to Wikipedia motivated to improve the content of Wikipedia, I would would value making people who are editing aware of the text deletions and replacements they could consider making in an easeful and structured way so that I can scale the impact I can have on improving the quality of Wikipedia's content.
Requirements
MVP
- Provide more actions that can be taken upon a match
- Pure notifications, that just offer a "dismiss"
- Replacements (see: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/1136408 which is a WIP patch that made a basic replacement check as a base for a british english check)
- Delete <-- current sole option
- Allow replacers to specify their own visibility config, which would be any of the generic config supported by BaseEditCheck (e.g. account status, edit count, category, template on page, namespace, specific page-name, etc.)
- Enhance the way "dismiss" works so that if you dismiss one specific instance of a suggestion within a specific range (e.g. replace "color" with "colour" in the lead section of the Double-decker bus article) it does not dismiss other instances of other text suggestion matches within the same range
Original list
- Provide more actions that can be taken upon a match
- Pure notifications, that just offer a "dismiss"
- Replacements (see: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/1136408 which is a WIP patch that made a basic replacement check as a base for a british english check)
- Delete <-- current sole option
- Make replacer pattern-matching more sophisticated by giving users a way to provide regular expressions as well as just literal strings.
- Allow replacers to specify their own visibility config, which would be any of the generic config supported by BaseEditCheck (e.g. account status, edit count, category, template on page, namespace, specific page-name, etc.)
- Also, implement some of those visibility config settings mentioned above
- Enhance the way "dismiss" works so that dismissing one replacer won't dismiss all textmatch checks
- Let users specify the severity for a specific replacer rule?