Feature summary:
Allow sysops and/or bot operators to retroactively mark existing edits as bot edits, either individually or in bulk. I'm not sure how to describe the implementation, but I will try in these ways:
- For a Few Edits:
- Introduce an action link or checkbox next to each edit in the revision history and contribution page to toggle the bot flag.
- For Bulk Edits:
- Implement a dedicated form in the wiki's administrative interface.
- Options include specifying a time range and applying the bot flag to all edits within that range associated with a specific bot.
- (Optional) additional customization (e.g., excluding a range of timestamp or using a list of oldid) ensures efficiency.
- For Developers:
- I think this will be the best and fastest way if we be able to fetch Quarry results and apply them. I highly prefer this.
Use case(s):
- A bot operator or sysop discovers that a series of edits made by a bot were not initially marked as bot edits. This may be due to software bugs or bot operator oversight resulting in a cluttered Recent Changes page. This Quarry query is my case.
- Sysops can designate specific edits for organizational purposes.
- Users with 'rollback' and 'markbotedits' permissions can mark rollbacks and associated edits as bot edits.
Benefits
- Enhanced flexibility for users to adjust the bot flag for edits.
- Improved organization of edits, maintaining a cleaner Recent Changes page.
- Consistency in marking edits as bot edits ensures accurate tracking and analysis.