4 | | |
5 | | == Design == |
6 | | * The Models: The table definitions go are in modules/s3db/cap.py. Place some functions which will help in the creation, sending and receiving of CAP XML files in s3msg module where it might best fit. |
7 | | * A detailed description of the data model is here: https://docs.google.com/spreadsheet/ccc?key=0AiLVG3CYfknsdGljMXNQejNWSURnVHZYYnMySERzdHc |
8 | | * The module dependency graph is explained here: ['''Tharindu - insert URL to doc'''] |
9 | | * The GUI |
10 | | * index: A map and a table of alerts sortable by the various fields of an alert. Clicking on a row on the table centers the map to the <Area> associated with the alert. |
11 | | * profiles: |
12 | | * index: View a listing of templates (We should ship some country-specific profiles by default in Eden since this is recommended) |
13 | | * edit & create: Editing / creating a profile. This should allow for specification of constraints for each field of the cap message. |
14 | | * templates: |
15 | | * index: View a listing of all templates grouped by their pertinent profiles. |
16 | | * edit & create: Allow users to create templates: This will allow for creating multiple <info> elements with placeholders for canned inputs such as [AREA] [SEVERITY] etc.which will then be substituted to produce text consumable via various media like SMS and IVR |
17 | | * create alert: A map with ability for easy input of polygons and circles, A drop-down for picking profiles and templates to use. A way to specify recipients for restricted alerts. |
18 | | * Reference and mockups: http://eden.sahanafoundation.org/ticket/1026 |