The Wikipedia Library/Processes/Library card platform/User stories

User stories are a convenient method to express desired functionality for end users of a software. Not all of these will map to individual tools or pages so duplication of features which may meet individual stories isn't a problem. Also they may not map to a particular access level, so if an editor needs to see a summary report but that report will be derived from something that a coordinator needs that's ok.

MVP:

The below should be considered necessary for the platform to be considered a success at 1.0. However, duplication of needs for each user should be ruthlessly removed. This list should be only as long as it needs to be get the product out the door.

As an editor I would like to:

• See what resources are available from different partners, viewing availability as well (open signups, signups open with waitlist and closed signups)
  • Check my own eligibility for various partner resources
• Add and update my contact information, including:
  • Add free text notes about myself
  • my email address
  • my home wiki
  • Note alternate or past accounts
• request access for a partner resource
  • Adding a (optional) text note for individual requests
• See the status of my access (pending/renewal/etc.)
• contact coordinators
• Log into the library platform via my wikimedia account

As a coordinator I would like to:

• View individual applications or editors
  • including status of previous applications
  • view global contributions of an editor with a link to their home wiki
  • view and verify alternate accounts where editors have specified them
  • Add a free text note to applications or editors
• View a queue of requests (either provided by an admin, per partner, or just the whole thing)
  • Sort and filter requests by time, status or other metrics
  • With a visual indicator for previously approved, denied or the presence of a coordinator note
• Act on requests for partner access (accept/deny/waitlist)
  • With the option to automatically notifying editors of the result
• Get a summary of editor access including e.g. mean/median wait times for editor access
  • By partners
  • Across partners
• Notify editors (individually or in bulk) of changes to partner access, renewal dates, etc.
• Export application data to .csv

As an admin I would like to:

• Task coordinators with queues of requests or partner resources
• Create and edit partner pages based on partner resource "applications"

Nice to have:

These are important to the product but aren't strictly necessary. They may be very important and their inclusion here doesn't necessarily mean that they won't be done. If you see anything in the MVP which belongs here, don't hesitate to suggest it be moved. As the set of functions for the MVP shrinks, the likelihood of success for the project will rise.

As an editor I would like to:

• View summary statistics for participation in the program (by partner or across partners)
• Quickly view multiple partner pages
• Interact with the system without using JavaScript (possibly)
• View partner resources by type (e.g. a page or view for all partner resources in the natural sciences)

As a coordinator I would like to:

• Package and email requests for editor access to partners from within the application
• Get analytics for editor use which go beyond summary statistics:
  • Contributions over time for editors with access
  • Reports on editors who may not be using the resources
• Track contributions via Linkypedia V.2 or some other tool
• Create pre-formatted reports for partners detailing access

As an admin I would like to:

• Post feeds of activity to a public facing page
• Create and manage templates for emails to editors and partners