Changes between Initial Version and Version 1 of Event/2012/GCI/Code

11/01/12 16:59:44 (9 years ago)
Mark Prutsalis



  • Event/2012/GCI/Code

    v1 v1  
     2= Contribute: Code  =
     3These tasks are suitable for coders of various levels. Sahana Eden using Python, !JavaScript and HTML.
     4== Easy ==
     5''Tasks for beginning coders, or if new to Python or web services''
     7=== Fix an Easy Ticket ===
     9Pick a bug report from, try to reproduce the issue in a local instance, fix the problem and submit a patch to the ticket on Trac, then notify the Sahana-Eden mailing list about your patch for verification.
     11=== Add Social Media Share Buttons to Pages ===
     13Add code which displays buttons to Share to Social Media (at least facebook & twitter) on every page.
     14* This should be controllable from a deployment_setting
     15* Please push the code to a branch on launchpad for review and submit a link to this branch
     18=== Common Operational Datasets ===
     19 *
     20 * Complete the Model definitions that have been started in [ models/]
     21 * Think about how we could make use of them
     22  * Display on the Map
     23  * Have Reports which compare the baseline & situational assessments
     25=== Update Pootle ===
     26Provide a set of admin scripts (bzr post-commit hook?) to update Pootle with any changed strings as a Merge.
     28=== GIS/Mapping ===
     29These are a various GIS/Mapping Tasks:
     30 * Add a delay to the onHover tooltip (highlightControl)
     31  * Something like [ hoverIntent]
     32 * Continue Integration of [ Potlatch]
     33  * for editing the main OSM database
     34  * for editing a local OSM database
     35 * Make the display_feature() & display_features() popup a Window instead of opening in a DIV
     36  * This was working in FF before:
     37 * Replace the Measure Length/Area tools with [ GeoExt.ux]
     38 * Option to go Full screen & back
     39  * Full screen view (No Ext window) will be required for use on a small-screen, such as a Mobile device
     40 * [ Layer Tree]
     41 * Get a pr/person/presence record upon login if HTML5 !GeoLocation available & not changed since last time
     42  * login_next
     43 * Map Preview when Lat/Lon set in pr/person/presence (auto or not)
     45[wiki:DeveloperGuidelinesGIS Use the Mapping API to:]
     46 * Color coded maps according to Geo-data (threats, needs, etc)
     47 * Placing variable sized markers on the map in proportion to data (number of people in camp, number of families needing food)
     49=== !Lat/Lon converter ===
     51Portuguese Volunteer Firefighters ([Deployments/Bombeiros Bombeiros]) use Eden.
     53They get given !Lat/Lon coordinates in Degrees/Minutes/Seconds, but Eden stores internally as Decimal degrees.
     56* Create a represent function to output the data as D/M/S
     57* Create a validator (& possibly widget) to allow entry of this format & have it converted to decimal dagrees for storage
     59=== Scale Uploaded Images ===
     60When images are uploaded we can limit the size, however larger pictures should be scaled instead.
     62This should be implemented as a Validator {{{modules/s3/}}}).  The size limitation should be configurable in the model for that specific field, with a sensible default.
     64Bonus points: UI to crop image (this would be a Widget: {{{modules/s3/}}})
     66Ideally the image would be resized client-side to make it faster to upload...this might be hard with pure JS, so would need to be Flash?
     67 * Maybe: (e.g. from )
     69Example: Personal Profile Picture
     70=== Suggestion Box ===
     71 Here are some potential features for a "suggestion box", roughly in order of priority:
     72 * Text data entry form -- just use standard Eden database fields like "timestamp", "authorstamp", and "comments", maybe with a subject field.
     73 * Allow defining topics or keywords. Let user choose a topic for their suggestion. Add all module names as an initial list of topics.
     74 * Simple search in the body of posts -- match words.
     75 * Regexp search.
     76 * Allow commenting on (replying to) suggestions -- show comment thread with original post.
     77 * Some form of importance rating (e.g. voting up or down).
     78 * Original suggestion from:
     80=== Map elements between EDXL-SITREP and EDXL-RM ===
     81Proposed by: [ | Nuwan][[BR]]
     82'''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]]
     83'''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]]
     84'''Attainable  : ''' [[BR]]
     85Step 1 :: Go through EDXL-RM and EDXL-SITREP documentations [[BR]]
     86Step 2 :: create example files to get an understanding of the data and structure [[BR]]
     87Step 3 :: develop the table with RM and SITREP elements with a description [[BR]]
     88Step 4 :: develop a simple XSL file to strip the RM data from SITREP [[BR]]
     89'''Relevant    : ''' Applies to Sahana interoperability policy. Given that Eden does support resource and incident management, it is important to derive the response resources and resource requirements from situational reports. This function would help automate some of those data extraction functions. That requires integrating the SITREP and RM components with underlying Eden schema [[BR]]
     90'''Time-bound  : ''' The exercise of understanding the data standards and mapping the elements should not take more than one week. developing a XSL to test the mapping may take another week, depending on the level of expertise with XML. (NB this is far too large a task for GCI. -- Pat)[[BR]]
     91'''Evaluate    : ''' The mapping table is the determining output. However, the example RM and SITREP files are also required. [[BR]]
     92'''Reevaluate  : ''' If the XSL transformation is developed, then the mapping can be tested with the sample RM and SITREP files [[BR]]
     94=== Review code for quality of localized strings ===
     96All strings which appear in the user interface, such as in menus and forms and help info, should be "internationalized" -- marked to make them available to be translated into different languages. This is done by putting the strings inside of {{{T( )}}}, e.g. {{{T("This string will be written into language files to be translated")}}}. The strings in {{{T( )}}} are keys that are used to look up translated strings. By convention, the key strings are in US English.
     98For GCI, you will need to review all the internationalized strings in the model and controller files for a single module, eg:
     99* {{{controllers\}}}, {{{models\}}}, and {{{views/gis/*.html}}}
     100* {{{controllers\}}}, {{{models\}}}, and {{{views/hrm/*.html}}}
     101* {{{controllers\}}} and {{{views/default/*.html}}}
     103Check for:
     104* Incomplete or cut-off sentences in the translation strings
     105* Avoid concatenation of localized strings with variables - use %s or %(key)s instead.  That is, instead of:[[br]]
     106  {{{T("My name is ") + name}}}[[br]]
     107  use this:[[br]]
     108  {{{T("My name is %s") % name}}}[[br]]
     109  And instead of:[[br]]
     110  {{{T("The item ") + item + T(" is not available in ") +}}}[[br]]
     111  use this:[[br]]
     112  {{{T("The item %(item)s is not available in %(place)s.") % {"item": item, "place":}}}}[[br]]
     113  This is better because the word order is not the same in all languages -- in the second form, the translator can move where the variables are inserted.
     114* Look for fields without a label - e.g. Field("fieldname") as these cannot be localised.
     115* Look at strings that have not been wrapped in {{{T( )}}} to see if they ought to be. But be cautious: Not all strings need to be localized, and some definitely should not be:
     116 * Strings that are used as keys in dicts, e.g. `{"this_is_a_key": 5}`, should not be localized.
     117 * A string that is intended to be in one specific language should not be localized (e.g. the language names in the language menu in {{{deployment-templates/models/}}}).
     118* Consider improving consistency of wording / terminology - don't use different strings that mean the same thing, e.g. if there is {{{T("My name is")}}} in one place, avoid using {{{T("I am called")}}} somewhere else.
     120You will need to download a working branch of Sahana Eden code for this task and push the changes you make to your own branch on Git.
     122Please focus on modules which are [ enabled by default].
     124== Intermediate ==
     126=== Feature Enhancements ===
     127 * Fix UI issues, add features, provide user-requested enhancements.
     128  * You can pick from these [/report/21 feature requests].
     130=== OSM Importer UI ===
     131 * There is an import stylesheet for .osm files: static/xslt/import/osm.xsl
     132 * This currently has hard-coded mappings between OSM admin levels & Sahana admin levels
     133  *  *
     134 * A custom controller should be written
     135  * provide a UI to the user to select their country from the dropdown which pre-populates the mapping fields for manual verification/adjustment
     136  * process the results of this to pass new variables back to the stylesheet:
     137   *
     139resource = s3xrc.resource("gis", "location")
     140template = os.path.join(request.folder, resource.XSLT_PATH, "osm", "import.xsl")
     141resource.import_xml("uploaded_filename.osm", template=template, mynewvar="xxx")
     143 * The Stylesheet needs updating to act on these vars when found
     145A nice further refinement would be to provide a UI to select a BBOX & optional filter to pull down the .osm file via [ XAPI]
     146 * Initially this could be manual text box entry of BBOX/filter
     147 * Then add a Map-based BBOX selection & dropdowns for the filter (which prepopulate the real dropdowns for manual verification/amendment)
     149=== Recurring Requests ===
     150e.g. Shelter needs 100 liters of water/week
     152Want to be able to add Scheduling functionality to Requests.
     154There is a wrapper for Web2Py's Scheduler class in {{{modules/s3/}}}
     156Can use UI ideas/code from Sync
     158=== Fix an Hard Ticket ===
     160Pick a bug report from, try to reproduce the issue in a local instance, fix the problem and submit a patch to the ticket on Trac, then notify the Sahana-Eden mailing list about your patch for verification.
     162=== Build library(ies) to integrate Emergency Data Exchange Language Distribution Element ===
     163Difficulty : '''HARD''' proposed by: [ | Nuwan] [[BR]]
     164'''Specific  : '''[ | EDXL-DE] is the final wrapper (envelope) of all [ | EDXL] data package. 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 package) 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. [[BR]]
     165'''Measurable: ''' It is purely a coding task that involves playing with XML and developing a class, possibly within or using the '''??? 3R**** ???''' framework It is basically a set of procedures for packing and unpacking EDXL-DE wrapped data. [[BR]]
     166'''Attainable: ''' run through the steps [[BR]]
     167Step 1 :: select one of the existing EDXL-based applications in Eden, I recommend the EDXL-RM [[BR]]
     168Step 2 :: discuss each of the attributes/elements; then determine how EDXL-DE would be added to EDXL-RM as a pop-up GUI. [[BR]]
     169Step 3 :: create some example XML files to get a feel for the inputs and outputs [[BR]]
     170Step 4 :: write code to add to take the inputs EDXL-RM and EDXL-DE to package the data for delivery [[BR]]
     171Step 5 :: test the code, fix bugs, and generalize the functions [[BR]]
     172Step 6 :: Apply to EDXL-HAVE and EDXL-SITREP to generalize the library [[BR]]
     173'''Relevant  : ''' Applies to Sahana Interoperability policy. Present developments to investigate are: HAVE, RM, and SITREP [[BR]]
     174'''Time-bound: ''' If steps 1 - 4 are completed that can be a full accomplishment; additional work is a bonus [[BR]]
     175'''Evaluate  : ''' Produce XML files with the EDXL-DE element appended to the EDXL-RM, SITREP, or HAVE[[BR]]
     176'''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 [[BR]]
     178== Advanced ==
     179Have a look at a BluePrint to see what advanced code contributions are needed.