Page MenuHomePhabricator

Normalize Special: pages for batch delete/undelete and batch moves
Open, Needs TriagePublic

Description

Currently, there is no "fixed" way to bulk [un]delete or bulk move a range of pages or subpages.

On projects like Wikisource for example - admins are frequently faced with the task of deleting dozens if not hundreds of existing pages and/or sub-pages thanks, in some part, to newly discovered copyright verifications as well as vise versa; undeleting a range of pages when new information disproves a previous claim used for supporting a prior deletion. At other times, an alteration to a source file that was previously used to transcribe and transclude a range of Page:s becomes problematic because the existing content no longer aligns with the modified source file's pagination. Without droning on by listing all the other possible scenarios requiring such "Bulk" (or Batch) actions, suffice is to say there is a need for such utility and that utility should be easily usable for any and all who hold the proper bit level.

If everyone cleared to delete or to move pages without creating a redirect can easily perform these functions, then everyone contributing to their respective Wikisource project's can benefit for sure. Wikibooks and Wikiversity may also find these standardized capabilities a plus to have too.

Currently, Special:Nuke is limited to recent creations or creations made by a single active User:. This is of no help when it comes works that have been static for months if not years or enjoys multiple contributions to the work by more than just one editor. When such a scenario requiring "Bulk" action comes to light, requests are documented as best as possible and await for attention by one of the few who are capable of pulling off such feats by scripting, python, tool-labs, wmfLabs and the like to pay a visit. Its not fair to consistently burden the same few individuals with these tasks nor is it efficient to have contributors wait around for 100 single page moves instead of a single job executing 100 moves near at once.

  • The optimal solution would be to design an easy to use Special: page for bulk deletions (and undeletions) and another Special: page for bulk moves that can handle ranges and/or offsets as part of the standard mediawiki core.
  • Next best thing would be to have a way to achieve much the same as the above through local scripting &/or gadgetization instead and preferably without relying in any part on "externals" like labs or tools in the process.

Both seem plausible going by what I can gleam from the Twinkle add-on (see w:MediaWiki:Gadget-twinklebatchdelete.js, w:MediaWiki:Gadget-twinklebatchundelete.js and w:MediaWiki:Gadget-twinklebatchprotect.js among other of its components).

Thanks in advance for any consideration. -- George Orwell III (talk) 02:23, 22 November 2015 (UTC)


  • 2016-01-04.-- FYI... the previous Mass-delete gadget script has been brought back to life & is working again. It builds a Special: page on-the fly (Special:MassDelete) for those with the delete bit and is "torn down" after you leave the page. It can serve as a proof-of-concept for some developer out there at least.

This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey
This proposal received 15 support votes, and was ranked #52 out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Special_pages#Normalize_Special:_pages_for_batch_delete.2Fundelete_and_batch_moves

See also:

Event Timeline

DannyH raised the priority of this task from to Needs Triage.
DannyH updated the task description. (Show Details)
DannyH subscribed.
GOIII set Security to None.
  • The very least someone can do is get the previous gadget for deletions back up and running -- see s:MediaWiki:Gadget-massdelete.js <-- ignore. see below
  • 2016-01-04.-- A FYI... previous Mass-delete gadget script has been brought back to life & is working again. It builds a Special: page on-the fly (Special:MassDelete) for those with the delete bit and is "torn down" after you leave the page. It can serve as a proof-of-concept for some developer out there at least.
IMPORTANT: If you are a community developer interested in working on this task: The Wikimedia Hackathon 2016 (Jerusalem, March 31 - April 3) focuses on #Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please REGISTER NOW.