The automation department of WikiProject Swimming uses various automated and semi-automated methods to perform batch tasks that would be extremely tedious to do manually; it collects requests for tasks, discusses whether they are suitable for automation, and attempts to match them with bot operators or users of semi-automated tools for implementation. All project members are invited to request tasks and to comment on the suitability of outstanding requests.
The current scope of WikiProject Swimming is quite extensive and covers many of articles. These articles must be tagged, their infoboxes replaced or deprecated, and so forth. Given the sheer number of articles, it is quite tedious to do these things by hand; therefore, various automated or semi-automated processes must be set up to perform these maintenance tasks.
Depending on the nature of the task, it can be either completely automated and run by a bot, or semi-automated via AWB, requiring a user's decision to whether or not implement the changes. Indeed, in order to minimize false positives, some of the operations should be performed by hand.
Rules of thumb:
A task is a maintenance operation that can be executed on a precise set of articles. It can be identified by several parameters:
Note: "non-recurrent" tasks should actually be reperformed once every few months, to take into account new articles created on the subject. However, moving a finished non-recurrent task back to unassigned will be done at discretion of the project coordinators.
When a task involves tagging articles from a stub tag and automatically rating them as "Stub-Class", the auto parameter in {{ WP Swimming}} must be set:
{{WP Swimming |class=Stub |auto=yes ... }}
Please add a brief description of the proposed task below; once it has been determined that it can be safely carried out, and that there are no objections to doing so, it will be moved into the tables above.
All project members are invited to comment on these requests—particularly if they notice any problems with the proposal!
The automation department of WikiProject Swimming uses various automated and semi-automated methods to perform batch tasks that would be extremely tedious to do manually; it collects requests for tasks, discusses whether they are suitable for automation, and attempts to match them with bot operators or users of semi-automated tools for implementation. All project members are invited to request tasks and to comment on the suitability of outstanding requests.
The current scope of WikiProject Swimming is quite extensive and covers many of articles. These articles must be tagged, their infoboxes replaced or deprecated, and so forth. Given the sheer number of articles, it is quite tedious to do these things by hand; therefore, various automated or semi-automated processes must be set up to perform these maintenance tasks.
Depending on the nature of the task, it can be either completely automated and run by a bot, or semi-automated via AWB, requiring a user's decision to whether or not implement the changes. Indeed, in order to minimize false positives, some of the operations should be performed by hand.
Rules of thumb:
A task is a maintenance operation that can be executed on a precise set of articles. It can be identified by several parameters:
Note: "non-recurrent" tasks should actually be reperformed once every few months, to take into account new articles created on the subject. However, moving a finished non-recurrent task back to unassigned will be done at discretion of the project coordinators.
When a task involves tagging articles from a stub tag and automatically rating them as "Stub-Class", the auto parameter in {{ WP Swimming}} must be set:
{{WP Swimming |class=Stub |auto=yes ... }}
Please add a brief description of the proposed task below; once it has been determined that it can be safely carried out, and that there are no objections to doing so, it will be moved into the tables above.
All project members are invited to comment on these requests—particularly if they notice any problems with the proposal!