Function details: Upon request (when added to the queue page), the bot will "merge" items by copying the descriptions, labels, and sitelinks from the source to the target, considering that the target does not as yet have it's own. In that process, it blanks the source, in order to avoid conflicts when adding to the target. This also means that (for now at least) statements would have been lost (unless manually moved, which would probably be the best option), as well as aliases (I'm not sure how this is updated via the API). For testing so far, I've used User:Hazard-Bot/merge.js as the queue page and inter-used Q4115189 and Q7219409 for the source and target. Currently it only merges items, though I may add property support in the future. Either way, this would help to minimize the issue of duplicated items losing descriptions/labels in other languages, and sitelinks don't have to manually be moved. Upon approval, this would probably have to be run once every 5 minutes the least for best results (to not have to slow down deletion processes too much). Also, I've been concerned about avoiding abuse, which is why I've used a user js page since only admins and the user can edit it, but it might me useful opening it to a wider group of people (still needs consideration). The only simple and flawless solution I have so far would be to use an abuse filter to restrict editing the page (which would have to not be a css or js page).
-- Hazard-SJ ✈ 04:12, 18 April 2013 (UTC)
Comment Good idea, but 'cause of the lack of edit summaries, it'll be difficult to track who stated the merge to be made; I think that we could have, instead, a JS tool (I'm working on it) that could semi-automatically help users merging items.
I think it a problem that moving of aliases, moving of statements and updating of property values in other items are not handled. If it cannot move them, it should at least not at delete them in the obsolete item. I am also concerned about this being doing automatically. Besides intentional abuse, users may type a wrong item number by honest mistake. A semi-automatic tool if available would be preferable. Any news about Ricordisamoa's tool? Byrial (talk) 09:52, 21 May 2013 (UTC)
Those could be fixed ... well I could move the statements too, not sure how to do the aliases via API yet (though I could probably find out, considering it's supported). However, since there is finally some progress on the semi-auto tool, and there is not really any consensus being formed for this request, I'm withdrawing. Hazard-SJ ✈ 23:37, 23 May 2013 (UTC)
The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.