|On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2015/08.|
gerrit:116297 enables a new and easier way of merging items via the Wikibase API. You can write e.g.
pywikibot.ItemPage(site, id).mergeInto(pywikibot.ItemPage(site, otherId), summary=u'duplicate item')
Subject matter restrictions on bots
What would be the appropriate policy or guideline to add subject matter restrictions on bots? One restriction that I believe should exist is that since dates in Wikidata are by default in the Gregorian calendar, bots should not extract any date from another source (such as Wikipedia) and add it to Wikidata unless the bot has a mechanism to confirm the date is stated in the Gregorian calendar. One such mechanism would be to check that the date is in the year 1924 or later, since Greece was the last country to switch from Julian to Gregorian, and that was in 1923. Jc3s5h (talk) 15:54, 25 August 2014 (UTC)
Mass-undo / mass-revert?
As we all know, mistakes can and will happen. Instead of merely delegating this issue to clean-up jobs after the fact, should it not be feasible for a Wikidata bot to itself undo what it has done? The structured data approach should entail that Wikidata is the ideal place for this kind of approach. (Although I admittedly have a limited knowledge about bot implementation, I haven't yet seen this kind of bot behavior when mistakes do happen; more often than not, semi-manual cleanups seem to be needed after mistakes occur.) -- Therefore, I would like to suggest making it a requirement for any bot that it is able to undo its last edit to any given item. (There could, for example, be a requirement that it should be able accept a list of items IDs plus a filter argument, e.g. how many of its own last edits to undo, or a date cutoff point for indicating 'all my edits since a particular date'.) Such a requirement could be adopted both in the bot approval process, making it a requirement for bot adoption, as well as in the underlying software. So what do you think, is this possible currently, or would it require some changes to the API or underlying software before it is possible to realize such a level of control? If it is already possible, or in the works, that would of course be great! Fred Johansen (talk) 17:22, 7 December 2014 (UTC)
- This seems like a good idea. It's also needed for Widar; see e.g. User_talk:Yamaha5#instance_of_.28P31.29. Emw (talk) 18:54, 7 December 2014 (UTC)
GZWDer (flood) flooding to much !
Firstly, this bot do not have a "proper" bot user page (with a "stop me" link). Secondly what exactly do this bot is not realy clear appart from "semi-automatic tasks" (witch is obvious for a bot).
This bot have many problems in the past :
- Creating duplicates, and so giving lot of manual chek. The reply of the user were "You can manually merge them" and "Duplicates can not be prevented".
- Made items with no labels. The user have just replyed than another bot (Dexbot) will correct his own bot.
- Create a bunch of wikidata stub entries without even speaking first to the related community. No reply yet.
- There are many such bots without "stop me" in Wikidata. I own one too. It is obivious that bots create duplicate items, those should have been connected before they were imported. AFAIK noone has to ask any project if they may create items for their pages. (I haven't seen such case since Wikidata was launched.)
- So do you want to stop them all? Matěj Suchánek (talk) 12:52, 30 March 2015 (UTC)
- That's not only the missing button but the way to use the bot. If you run your bot in a correct way the button is not needed but when you do thing without any agreement with the persons involved in the topic and if your bot is doing mass bad edits, the button is becoming a problem. Snipre (talk) 13:06, 30 March 2015 (UTC)
- The problem of duplicate items is mostly resolved by the addition of "Do not create item if label/alias exists" in https://tools.wmflabs.org/wikidata-todo/creator.html; old duplicate may be merged by Merge game, User:Pasleim/projectmerge or yichengtry (currently broken).
- https://tools.wmflabs.org/wikidata-todo/creator.html will not automatically add labels to created items for non-Wikipedia wikis. If no bot will add labels, I must do it manually. But Dexbot will (See an random example). also other bots may also do it.
- Items are notable as long as they meet Wikidata:Notability and there're no consensus against creating them. Not validated pages may have items as long as they are not deleted because abandoned, like stubs in Wikipedia. Add statements is a very long process to do.
- Dispatch issues is because of a bug in Wikibase software, now fixed.
- there is a very big difference between wikipedia projects and wikisource projects : wikisource has very few contributors, and there is a reflection in progress about how to import texts, and exactly which texts are to be imported to wikidata : books, obviously... but for chapters, it's less obvious, and for pages it is clearly "N/A". Besides, the technical structure of wikisource is very different from that of wikipedia…
- tonight I had to ask deletion of more than 120 pages from a book, that you imported, because these were not entire text, but text of single pages, that could not be put in Page namespace for technical reason…
- besides, there is a need for data to add properties, that are much more difficult to get than from wp, because of transclusion that does not allow visualisation in wd, and categories are much less developped… all the work afterwards has to be made by hand and cannot be automated, which makes large blind imports very uneasy to manage…
- there is absolutely no urge to import all wikisource very quickly, especially if items stay without claims for months (or years), because there is noone to document them… a systematic import, by author for example (or by source for articles of periodicals), is more efficient and easier to document afterwards…
- The consensus of wikisource projects is to import validated texts first, then corrected texts, and then see for the others… you imported blindly, when we were working on tools to do it properly, which is why I am so irated about your bot… it works randomly, in languages it does not understand… that's crap… :(
- if GZWDer just does not understand what he does, at least, just stop importing from wikisource… let ws-contributors work on it, as they are now, and let them do it properly - thanks --Hsarrazin (talk) 22:56, 13 May 2015 (UTC)
- Properties can be added by autolist, and in the future by bot; but autolist doesn't create any new items
- Already stopped importing from Wikisource but Dexbot will still create items for new Wikisource pages (while many items for old pages were created myself)
BREAK - Deprecation & Removal of the ungroupedlist API parameter
The ungroupedlist api parameter will be deprecated from the wbgetentities and wbgetclaims modules on Wikidata as of the next deployment on Wednesday 29th July.