Skip to content
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

Report that Nearby item is not at specified location #965

Closed
nicolas-raoul opened this issue Nov 16, 2017 · 10 comments
Closed

Report that Nearby item is not at specified location #965

nicolas-raoul opened this issue Nov 16, 2017 · 10 comments

Comments

@nicolas-raoul
Copy link
Member

nicolas-raoul commented Nov 16, 2017

Sometimes Nearby makes me go to a place, and I realize that there is nothing, for instance it was supposed to be a museum but it is just fields. This probably happens to any regular Nearby user.

This leads to frustration, and if nothing is done the point stays on the Nearby map, and another person (or forgetful me) might be tricked by it again.
But this could be turned into a very positive experience that benefits Wikidata: Let the user report the point.

Implementation could be a "Report" button that proposes:

  • The item is not found around that point
  • The point is a bit further
  • The item does not exist anymore at that place

Feedback could be appended to a particular Wikidata maintenance article such as https://www.wikidata.org/wiki/User:Syced/Commons_Mobile_App

@janpio
Copy link
Contributor

janpio commented Nov 16, 2017

How is such "maintenance" done in Commons itself, outside the context of the app?

@nicolas-raoul
Copy link
Member Author

commons.wikimedia.org does not even have a Nearby feature, actually.
This is Wikidata maintenance rather than Commons maintenance, within the purpose of adding missing content to Commons.
The same concept could probably be used for OpenStreetMap points, though.

@janpio
Copy link
Contributor

janpio commented Nov 16, 2017

Yeah right, I was wondering how they normally do the "Oh, I noticed this data/entry is wrong, let's fix it" process.

@misaochan
Copy link
Member

@nicolas-raoul Sounds good, but if we do that we probably need someone to consistently check that article and make the necessary modifications, otherwise they may get even more frustrated. :) I don't think the regular Commons/Wikidata volunteers will be willing to do it.

@nicolas-raoul
Copy link
Member Author

@misaochan I volunteer to monitor that page, fix what I can, and announce the rest on Wikidata's project chat :-)
I guess it will not be more than 50 reports a month anyway, even when the app becomes very popular.

@misaochan
Copy link
Member

Thanks @nicolas-raoul ! :) So implementation-wise, we are really just talking about a link that takes the user to https://www.wikidata.org/wiki/User:Syced/Commons_Mobile_App , right?

@nicolas-raoul
Copy link
Member Author

Actually, I was thinking about a UI with radio buttons letting the user choose what the problem is.
This UI would automatically post a message on the wiki page above in the user's name, including the item's identifier and the selected problem.
That forces the user to include the reason of the problem (some users would just say "It does not work").
Another advantage is that it writes reports in English. The UI would ideally be translated to the users' languages.

@Rishavgupta12345
Copy link
Contributor

@nicolas-raoul @4D17Y4 According to https://github.com/commons-app/commons-app-documentation/blob/master/android/Students.md can i consider this project to work on in GSOC 2022 ?

@nicolas-raoul
Copy link
Member Author

@Rishavgupta12345 If for any reason you are strongly motivated by (#953 + #965), you can choose it. But otherwise I would suggest #4764.

@nicolas-raoul
Copy link
Member Author

Duplicate of #2425

@nicolas-raoul nicolas-raoul marked this as a duplicate of #2425 Aug 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants