Contents |
Proposed by: CUNY School of Professional Studies / New York City Office of Emergency Management
Contact (name, email, irc, skype): Chad Heuschober, chad.heuschober@mail.cuny.edu, chadheus@freenode, cunychad
Best way and times to contact during RHoK 2.0 Dec 4/5 2010: email, available most other means late mornings through evenings EST
The experimental rewrite of Sahana Agasti, using the Symfony framework, has given Agasti developers the opportunity to get a lot of the system out of the code and into datapoints. Unfortunately, administrators still don't have a way to interact with these edge tables and datapoints. This definition supports the creation of a control panel and a means to interact with those edge (also known as lookup) tables so that emergency managers with differing requirements are not forced to go into database tables directly to make changes to suit their organization.
An emergency management organization may only use and store six religions while a different organization defines and uses over 30 religions. Each organization will want to define and/or restrict which religions it wishes to use in its dataset.
Notable to the current design of the system is the app_display boolean found on many tables. Rather than allowing end-users to delete data, the preference is to have them remove records from appearing in field lists. When this bool is true, the record is visible.
Addresses are stored as independent elements (eg, line 1, line 2) and parsed/rebuilt according to a formatter that defines the line, delimiter, etc. Having the ability to define one's one address format would be a huge step forward towards internationalization.
This, almost pipe-dream, would support having a few pre-defined standards-compliant modes that would provide a one-button solution to automatically adjust the display bits (and create records where necessary) to ensure that the application is working with datapoints that are compliant with a specific data standard (eg, PFIF for client data).
To allow branding by the organization(s) hosting Sahana, either during an activation or planning by a municipality, and to help lower confusion the ability to define a logo for a specific instance would be beneficial.
To participate:
The Agasti Mayon trunk can be found on Launchpad at: https://code.launchpad.net/~sahanaphp-committers/sahana-agasti/mayon
Documentation for Agasti Mayon can be found at: http://wiki.sahanafoundation.org/doku.php/agasti:mayon:start
More information about Agasti Mayon and links to other resources can be found at the official documentation wiki with special note given to the Mayon 911 page.[1]
Sahana Agasti is an open-source PHP-based disaster management software registered by the Sahana Software Foundation, first created in response to the 2004 Tsunami, and used by emergency management organizations and grassroots organizers alike to coordinate preparedness, response, and recovery tasks throughout disaster operations. Used by the New York City Office of Emergency Management (NYC OEM), and supported by development efforts from the City University of New York School of Professional Studies (CUNY SPS), the National Library of Medicine, Respere, and an international community of developers, Sahana Agasti is an internationally recognized platform for disaster operations management.
The Agasti Mayon (2.0) branch is currently being headed by the CUNY SPS team, a subset of whom will be actively participating in RHoK #2 to try to merge any solutions directly into the Mayon trunk. The CUNY SPS team is also supported by their partner, the New York City Office of Emergency Management who is slated to be the first active installation of the Agasti Mayon in 2011.
All Sahana Agasti projects are registered under the Sahana Software Foundation (SSF). For more information about the SSF, please see: http://sahanafoundation.org/
Most of the edge tables already exist. Likely, Symfony/Doctrine forms can be utilized and standardized to pick up these data tables quickly and provide a simple, consistent way to edit them. Reference information for the schema as well as some Doxygen/Symfony reference can be found here: http://wiki.sahanafoundation.org/doku.php/agasti:mayon:start#reference_information