Changes between Version 13 and Version 14 of Event/2012/GSoC/CAPBroker


Ignore:
Timestamp:
06/29/12 16:48:01 (9 years ago)
Author:
g0wda
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Event/2012/GSoC/CAPBroker

    v13 v14  
    99  * 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 (simply reversing the order of the objects). This would allow for a validated CAP message to be created; core of the module.
    1010||= Component =||= Stage =||
    11 ||Data model for CAP alerts || implemented: to be reviewed ||
     11||Data model for CAP alerts || completed ||
    1212  * the models are at modules/eden/cap.py
    1313
    1414||= Component =||= Stage =||= Expected =||
    15 ||CAP alert creation interface || Started || Thursday, 21 June ||
     15||CAP alert creation interface || Started || Under review ||
    1616  The data model is in place. I am now creating the various UI widgets necessary for the same, namely:
    1717  * ~~KeyValue widget: for cap fileds such as Codes and Parameters: this is a widget will help in input of key-value pair data.~~
     
    2323
    2424||= Component =||= Stage =||= Expected =||
    25 || CAP Alert import/export || Not started || Thursday 28 June ||
     25|| CAP Alert import/export || Not started || Thursday 1 June ||
    2626  * Plan: modify s3import and s3export, XSLTs for CAP messages.
    2727||= Component =||= Stage =||= Expected =||
    28 || CAP template creation interface ||  Not started || 1 July ||
     28|| CAP template creation interface ||  Not started || 5 July ||
    2929  * 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.
    3030||= Component =||= Stage =||= Expected =||