Changes between Version 69 and Version 70 of Event/2011/GCI

11/20/11 09:22:31 (13 years ago)
Pat Tressel



  • Event/2011/GCI

    v69 v70  
    178178=== Map elements between EDXL-SITREP and EDXL-RM ===
    179179'''''Not migrated'''''[[br]]
    180 Difficulty : '''HARD''' Proposed by: [ | Nuwan][[BR]]
     180Difficulty : Nuwan:'''EASY''', Pat:'''HARD''' Proposed by: [ | Nuwan][[BR]]
    181181'''Specific    : ''' There are several elements within the [ | EDXL-SITREP] data standard that are identical to that of [ | EDXL-RM]. The objective is to create a descriptive table of those elements that a programmer can use to develop a set of procedures to strip the RM data from SITREP to manage records in the relational database [[BR]]
    182182'''Measurable  : ''' Requires diligently investigating each and every data element then comparing them with the two data standards SITREP and RM. Requires knowledge of data types and XML. If not, this exercise will help the student learn about XML and data standards [[BR]]
    193193=== Blue print to add Transliteration to text entry controls ===
    194194'''''Not migrated'''''[[br]]
    195 Difficulty : '''HARD''' Proposed by: [ | Nuwan][[BR]]
     195Difficulty : Nuwan:'''MEDIUM''', Pat:'''HARD''' Proposed by: [ | Nuwan][[BR]]
    196196'''Specific    : ''' For local language text entry one can use a native language keyboard with native unicode character set or use transliteration to allow entering the native word phonetically. for example with [ | Google Transliteration Beta] or other plug-in like [ | USCS's Real-Time Unicode Converter] [[BR]]
    197197'''Measurable  : ''' Users in Sri Lanka, for example, prefer Sinhala or Tamil languages. Making the option for them to turn on transliteration in Sahana to enter critical information in the local language is an important usability aspect. [[BR]]
    256256'''''Not migrated'''''[[br]]
    257257for Common Alerting Protocol (CAP) with capabilities for multi-language alerting and multi-media delivery; use Agasti CAP Broker as a starting point (Nuwan)
    258 Difficulty : Nuwan:'''MEDIUM''',Pat:'''HARD''' Proposed by: [ | Nuwan][[BR]]
     258Difficulty : Nuwan:'''MEDIUM''', Pat:'''HARD''' Proposed by: [ | Nuwan][[BR]]
    259259'''Specific    : ''' Build a [ | wireframe] with functionality for the [ | Common Alerting Protocol] messaging broker. It should follow a publisher subscriber model. Some specifications are in the [ | CAP Software Requirement Specifications] [[BR]]
    260260'''Measurable  : ''' CAP messaging broker is becoming a much sort after tool by many organizations. It is an ITU recommendation. Such tool can be easily adopted by governments and emergency coordination agencies for managing their alerting and situational awareness. [[BR]]
    271271=== Design a GUI to build and test XSL file ===
    272 Difficulty : Nuwan:'''MEDIUM''',Pat:'''HARD''' Proposed by: [ | Nuwan][[BR]]
     272Difficulty : Nuwan:'''MEDIUM''', Pat:'''HARD''' Proposed by: [ | Nuwan][[BR]]
    273273'''Specific    : ''' Given that Sahana is getting heavy on XML there should be a tool to develop text, html, etc outputs based one's own XSL transformation file.  The user should be presented with the option to select the XML file; i.e. tags and schema, then include/exclude those tags with inserts of fixed text. The user should be able to preview the output. The built XSL file can then be stored to be used for a particular function. In this case it would be producing CAP message based user specific outputs for email, web, rss, twitter, google, etc. [[BR]]
    274274'''Measurable  : ''' This would allow super users to develop implementation specific CAP content delivery outputs. [[BR]]