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

Timestamp:

06/29/12 16:48:01 (12 years ago)

Author:

g0wda

Comment:

--

Event/2012/GSoC/CAPBroker

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