Brickipedia:Marking article feedback
Brickipedia is one of many wikis which use the Article feedback tool, a project of the Wikimedia Foundation. Brickipedia allows most registered users to mark article feedback with any one of four options. This guide, copied from the extension's moderation guidelines, explains to users how they should rate incoming article feedback.
Mark as 'useful'[edit source]
Any feedback which is reasonably actionable may be marked as useful if it is likely to improve the article. The format of the feedback (such as whether it is all in capitals or not) should not be considered when deciding whether to mark a post as useful.
Mark as 'resolved'[edit source]
Feedback should be marked as resolved if the reader suggestion has been addressed in the article.
Editors are encouraged to look through featured feedback and see if they can make some of the suggested changes to the article. When the suggested change is completed, the feedback post should be marked as resolved. (Tip: click on 'Add a note' to share a link to the diff).
Feedback can also be marked as resolved if it includes a reasonable suggestion (which would normally meet the conditions for 'useful') but is clearly not going to be fulfilled on policy grounds (please also state the policy in your note when you mark it as resolved).
Mark as 'No action needed'[edit source]
Feedback may be marked as 'No action needed' if it does not contribute to the development of the article but doesn't require an action from editors. This could include comments that are unclear, irrelevant, praise, or duplicates, for example. This tells other editors that the comment has been reviewed, and removes it from the 'featured' or 'unreviewed' queues.
Mark as 'Inappropriate'[edit source]
Feedback may be marked as 'Inappropriate' if it is nonsense, offensive or spam -- or if it includes private data like phone numbers or email addresses, for example. This tells other editors that the comment is not suitable for Wikipedia, and removes it from the 'featured' or 'unreviewed' queues. Monitors can then review it in the 'inappropriate' queue and decide if it should be hidden or not, as described below.