In preparation for T193782, we need to think through what it will take distinguish "submitted drafts awaiting review" from all drafts so that they can be displayed as such in the [[ https://en.wikipedia.org/wiki/Special:NewPagesFeed | New Pages Feed ]] interface.
The background is that new users create pages in the draft namespace, but then go through a separate step to "submit" them for review by Articles for Creation (AfC). This step applies a template and category to the draft. Those submitted drafts await review by an AfC reviewer, who can accept them and move them to the main namespace, or can decline them and send them back to the author for improvement and resubmission.
One additional element is that we want to prevent multiple AfC reviewers from reviewing the same draft at the same time. The gadget that most AfC reviewers use, [[ https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Articles_for_creation/Helper_script | AFCH script ]], allows users to mark drafts as "under review", which could be used to prevent other reviewers from selecting that draft.
Therefore, there are two main user stories here are:
* As a reviewer, I need to be able to filter to only those drafts that have been submitted to AfC and are awaiting review. This would include drafts that are awaiting their second, third, etc. review, but it would exclude drafts that have been submitted for review, have already been reviewed, and awaiting resubmission by their authors.
* As a reviewer, I need to not accidentally attempt to review a draft already under review by another reviewer.
------
Some technical considerations that have been brought up so far in discussion of these user stories (though there are likely many more):
* What work will it take to identify which drafts have the status of "submitted and awaiting review"?
* Will we be able to exclude drafts under review from being present in the New Pages Feed list? Review typically takes only a couple minutes, so this type of exclusion would essentially need to be realtime.
------
====Deliverables
* Create Phab tickets for a rough implementation plan
* Identify & document any dependencies and risks
* Answer technical consideration questions above.