8 | | * Project plan with progress column |
9 | | The project plan is now different from the one in the proposal in that, I will be implementing CAP Alert creation then CAP template and then CAP profile. |
10 | | ||= Component =||= Stage =|| |
11 | | ||CAP alert creation interface || Started || |
| 8 | * '''Project plan''': |
| 9 | * The project plan is now different from the one in the proposal in that, I will be implementing CAP Alert creation then CAP template and then CAP profile. |
| 10 | ||= Component =||= Stage =|| |
| 11 | ||Data model for CAP alerts || To be reviewed || |
| 12 | * the models are at modules/eden/cap.py |
| 13 | |
| 14 | ||= Component =||= Stage =|| |
| 15 | ||CAP alert creation interface || Started || |
18 | | ||= Component =||= Stage =|| |
19 | | || CAP Alert import/export || Not started || |
20 | | * Plan: |
21 | | ||= Component =||= Stage =|| |
22 | | || CAP template creation interface || Not started || |
23 | | * Plan: set a flag in the alert table and all the children (has a) tables to denote a row belongs to a template. |
24 | | ||= Component =||= Stage =|| |
25 | | || CAP Profile creation interface || Not started || |
| 22 | ||= Component =||= Stage =|| |
| 23 | || CAP Alert import/export || Not started || |
| 24 | * Plan: modify s3import and s3export, XSLTs for CAP messages. |
| 25 | ||= Component =||= Stage =|| |
| 26 | || CAP template creation interface || Not started || |
| 27 | * Plan: set a flag in the alert table and all the children (alert has a (which has a)) tables to denote a row belongs to a template. |
| 28 | ||= Component =||= Stage =|| |
| 29 | || CAP Profile creation interface || Not started || |