Changes between Version 41 and Version 42 of BluePrint/OccupyProjects


Ignore:
Timestamp:
03/19/13 03:29:34 (12 years ago)
Author:
devin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/OccupyProjects

    v41 v42  
    11= !BluePrint: Update Projects interface to meet Occupy's needs =
    22[[TOC]]
    3 
    4 == Use-Cases ==
    5 
    6 A project team member would register for the Sahana site as a "Project User" role, which would allow them to register their project in the system.  Once registered, Project Admin users can approve or reject them. Approved projects have their basic details publicly accessible via table and map views, but the rest of their information would only be accessible to project owners and project admins.  An additional tab on project profiles only viewable to project owners and admins would be a threaded comments section where those two groups could publish notes and communicate with each other.
    7 
    8 Project users have the ability to make requests for supplies, people (skils) and services from the network. Project Admins maintain a directory of "services" (new request type: services) that can be requested by projects.  Services consist of a Title, Description and General Contact Email and can be associated with a Person Entity: individual, group/team, organization.  When a project requests a service, the general contact is sent an email notification (via saved search and notification functionality).  These requests would be viewable by filtering services for type: services.
    9 
    103
    114== Projects ==