Article feedback/Version 5/Feature Requirements

Feature Requirements
This page will describe the features to be developed for the Article Feedback Tool V5. Check the new AFT V5 project page for more information about this initiative. For a preview of what these forms and pages might look like, read below, or, which include simple wireframes for key touchpoints, as well a project plan and other useful exhibits.

Overview
Key features for AFT V5 will include:
 * new feedback forms
 * calls to action
 * expanded feedback
 * feedback page
 * moderation tools

In the first phase of this project (Oct.-Dec. 2011), we will create and test four different ways to extend the current rating tool:
 * Option 1: Share your feedback - Did you find what you were looking for? Add a comment
 * Option 2: Make a suggestion Suggest an improvement, ask a question, report a problem or give praise to the editors
 * Option 3: Review this page - Rate this article. Add a comment or suggestion for improvement.
 * Option 4: Edit this page - Help improve Wikipedia (call to action, for comparison purposes)

We plan to A/B test these four options against the current rating tool, to find out which is most effective for engaging readers, supporting editors and improving article quality.

]

We plan to develop more features in a second phase (Jan.-March 2012), based on first phase results. We are starting a wish-list of features for that second phase and will link it here shortly.



Technical (non-functional) requirements

 * The AFT v5 shall be developed on top of the existing AFT implementation (MediaWiki extension), preserving its current functionality, e.g.:
 * Feedback items expire after 30 days
 * Feedback tool can be disabled in user preferences for registered users
 * Source control requirements:
 * Core - use v1.18 (REL1_18)
 * Extensions - from trunk
 * AFT being developed as an extension, forked (not branched) from trunk



Feedback functionality
TBD (ratings, comments, etc).



Feedback interface
The feedback interface appears on every article, as the current AFT does (unless disabled in user preferences). There shall be several options of the user interface, for A/B testing. Ultimately, one option will be selected for production use. the following 4 options shall be implemented, in addition to the currently existing one.
 * TBD: which articles do/do not display the feedback form (criteria).
 * The interface option to display shall be selected randomly. (TBD: equal chance? configurable/automatic weighted system?)



Option 1


This variation is a feedback form. The important parts of it are: Additional elements:
 * A yes/no question. The yes/no shall be mapped to 4 and 2 overall rating, respectively.
 * A comment box (multiline).
 * Label - served as a facade for the tagging functionality. The interface shall only allow 1 label (tag) to be selected for a comment.
 * Help button - functionality TBD
 * Links to feedback page and privacy policy
 * Post button



Option 2
TBD



Option 3
TBD



Option 4
TBD



Calls to Action
After readers post their feedback, they will see one of these calls to action:
 * take a survey (link to survey page)
 * edit this article (if logged in)
 * sign up or login (if logged out)
 * get email notifications (if my post is used)

This is one of the four calls to action to be displayed after the feedback had been submitted.
 * Take a Survey *

Questions to discuss:
 * 1) Can the user edit his/her feedback after it was submitted? [FF: yes]
 * 2) Are the different calls to action to be displayed here? [FF: yes]



Feedback page
The shall display a list of the feedback items for an article. See all the posts for this article, vote them up or down (moderated by editors and administrators)

Expanded Feedback
(preliminary) (optional) - Tell us more: suggest improvements, rate article qualities or share your expertise.

Talk page features
- Tools to feature the best feedback on the article talk page, with a recommended check list for editors

Touchpoints
Here is an overview of how key features and touchpoints will interact with each other to make reader feedback more useful:





Community Ideas
Here are some of the community feature ideas which we have categorized so far:

Phase 1: (Q4 2011)
 * Comment box
 * "Did you find what you were looking for?"
 * Checkboxes for suggested improvements
 * Make rating tool more visually compact
 * Hide AFT for recently created pages
 * Different calls to action

Phase 1.5: (Q4 2011)
 * Dashboard with recent feedback and page metrics
 * Allow permanent linking of page scores
 * Courtesy diff link to the rated revision

Phase 2: (Q1 2012)
 * Ratings details (counts, distribution, averages over time)
 * Promote (or post) feedback/comments to talk page
 * Let registered users track pages they rated
 * Comments feed per article (for editors) – RSS/API?

Developer Ideas
Here is where we will add developer feature ideas as the project gets underway.