You do have a valid point about getting the local community exposure to Wikidata. But I see no contradiction between that and my proposal, because I think it would be very easy to come up with countless Wikipedia/Wikidata cleanup tasks that require human attention. There is always be plenty of work. After my program runs, there will be thousands of items that could not be resolved as easily. For example, there will be tons of cases when wikipedia and wikidata point to different entities. Some of them are legit - e.g. island (wikipedia) vs administrative area (wikidata). Redirect resolution would not introduce communities to wikidata, but rather teach community how to mindlessly click "accept", and I would much rather avoid that - as this might result in bigger problems when a real decision needs to be made.
On Tue, Sep 26, 2017 at 1:04 AM, Marc Gemis <marc.ge...@gmail.com> wrote: > By using Osmose, it would be possible to involve the local > communities. People would learn about Wikidata, and might start adding > them to other objects as well. They might even start contributing to > Wikidata as well. > By just running your program, you would only fix a small number of > entries and nobody would know, nobody would bother about them. > > I have the feeling that a program can fix some errors in a short > period, but doesn't bring anything else. Allowing people to fix > trivial problems, allow them to get familiar with the data, they will > take some form of ownership and maintain the data and that is more > beneficial in the long term than an automated quick fix now. > > m. > > On Tue, Sep 26, 2017 at 5:53 AM, Yuri Astrakhan <yuriastrak...@gmail.com> > wrote: > > According to Martijn (of MapRoulette fame), there is no way a challenge > can > > link to object IDs. MapRoulette can only highlight location. Nor can I > > provide a proposed fix, which means someone would have to manually find > the > > broken object, navigate to Wikipedia, copy/paste the title, and save the > > object. I guesstimate 1 minute per object on average... that's nearly > 700 > > hours of community time - a huge waste of human brain power that could be > > spent on a much more challenging and less automatable tasks. > > > > Osmose might be a good alternative, and might even lower the total > number of > > hours required, but still - would that significantly benefit the project? > > These tags are just a tiny arbitrary subset of one million > wikipedia-tagged > > objects. Verifying just them by hand seems like a waste of human > > intelligence. Instead, we can run queries to produce knowingly bad > objects > > and let community fix those. I hope we can let machines do mindless > tasks, > > and let humans do decision making. This would improve contributors > morale, > > instead of making them feel like robots :) > > > > Clarifying: the OSM objects already point to those pages via redirect. > The > > redirect information is only stored in Wikipedia. > > > > On Mon, Sep 25, 2017 at 11:18 PM, Marc Gemis <marc.ge...@gmail.com> > wrote: > >> > >> or via Osmose ? > >> > >> On Tue, Sep 26, 2017 at 5:16 AM, Marc Gemis <marc.ge...@gmail.com> > wrote: > >> > what about a Maproulette task ? > >> > > >> > On Tue, Sep 26, 2017 at 5:11 AM, Yuri Astrakhan > >> > <yuriastrak...@gmail.com> wrote: > >> >> At the moment, there are nearly 40,000 OSM objects whose wikipedia > tag > >> >> does > >> >> not match their wikidata tag. Most of them are Wikipedia redirects, > >> >> whose > >> >> target is the right wikipedia article. If we are not ready to abandon > >> >> wikipedia tags just yet (I don't think we should ATM), I think we > >> >> should fix > >> >> them. Fixing them by hand seems like a huge waste of the community > >> >> time, > >> >> when it can be semi-automated. > >> >> > >> >> I propose that a small program, possibly a plugin to JOSM, would > change > >> >> wikipedia tags to point to the target article instead of the > redirect. > >> >> > >> >> Thoughts? > >> >> > >> >> _______________________________________________ > >> >> talk mailing list > >> >> email@example.com > >> >> https://lists.openstreetmap.org/listinfo/talk > >> >> > > > > >
_______________________________________________ talk mailing list firstname.lastname@example.org https://lists.openstreetmap.org/listinfo/talk