System Configuration Control Panel
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.
Blueprint information
- Status:
- Complete
- Approver:
- Chad Heuschober
- Priority:
- Medium
- Drafter:
- Chad Heuschober
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- Accepted for mayon
- Implementation:
-
Not started
- Milestone target:
-
2.0.0
- Started by
- Completed by
- Darlene McCullough
Related branches
Related bugs
Sprints
Whiteboard
Summary
=======
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.
Example
-----------
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.
Description and Constraints
=======
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.
Extra Credit
==========
* Building an address format generator
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 internationaliz
* Defining and enabling standards-compliant modes
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).
* Logo Configuration
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.
