Changes between Version 8 and Version 9 of BluePrint/PublicPortal


Ignore:
Timestamp:
04/02/12 00:41:28 (13 years ago)
Author:
Michael Howden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/PublicPortal

    v8 v9  
    11[[TOC]]
    22= !BluePrint: Public Portal =
    3 This !BluePrint describes a project to  used Sahana Eden as a platform for engaging member of the community, corporations and different organisations to collaborate together for disaster risk management. This will require customizing a number of workflows for Sahana Eden to be used for coordinating Volunteers, Projects and Requests. This will also require setting different permissions for different types of information and different users (based on what organisation they work for). This project would involved developing Sahana Eden to ensure that it could be easily configured during deployment to be used is this way.
     3This !BluePrint describes a project to  used Sahana Eden as a platform for engaging member of the community, companies and different organisations to collaborate together for disaster risk management. This will require customizing a number of workflows for Sahana Eden to be used for coordinating Volunteers, Projects and Requests. This will also require setting different permissions for different types of information and different users (based on what organisation they work for). This project would involved developing Sahana Eden to ensure that it could be easily configured during deployment to be used is this way.
    44
    55== Introduction ==
    … …  
    99
    1010== Requirements ==
    11 This project would involve supporting a wide range of different workflows. The priority in this project should be to make use of existing Sahana Eden framework features, working to improve them and make them more flexible and useful. The development in this project should be done in a way so that it can be enabled/disabled through [DeveloperGuidelines/DeploymentSettings Deployment Settings]
     11This project would involve supporting a wide range of different workflows. The priority in this project should be to make use of existing Sahana Eden framework features, working to improve them and make them more flexible and useful. The development in this project should be done in a way so that it can be enabled/disabled through [DeveloperGuidelines/DeploymentSettings Deployment Settings].
    1212
    13 == Public Portal Use Cases ==
     13The Public Portal would use the following modules:
     14* Organisations
     15* Human Resources
     16* Membership
     17* Projects
     18* Events
    1419
    15 === Registration ===
    16 * When users register they should be able to select what organisation they belong. Then only someone with Admin rights for that organisation should be able to authorize that user
    17 * Users should also be able to register
    18 * Someone
     20Please feel free to add your own use cases here.
    1921
    20 === Permissions ===
    21 [wiki:S3AAA]
     22=== Public Portal Use Cases ===
    2223
    23 * Custom registration forms:
    24  * Public
    25  * Organisation
    26  * Companies
    27 * Setting authorizations & customizing workflows for:
    28  * Volunteer Registration
    29  * Organisation Registration
    30  * Member Registration (Application?)
    31  * Incident Reporting
    32  * Item, Task & Volunteer Requests
    33  * Task Assignment
    34  * Project
    35  * Social Media Integration
    36  * Sign Up for Alerts
    37  * Sign Up for Trainings
    38  * Register Donations ($$$ & Virtual)
    39 * Tracking of work
    40 * Verification of Data
     24==== Registration ====
     25* Users should also be able to register as members of the public, which doesn't require any approval.
     26* When users register they should be able to select what organisation they belong. Then only someone with Admin rights for that organisation should be able to authorize that user for the organisation (although the user gets public permissions immediately).
     27* A User can register a new Organisations into Sahana Eden. They will become a admin for that organisation. The site admin should be able to verify/correct this.
    4128
    42 * Organisation Dashboards
    43 * Publish data
     29==== Permissions & Verification ====
     30The project should make use of the Sahana Eden framework support for permissions: [wiki:S3AAA] and [S3AAA/OrgAuth Organisation Authorization]. This project would also have to extend this to add configurable support for verification levels for data which is added. This would mena that when data is added it can only be read by a smaller group, until it is verified.
     31
     32Organisations should be able to control their own permission levels. They should be able to choose how different types of data are shared by default and also modify this for specific data.
     33
     34==== Organisations & Companies ====
     35* Add projects to show what sort of work they are doing.
     36* Assignment tasks within their project to users
     37* Publish trainings which other users (either internally within their organisation or open too the public) can apply for.
     38* Maintain a dashboard within Sahana Eden which is specific to their organisation
     39 * Allow them to edit some of the content on that dashboard
     40 * Show configurable data (maps, lists, reports)
     41* Maintain a contact list of their staff/volunteers/members/people who have subscribed to that organisation's updates
     42
     43==== Public ====
     44* Public should be abel to apply to be a member/volunteers with an organization. This would need to be approved by the organisation.
     45
     46==== Misc ====
     47* All users should be able to:
     48 * Report incidents. These would need to be verified by someone with the right permission to appear for an organisation / all users.
     49 * Request Items
     50 * Offer requested items
     51 * Request tasks that need to be done
     52 * Offer to do requested tasks
     53 * Sign Up to Alerts from the site
     54* The Site must be able to broadcast data to Social Media (Facebook & Twitter)
    4455
    4556== Design ==
    … …  
    56671. Document
    5768
    58 The implementation involves taking advantage of the already built in web2py user roles and privileges. User groups can be created by the administrator at the time of the initial setup.
    59 
    60 After that, once a user registers on a website he can be allocated a certain group on the basis of what he has requested, or a role that a member of higher role has assigned to him (assuming a total order exists between the roles, which is not a necessary assumption though) which will add an entry to the auth_membership.
    61 
    62 After this, we can before any function have a wrapper to say that only people with roles 'A' and 'B' or with privileges 'X' or 'Y' can access the same function.
    63 
    64 This works at granularity of two levels :
    65 1. Groups
    66 2. Privileges
    6769== References ==
    6870* BluePrintVolunteer