-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow users to rate pictures in their area #2068
Comments
Rating pictures is an good idea by this we can also remove images which are not of any use or if someone has uploaded his or her photo |
Currently, do we have such an API? |
Structured Commons will introduce a "Quality assessment" property for each media. Also, let's add a "thank" to the picture if the number of stars is 4 or 5. |
Is it the same as #2386 ? |
@vanshikaarora Yes both issues are about Mediawiki's "thanking" feature. The present issue would give a thank, whereas the issue you mention would receive the thank :-) |
That would be a great idea so currently shall we include the rating widget to the images in explore? |
Good question. I have not though about the UI. If we mix featured pictures with normal pictures, users might rate normal pictures very harshly. Which might not be a problem, we could just maintain the user's medium rating for non-featured pictures, and apply a multiplication. Maybe this activity could be sort of grouped with the peer review activity? Peers in the sense of mobile app users, and peers in the sense of same area. A "Peer review" item in the left menu would be acceptable. Have you found the API that gives pictures in a current area? You can find it by looking at the JavaScript client-side code of https://tools.wmflabs.org/wikishootme/ |
@nicolas-raoul where should the rating icon be added? |
Well, the idea is commendable :)
@nicolas-raoul "left-menu", is that navigation drawer? |
Ah yes, navigation drawer is the right word, thanks! |
@nicolas-raoul Currently the "Peer-review" activity is will be showing a list of images along with their rating or is it something else? |
There are several ways to implement this. |
@nicolas-raoul Since currently we don't have the server-side ready. Shall I start with option A |
Yes if you want :-) |
For the UI, how about this:
|
The same feature should also be available in the media details as double-tap too, and in the media details' menu (along with Download) for discoverability. |
Sure :)
One point of suggestion here, user's might not know about this double tapping feature. So either,
Please share your opinion @nicolas-raoul :) |
A rate icon near the download icon or inside the menu in the media details would be good, I think. |
Ok I'll add the rate icon in the media details 👍 |
Task List for me:
|
@nicolas-raoul As discussed here. Currently we do not have the an API to write media talk page. Task 2 in my work list shall be kept on hold. Please correct me if I am wrong :)
Is it like sending a thanks to the editor of the picture? |
Talk pageI think this is the API to use to edit any wiki article (which includes Commons talk pages): ThankThe app must thank the wiki edit which is the upload of that media. Just like clicking the "thank" link at https://commons.wikimedia.org/w/index.php?title=File:Baragazza_vista_del_centro.jpg&action=history : |
Do we need to further editing on this PR? Or it is sufficient to be merged with my branch? |
That PR will get more commits, but even now it should be enough to edit talk pages I believe. |
@nicolas-raoul So shall I merge the PR in it's current state with my branch? |
Yes, merge that PR into your branch. |
Was this implemented? |
@misaochan Not really. Thanks were implemented, by not "in your area". Maybe it could be another tab in Explore, after "Mobile uploads"? I suggest abandoning the idea of star rating for now, and instead making any picture targetable for "peer review", where the user can either thank or tag any problem. |
This would be fantastic IMO. :) |
From http://www.opensym.org/wp-content/uploads/2018/07/OpenSym2018_paper_30-1.pdf :
The text was updated successfully, but these errors were encountered: