Changes between Version 6 and Version 7 of BluePrint/PublicPortal

04/01/12 23:57:12 (12 years ago)
Michael Howden



  • BluePrint/PublicPortal

    v6 v7  
    22= !BluePrint: Public Portal =
    3 Customizing workflows to enable a single instance of Sahana Eden to be used to coordinate Volunteers, Projects and Requests between multiple users from different Organisations, Companies and members of the public. Authorizations would be set based on what group(s) the use belongs to.
     3This !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.
    55== Introduction ==
    6 Currently, Eden is overwhelmed with functionalities which might not be required by every user. For example, if you have come to volunteer on Eden, assets might not be so important for yourself. In such scenarios, it is imperative to include user management and roles. Selective features then to the users on the basis of their roles and privileges adds ease of use and help making the interface more usable and concise.
     6Disaster risk management involves a large number of different organisations, from Government, UN, Military and NGOs. It is also important to engage members of the public. During a disaster members of the public need to be kept informed of key information, but also need to be told what they can do to help. "Spontaneous Volunteers" who come to help during an disaster present authorities with a unique challenge, as they need to be given direction to ensure that they don't become part of the problem.
    8 <Introduce the problem the solution is meant for>
    9 <Explain why this could be relevant for Eden>
    11 == Description ==
    12 Numerous examples, can be given in order to explain the problem. For example, if there is a need to send a bulk email to the staff and volunteers it might be useful if only a handful of people on the basis of their roles can do so. The clear distinction among the users regarding their roles and privileges, makes it easy enough to add new functionalities in a community environment.
    14 <Briefly describe the solution, e.g. start with a user story>
    15 <Name existing solutions, e.g. in other applications>
     8Sahana Eden can provide a web based solution to these coordination problems.
    1710== Requirements ==
     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]
     13== Public Portal Use Cases ==
     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
     20=== Permissions ===
    1823* Custom registration forms:
    1924 * Public
    3439* Tracking of work
    3540* Verification of Data
    36 == Use-Cases ==
    37 <Describe actors and use-cases>
    38 <Describe workflows>
    39 <Include diagrams where useful>
     42* Organisation Dashboards
     43* Publish data
    4145== Design ==
    4549== Implementation ==
     50Much of this functionality is already available in Sahana Eden. This project needs to focus on ensuring that it is easily configurable, well tested and well documented.
     521. Identify Deployment Settings
     531. Develop Workflows
     541. Improve Usability of Workflows
     551. Develop Test Cases
     561. Document
    4658The 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.