Limit peer review to users above level 5

[nicolas-raoul]

Peer review can not be done by a beginner. It takes quite some experience to know what is on-topic and off-topic, what is a copyright violation or not.

So, I suggest hiding the navigation drawer's "Review" item from users who have not yet reached level 10.

I chose 10 because it is a round number, but I am open to other suggestions.

This means storing the level somewhere when it is retrieved from the server (in the Achievements activity). People who have never opened the Achievements activity will not see the "Review" item, because their level is unknown.

[madhurgupta10]

@nicolas-raoul Instead of hiding, what if we have a dialog which tells the user why he/she can't review, this will motivate him/her to reach next levels quickly :)

[neslihanturan]

This means storing the level somewhere when it is retrieved from the server (in the Achievements activity). People who have never opened the Achievements activity will not see the "Review" item, because their level is unknown.

If we will implement this, we can calculate achievements on background on application start. Or as @madhurgupta10 said, we can inform user. We can first "if you like to discover review item please check your achievement score first, and redirect user to achievements", on next visit if they are under the score inform that why we have such mechanism. If they exceed, let them review.

But this should be designed carefully because saying "you are not eligible to review" may be understood as a rude/annoying expression.

[nicolas-raoul]

@madhurgupta10 Indeed, displaying the button and showing an explanation can be a way to motivate people, indeed. We don't want to make people play the system, though, for instance by uploading 1000 picture of a mushroom and embedding them all in sub-pages of the Swahili Wikipedia, for instance.

@neslihanturan You are right. I am confident that we can do this in a careful way. StackOverflow has tons of level-specific privileges and manages to not make them feel rude. https://stackoverflow.com/help/privileges

[misaochan]

Good idea! But umm, is level 10 a bit high? Maybe 5 or something...? I think you are the only one here who has level 10+, @nicolas-raoul . ;)

[nicolas-raoul]

Yes sure, 5 is probably enough. But if it is only to allow developers to performs tests, then maybe implementing https://github.com/commons-app/apps-android-commons/issues/2861 is safer strategy? :-)

[misaochan]

Not really for the developers, I just thought that 10 is a bit too high. :) Devs can always hardcode or mock their level with the debugger.

[madhurgupta10]

@nicolas-raoul @misaochan Can I start implementing this?

[nicolas-raoul]

@madhurgupta10 Sure, thanks! :-)

[madhurgupta10]

@nicolas-raoul I just need a few clarifications!

When the user visits the Review Activity then we will check if the user level is >=5 if yes then we will let them review. If not then we will display a popup that explains that the user can't review until the profile reaches level 5 and redirects them to Achievements Activity.

When the user visits the Review Activity again and he/she is still under level then we will display the same popup or something else or we will let them review?

[nicolas-raoul]

Good question! The best would be to at first never display the Review item in the left menu, a bit like we don't display it for users who are not logged in. Then each time the user goes to their Achievements and gets their level calculated, you would "unlocked" the feature (allow the review item to appear in the menu, either immediately or next time they open the app).

[madhurgupta10]

@nicolas-raoul Thanks, on it!

[nicolas-raoul]

Variation on this idea:

• Let all users do review
• When a review is done, send it:
  • If the user is over Level 5: to the wiki pages as currently done
  • If the user is below Level 5: to a "flagged" queue on our toolserver
• When a user over Level 5 wants to perform a review, first pull from that "flagged" queue, and only pull from normal if the "flagged" queue is empty.

Problem: It increases the time it takes to get bad images down. So here is a bonus idea:

• For images in the flagged queue, make 2 more users below Level 5 review it, and if more than 24 hours have passed without a user over Level 5 reviewing it.

If toolserver is down or not working, just post the review directly (like currently).

When a user below Level 5 uses "Nominate for deletion" (in Explore>Media details), the picture could be sent to that "flagged" queue.

Current peer review usage

It would be good to get an estimate of how much peer review is actually getting used. We don't track anything, the only thing we can measure might be the deletion nominations tagged as sent by the app.

https://commons.wikimedia.org/w/index.php?namespace=1%3B3%3B5%3B7&tagfilter=android+app+edit&limit=500&days=7&title=Special:RecentChanges&urlversion=2 shows all deletion nomination for the last 8 days, and it contains:

• 1 completely invalid nomination.
• 1 nomination that could be considered valid by some Commons veterans, though I would personally consider it too harsh.
• 1 nomination that is definitely too harsh, but I can see why the nominator thought this way.
• 1 completely invalid nomination though the pic ended up being deleted for another reason.
• A lot of self-deletions, mostly people testing the app.

That's 1 nomination every two days. Given the low threshold of many nominators, I would guess that about 2~5 reviews are made per nomination, meaning 1~10 reviews per day. This is too low to justify a queue system, but we could increase usage by suggesting review when pictures are currently being uploaded.