wiki:Event/2011/GCI

Version 28 (modified by Nuwan Waidyanatha, 10 years ago) ( diff )

--

Tasks for GCI

http://code.google.com/p/google-code-in/wiki/GCIAdminMentorInformation

Code

  • Build library(ies) Emergency Data Exchange Language Distribution Element

Difficulty : Hard Proposed by: | Nuwan
Specific: | EDXL-DE is the final wrapper (envelope) of all EDXL data parcels. We may be delivering a EDXL Resource Management (RM) information and Situational Reporting (SITREP) information to the managers of several emergency organizations. The DE will contain who, when, and where those RM and SITREP data parcels would be delivered. Every EDXL message (data parcel) must carry this information. Otherwise, it cannot use available distribution methods and would need to rely on its own protocol; that's not very user friendly.
Measurable: It is purely a coding task that involves playing with XML and developing a class, possibly within the ??? 3R ??? framework.
Attainable: run through the steps
Step 1 :: select one of the existing EDXL-based applications in Eden, I recommend the EDXL-RM; Step 2 :: discuss each of the attributes/elements; then determine how EDXL-DE would be added to EDXL-RM as a pop-up GUI.
Step 3 :: create some example XML files to get a feel for the inputs and outputs Step 4 :: write code to add to take the inputs EDXL-RM and EDXL-DE to package the data for delivery Step 5 :: test the code, fix bugs, and generalize the functions Step 6 :: Apply to EDXL-HAVE and EDXL-SITREP to generalize the library
Relevant: Applies to Sahana Interoperability policy. Present developments to investigate are: HAVE, RM, and SITREP http://www.oasis-open.org/standards#edxl
Time-bound: If steps 1 - 4 are completed that can be a full accomplishment; additional work is a bonus
Evaluate: Produce XML files with the EDXL-DE element appended to the EDXL-RM, SITREP, or HAVE
Reevaluate: Use an API to add and strip the EDXL-DE to any EDXL data standard. Use the same set of XML files to run through this process

Documentation

Outreach

Quality Assurance

  • 2 xTesting and reporting bugs
  • Using Selenium IDE create test scripts for application (easy)
  • Document the data needed for a selenium test script to run from a bare (prepopulated) system (medium)
  • Take a selenium script (see above) and using the test API generate a python test (hard)

Research

  • 3 x Create disaster scenarios & demos with data through pre-populate
  • Easy (Nuwan): Map elements between EDXL-SITREP and EDXL-RM to integrate the Situational Reporting and Resource Management components (deliverable: "table") with underlying schema
  • Medium (Nuwan): Develop a blue print (deliverable: "specifications document") for adding Transliteration to text entry controls, for example with http://www.google.com/ime/transliteration/ engine or any other generic plug-in
  • Easy (Fran): Provide UTF8 names for Locations exported from GADM in Vietnam, e.g. using Wikipedia
    • see attached spreadsheet VNM_adm4.7z (L1 has been done, focus on L2 1st, then L3, then finally L4 if you can)

Training

Translation

  • Translating key phases (from home page)
  • Review code to for quality of localized strings (1 task = 3 fixes)
    • Avoid concatenation of localized strings - use %(variable_name)s instead
    • Avoid non keyboard characters (Excel doesn't handle these)
    • Try to use consistent language

User Interface

  • Provide feedback on Workflows in Sahana Eden
  • design a better homepage for Sahana Eden (wireframes)
  • design a better GUI (deliverable: "wireframes" = moderate) for Common Alerting Protocol (CAP) with capabilities for multi-language alerting and multi-media delivery; use Agasti CAP Broker as a starting point (Nuwan)
  • design a GUI (deliverable: "wireframes" = hard) for building implementation specific XSL documents that generate SMS, Email, IVR, tweet, etc multi-media delivery text outputs (Nuwan)

Attachments (35)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.