-
Notifications
You must be signed in to change notification settings - Fork 50
Implement feature "revision.is_patrolled" #67
Comments
A query like |
Considering that
I think having a feature like this for training a machine learning algorithm might incorporate useful information, even if only for relatively old revisions (which are of interest in use cases such as "get a list of likely bad edits which were not reverted so that I can review them") |
Assign to me. Claiming task. :-) |
I don't think that this feature is a good idea. It's not a stable characteristic of the edit. If we're going to put this anywhere, it should be in the |
Essentially the idea is that if an edit is not reverted and it is patrolled, we can conclude that it is a good edit (not damaging) saved in goodfaith. Does that sound right? |
Yeah, that makes sense. |
Given a revision id, "revision.is_patrolled" would return True if there is a log entry saying that this edit was patrolled by some user, and False otherwise.
I believe this would mostly solve Nemo's concerns about reusing the data already provided by recent changes patrollers (on wikis where this MW feature is enabled):
https://meta.wikimedia.org/w/index.php?title=Grants_talk:IEG/Revision_scoring_as_a_service&oldid=10089505#Existing_tool
The text was updated successfully, but these errors were encountered: