User:Krinkle/Tools/Commons Upload Patrol
|This is kept for historical interest. Any policies mentioned may be obsolete. If you want to revive the topic, you can use the talk page or start a discussion on the community forum.|
Commons Upload Patrol (or CUP) was a system that provided upload patrolling functionality to Wikimedia Commons. It was hosted on Toolserver and had a "Recent uploads" page that could be sorted by time and viewed either chronological (oldest first) or reverse-chronological (newest first). For patrollers, it offered the ability to see the current patrol status, and mark an upload as patrolled with a single click.
- Paste this code in your common.js:
- Done :-)
If nothing appears, be sure to verify that you've put the above code on the wiki you use the tool on, not per se here on Meta.
Also clear your cache and do a hard refresh. If you encounter any issues, please let me know!
How to clear cache
Note: After saving, you may have to bypass your browser's cache to see the changes.
Anybody can view the tool's main page with the list of uploads and can use the filter options From:, Untill: and Reversed. However, you need to be logged in to see the patrol status of uploads on both the tool page and File-description pages, to mark an upload as patrolled, and more. Authentication is done through TUSC. Access is allowed to anyone who has the 'patrol' right on Wikimedia Commons (user group: administrators or patrollers). You can request the patroller right here.
Once you are logged in, you can visit any File-page and the Patrolstatus box should show up on the top right indicating the current status and/or allowing you to patrol it.
If you're not sure where or how to start patrolling, visit the Recent uploads patrol-page on Commons. Once you are on that page, click on any of the CUP-permalinks below each day-section. Those links take you to the CUP-tool showing only uploads during that time frame and will hide any patrolled uploads as well. Eventually, the list will be empty and ay "No more unpatrolled uploads in this timeframe" - this means that portion is now done and you can move on with another one.
In the sidebar next to Recent changes is a link added for Recent uploads. This takes you to an overview of recent uploads sorted by date. This list can be filtered, sorted and timeframed. Example with all settings used: All unpatrolled uploads between 3 and 4 AM on October 18 in chronological order from old to new.
The recent uploads module takes url paremeters
untill as a 14-digit timestamp (YYYYMMDDHHIISS). Shorter is allowed, and will be zeropadded to the right to fill up to 14 digets. (ie.
from=2010110304&reverse=on will show uploads starting from 4:00 AM on November 3, 2010). At any time you can click, copy, bookmark or share the "Permalink to this page" link that will represent the current settings. Logged in patrollers can also filter out patrolled uploads
- » uploads between 16:10 and 16:20 on November 2, 2010
- » unpatrolled uploads between 16:10 and 16:20 on November 2, 2010
When you view a filepage of an upload, a box line one on the right here appears on the top right of the page. If the upload is patrolled it tells when and by whom the upload was patrolled, otherwise it's a link to mark the upload as patrolled. Alternatively it might show a short message saying the upload is autopatrolled (such as uploads by bots, sysops, autopatrollers, patrollers, Image-reviewers etc.)
The little " next »"-links redirect you to the file page of the oldest unexpired unpatrolled patrollable upload. The " skiip »"-links add the current upload id to a memory that will be checked whenever you click "next »". This can be handy whenever you encouter something you'd like to skip, however with only "next" you'd get the same one over and over again, with "skip" you can store a large amount of upload-ids in the session memory so that whenever you click "next" it will pick the oldest unpatrolled patrollable upload, that is not any of those that you have added to the skip-memory.
Editnotice and FixFile script
On filepages the editlink will be extended with an editnotice. Once clicked the editnotice will show. The static content of the editnotice is located at commons:User:Krinkle/FixFileEditnotice. Several parts of the messages are enhanced and added by the script. One of the added enhancements is as a button to automatically perform several fixes such as replacing headings with their localized versions (
If a certain user has uploaded many similar images that all need the seem 'treatment', you can enter the username in the Userfilter to only show uploads of that user. Together the "Hide patrolled uploads" and the "arrow buttons" on the bottom right of the Shadowbox this can be used to go through a series of images and edit them all the same way in a row without being interrupted by other images and without seeing the same image twice.
If a certain user uploaded many similar images that are all good to be patrolled, you can do the above in combination with MassPatrol to patrol all the uploads currently on the page with the push of a button. If a user seems experienced enough in general and not just for a series of image that are 'good', you may want to consider requesting the user to be autopatrolled. Beware though that this also affects edit patrol and new page patrol, so the user should be fairly experienced and not need patrolling of any kind.
MassPatrol will mark all the uploads currently on the page as patrolled. To avoid unrevertable mistakes and abuse this option is only available if atleast 1 filter is applied (currenltly: Userfilter).
To enable one or more of these options, copy the line to your vector.js *before* the importScriptURI-call.
- Mark FixFile-actions as minor edits
window.CUP_Option_FixFileMinorEdit = true;
- Suppress the confirmation dialog when patrolling uploads
window.CUP_Option_SkipConfirm = true;
|2010-11-29 - 0.2.7||
|2010-11-27 - 0.2.6||
|2010-11-26 - 0.2.5||
|2010-11-19 - 0.2.4||
|2010-11-18 - 0.2.3||
|2010-11-16 - 0.2.2||
|2010-11-12 - 0.2.1||
|2010-11-06 - 0.2.0||
|2010‑11‑02 ‑ 0.0.1||