Page Curation/Zoom interface
Note: this page is absolutely a work in progress. There are no screens at this time; I wanted to get the text out first.
Zoom will grant users the ability to add individual articles to various queues for later processing. These queues can then be viewed or read independently with the assumption that all articles within the queue meet certain criteria.
Ideally, the queues can be configured by the community. New queues can be created as needs arise. This is actually the central function of the Zoom triage system: moving articles into queues which will be processed by those more experienced in certain areas.
Queues are ideally used by inexperienced reviewers. For example, a reviewer may be uncertain about an article's notability: it reads like a good article, but the topic may be overly promotional.
Adding an article to any queue requires a comment as to why it was placed into a specific queue. For example, a user may leave the comment "includes a phone number" when pushing an article into the "Oversight" queue.
Articles may be added to multiple queues.
Articles may be removed from a queue at any time. Deleting the article will also remove it from any queues it is a member of.
Ideally, there will be the ability to for trigger events to fire when an article is placed within a queue. For example, if an article is placed into the "Oversight" queue, a trigger event could be that the article is automatically hidden from everyone except for those with oversight ability. These people may then run the "Oversight" queue and restore visibility of the article if its placement is unwarranted.
Ideally, reviewers will be able to "watch" existing queues. When an article is placed into one of the queues (such as the Oversight queue), they will be notified of the event and will be able to take immediate action.
By default, Zoom will place the reviewer into the "Unreviewed" queue. This queue contains all articles that have not been marked as "patrolled" or "reviewed".
However, the reviewer may, at any time, switch queues to review articles within those queues.
Note that an article may remain in other queues (and be visible via Zoom), even if it has been removed from the "Unreviewed" queue.
The following queues are probably essential.
This is all articles that have not been reviewed. It is analogous to the "patrolled" flag that is currently used.
Articles placed into this queue have been deemed "promising" by the reviewer. This queue can be used by anyone to help make the article better.
This queue is for articles that require oversight. These articles are may contain personal information, for example, and the reviewer may not have the rights to change the revision visibility.
This queue will be useful to oversighters who have subscribed to it.
Zoom can be configured to utilize different "toolsets". A toolset is a palette of actions or activities. For example, Zoom will ship with two toolsets: basic and advanced.
Ideally, toolset construction can be handled by the community, who may add or remove actions (or even new toolsets). There is a problem, however, with additional toolset bloat (too many toolsets become a usability problem).
Toolsets should also be "rights aware". That is, some functions should be available to administrators or those with oversight abilities, and not be displayed for those who do not have these rights.
A possible future toolset could be created for image reviewing.
The basic toolset is designed for new and inexperienced reviewers. This toolset is extremely simple and designed primarily for triage and not tagging. It is also intended to help train newer reviewers and not to overwhelm them with internal jargon (such as deletion criteria).
The basic toolset will, in many instances, ask simple yes-or-no questions of the reviewer. "Is this article spam?" or "Do you think it should be deleted?". Some questions may have additional questions: "Why do you think it should be deleted?" (with a list of high-level reasons why), and so forth.
The advanced toolset is designed for more experienced reviewers. This toolset will include more complicated tagging mechanisms, and will assume that the reviewer knows that they are doing.
It is primarily designed for running specific queues (e.g., blazing through a "suspect" queue) and for more direct manipulation (for those who understand speedy deletion criteria and the like).
Zoom will provide a series of simple, automated tests to help guide the reviewer to the correct conclusion regarding an article. These tests include things like checking to see how many inbound links exist, or if there are curse words, or other obvious problems like a lack of references.
These problems will be surfaced to the reviewer in an easy to understand manner.
Ideally, new tests can be created by the community without developer intervention (in a manner similar to AbuseFilter rulesets).
Zoom will provide the reviewer the ability to edit the article in place, without leaving the Zoom interface. The editor will open in situ, and be able to save directly.
This section describes additional ideas about queue mechanics which may or may not be useful. Let's call this a slush bucket.
Once an article has been placed in a queue, other reviewers might have the option to agree or disagree with the article's placement within a queue. This functionality would allow other reviewers to express opinion about an article's quality, especially during a learning phase.