Re: [sahana-maindev] Update: Google Summer of Code: CAP aggregator Module

[Nuwan W. <wai...@gm...>]

Hi Shree Kant,

I must have missed the email exchange with respect to making CAP reader a
sovereign module and not part of the Alerting module. Given the strong
synergies with the other elements in the alerting module, I am not in favor
of it being a separate module and strongly believe it should be part of the
Sahana Alerting sub module inside the Messaging module or carve out the
entire Alerting Module as a sovereign module but put the CAP reader in it.

On the message priority, once again severity cannot be the sole element
defining the priority, you should read the ITU CAP guidelines with respect
to message priority; I think it was also mentioned in the specs I shared
with you. Lets discuss this tomorrow, I think we have a IRC meeting
schedule, right? else you suggest a time.

Nuwan

On Sun, Jun 28, 2009 at 11:45 AM, shreekant bohra
<shr...@gm...>wrote:

> Hi Everyone,
>
> @Mark Thanks a lot! The red lines shows, starting and ending point of area
> affected by alert.
>
> @Nuwan,
>
> 1) Have you tested on Explorer, I came across some inconsistencies with the
>> display like content not layering correctly.
>>
>
> Thanks for reminding me of  IE :) I have fixed the problems
>
> 2) When we click on the link it takes us to the alert creator's website.
>> Why can't we display the CAP content in a Sahana page? Each alert opens a
>> new FF tab, better to display the content in same tab.
>>
>
> I have now designed a xsl stylesheet for transformation of CAP alerts, now
> the alerts are shown in Sahana itself! This is achieved by xslt
> transformation.Thanks for the advice.
>
> 3) CAP Aggregator should ideally come under the main menu "Sahana
>> Messaging/Alerting Module" then under sub menu "CAP"
>
>
> Initially it was part of Messaging Module, but after discussion with Gavin,
> we decided to make it a separate module. And I think keeping it as a
> separate module is better solution, as its more of a general use module.
>
> 4) We may want to relay a particular alert locally. For example, a IOTWS
>> tsunami warning received will be changed to fit the local scenario and
>> relayed through local network. How do we do that? Can we save the CAP XML
>> file and read it in to the CAP editor? There is a work around where we go to
>> the alert publisher's website and save the CAP XML file on hard drive then
>> uploading it to Sahana CAP editor. We may want to automate some of it to
>> make it easy on emergency managers.
>>
>
> I think this is more a part of CAP Publisher module, once we get both
> module working , we can integrate to achieve this.
>
> 5) I think the user should be given the option to set the priority levels
>> by offering a config table to assign the respective severity, certainty, and
>> urgency predefined values. The tags urgency, severity, and certainty have 5
>> predefined values each; thus there are 125 different combinations. If we
>> give the user to set "urgent", "high", and "low" priorities then that
>> accounts for only 3 urgency, severity, and certainty combinations.
>> Therefore, we may need to use some fuzzy logic to capture the priority
>> levels = urgent, high, low. These priority levels will be assigned a color
>> as well. (if this is something you want to do we can discuss)
>>
>
> The priority level set by user is for a CAP Source, which sets if user
> wants to see the alerts from this source at priority. The color coding is
> done presently based on 'Severity' and 'Message Type' tags, if the severity
> is 'severe' the color is set to 'red' , if severity is 'moderate' color is
> set to 'blue' and if severity is 'minor' color is set to 'yellow'  and in
> case an alert is 'Test' alert, an image indicating that is set. However if
> you think we should take into account all 125 combinations, we can have a
> discussion over it.
>
> 6) Do we need to sort by category? I think so especially when searching for
>> a specific alert. The list of categories are given in the cap cookbook. This
>> is none exhaustive. No need to clutter all functions in to one page; perhaps
>> make the search function separate. If you plan on adding a search function
>> perhaps make it a strong search function by giving all possible filter
>> criteria.
>>
>
> The searching options are to easily filter out alerts based on date,
> severity, source and category. These lists are dynamically generated based
> on database entries, we can probably work on a better search function too.
> Sort by category is useful in case we need to have a look at alerts of a
> particular category.
>
> Live Demo here: http://tinyurl.com/sahanacapdemo
>
> Thanks a lot for your reviews and suggestions.
> I am now working on firefox addon, would soon show up something :)
>
>
> Thanks
> Shree Kant
>
> On Sat, Jun 27, 2009 at 8:15 AM, Nuwan Waidyanatha <wai...@gm...>wrote:
>
>> Hi Shree Kant,
>>
>> 1) Have you tested on Explorer, I came across some inconsistencies with
>> the display like content not layering correctly.
>>
>> 2) When we click on the link it takes us to the alert creator's website.
>> Why can't we display the CAP content in a Sahana page? Each alert opens a
>> new FF tab, better to display the content in same tab.
>>
>> 3) CAP Aggregator should ideally come under the main menu "Sahana
>> Messaging/Alerting Module" then under sub menu "CAP"
>>
>> 4) We may want to relay a particular alert locally. For example, a IOTWS
>> tsunami warning received will be changed to fit the local scenario and
>> relayed through local network. How do we do that? Can we save the CAP XML
>> file and read it in to the CAP editor? There is a work around where we go to
>> the alert publisher's website and save the CAP XML file on hard drive then
>> uploading it to Sahana CAP editor. We may want to automate some of it to
>> make it easy on emergency managers.
>>
>> 5) I think the user should be given the option to set the priority levels
>> by offering a config table to assign the respective severity, certainty, and
>> urgency predefined values. The tags urgency, severity, and certainty have 5
>> predefined values each; thus there are 125 different combinations. If we
>> give the user to set "urgent", "high", and "low" priorities then that
>> accounts for only 3 urgency, severity, and certainty combinations.
>> Therefore, we may need to use some fuzzy logic to capture the priority
>> levels = urgent, high, low. These priority levels will be assigned a color
>> as well. (if this is something you want to do we can discuss)
>>
>> 6) Do we need to sort by category? I think so especially when searching
>> for a specific alert. The list of categories are given in the cap cookbook.
>> This is none exhaustive. No need to clutter all functions in to one page;
>> perhaps make the search function separate. If you plan on adding a search
>> function perhaps make it a strong search function by giving all possible
>> filter criteria.
>>
>>
>> best
>> Nuwan
>>
>> On Fri, Jun 26, 2009 at 10:32 PM, shreekant bohra <
>> shr...@gm...> wrote:
>>
>>> Hello Every one,
>>>
>>> Hoping that everyone is doing fine, me and Gavin had a discussion on
>>> #sahana over the firefox addon development on this monday and over the
>>> improvements needed in Sahana CAP aggregator module. I have made some
>>> important improvements in CAP aggregator module, based on discussion we had,
>>> one of the nice feature suggested by Gavin was "Retweeting of alert" I have
>>> included this feature as an experiment, would like to see reviews over it,
>>> another major changes are in UI, I have made alerts look more compact and
>>> had put the map on the homepage, you can check out live demo here,
>>> http://tinyurl.com/sahanacapdemo
>>>
>>> I would like to hear suggestions, comment over it. Meanwhile I am working
>>> on firefox addon, I have done the basic part of it, I would show up first
>>> working demo in a couple of days.
>>>
>>>
>>> Cheers!
>>> Shree Kant Bohra
>>>
>>> --
>>> Let the source be open
>>> website:www.geekybuddha.org
>>> Summer of Code Blog: eth0.tumblr.com
>>> Personal Blog: insideme.geekybuddha.org
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Sahana-maindev mailing list
>>> Sah...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sahana-maindev
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Sahana-maindev mailing list
>> Sah...@li...
>> https://lists.sourceforge.net/lists/listinfo/sahana-maindev
>>
>>
>
>
> --
> Let the source be open
> website:www.geekybuddha.org
> Summer of Code Blog: eth0.tumblr.com
> Personal Blog: insideme.geekybuddha.org
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Sahana-maindev mailing list
> Sah...@li...
> https://lists.sourceforge.net/lists/listinfo/sahana-maindev
>
>