Skip to content
This repository has been archived by the owner on Dec 8, 2017. It is now read-only.

Administration module requirements

Roger Steve Ruiz edited this page Dec 2, 2015 · 2 revisions

This page is for scoping out the elements that will go in an administration module on Open Opportunities. Draft and open for comment.


Basic requirements

User Management

  • Add/suspend/delete users
  • Only suspend/delete needed for state; low priority
  • Reset a user’s password

Admin management: Make user an admin (or remove admin privileges)

Tag management: Add/merge/delete tags

Project/op management

  • Close/delete projects & tasks
  • Master owner privilege -admins can edit everything as an owner
  • Delete comments

Metrics

  • Determine how many users, projects, ops, # of open/closed projects/opportunities
  • Determine how many projects / ops completed vs incomplete
  • User-definable timeframe for filtering results

Stretch concepts

+Piwik integration


See also the page on CrowdWork metrics, analytics and user surveys


Ideas

Read an article on why Quora is a success and one factor was they actively edit content to promote good content and bury bad content. They see this as a key success factor. Might be useful for Open Opportunities if admins could promote or otherwise feature cool, interesting projects and keep the grunt work from showing up in promotional emails, dashboard notifications, etc.