| 69 | | ==== OSM Importer UI ==== |
| 70 | | * There is an import stylesheet for .osm files: static/xslt/import/osm.xsl |
| 71 | | * This currently has hard-coded mappings between OSM admin levels & Sahana admin levels |
| 72 | | * * http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative#10_admin_level_values_for_specific_countries |
| 73 | | * A custom controller should be written |
| 74 | | * provide a UI to the user to select their country from the dropdown which pre-populates the mapping fields for manual verification/adjustment |
| 75 | | * process the results of this to pass new variables back to the stylesheet: |
| 76 | | * http://pub.nursix.org/eden/s3xrc/vita.modules.s3xrc.s3rest.S3Resource-class.html#import_xml |
| 77 | | {{{ |
| 78 | | resource = s3xrc.resource("gis", "location") |
| 79 | | template = os.path.join(request.folder, resource.XSLT_PATH, "osm", "import.xsl") |
| 80 | | resource.import_xml("uploaded_filename.osm", template=template, mynewvar="xxx") |
| 81 | | }}} |
| 82 | | * The Stylesheet needs updating to act on these vars when found |
| 83 | | |
| 84 | | A nice further refinement would be to provide a UI to select a BBOX & optional filter to pull down the .osm file via [http://wiki.openstreetmap.org/wiki/XAPI XAPI] |
| 85 | | * Initially this could be manual text box entry of BBOX/filter |
| 86 | | * Then add a Map-based BBOX selection & dropdowns for the filter (which prepopulate the real dropdowns for manual verification/amendment) |
| 87 | | |
| 88 | | === Recurring Requests === |
| 89 | | e.g. Shelter needs 100 liters of water/week |
| 90 | | |
| 91 | | Want to be able to add Scheduling functionality to Requests. |
| 92 | | |
| 93 | | There is a wrapper for Web2Py's Scheduler class in {{{modules/s3/s3task.py}}} |
| 94 | | |
| 95 | | Can use UI ideas/code from Sync |
| | 80 | === Map elements between EDXL-SITREP and EDXL-RM === |
| | 81 | Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]] |
| | 82 | '''Specific : ''' There are several elements within the [http://tinyurl.com/bn9nxty | EDXL-SITREP] data standard that are identical to that of [http://docs.oasis-open.org/emergency/edxl-rm/v1.0/EDXL-RM-SPEC-V1.0.pdf | 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]] |
| | 85 | Step 1 :: Go through EDXL-RM and EDXL-SITREP documentations [[BR]] |
| | 86 | Step 2 :: create example files to get an understanding of the data and structure [[BR]] |
| | 87 | Step 3 :: develop the table with RM and SITREP elements with a description [[BR]] |
| | 88 | Step 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]] |
| | 93 | |
| | 94 | === Review code for quality of localized strings === |
| | 95 | '''''Migrated'''''[[br]] |
| | 96 | All 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. |
| | 97 | |
| | 98 | For GCI, you will need to review all the internationalized strings in the model and controller files for a single module, eg: |
| | 99 | * {{{controllers\gis.py}}}, {{{models\gis.py}}}, and {{{views/gis/*.html}}} |
| | 100 | * {{{controllers\hrm.py}}}, {{{models\hrm.py}}}, and {{{views/hrm/*.html}}} |
| | 101 | * {{{controllers\default.py}}} and {{{views/default/*.html}}} |
| | 102 | |
| | 103 | Check 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 ") + location.name}}}[[br]] |
| | 111 | use this:[[br]] |
| | 112 | {{{T("The item %(item)s is not available in %(place)s.") % {"item": item, "place": location.name}}}}[[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/000_config.py}}}). |
| | 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. |
| | 119 | |
| | 120 | You 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. |
| | 121 | |
| | 122 | Please focus on modules which are [https://github.com/flavour/eden/blob/master/deployment-templates/models/000_config.py#L427 enabled by default]. |
| | 123 | |
| | 124 | == Intermediate == |
| | 125 | |
| | 126 | === Feature Enhancements === |
| | 127 | * Fix UI issues, add features, provide user-requested enhancements. |
| | 128 | * You can pick from these [/report/21 feature requests]. |
| | 129 | |
| | 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 | * * http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative#10_admin_level_values_for_specific_countries |
| | 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 | * http://pub.nursix.org/eden/s3xrc/vita.modules.s3xrc.s3rest.S3Resource-class.html#import_xml |
| | 138 | {{{ |
| | 139 | resource = s3xrc.resource("gis", "location") |
| | 140 | template = os.path.join(request.folder, resource.XSLT_PATH, "osm", "import.xsl") |
| | 141 | resource.import_xml("uploaded_filename.osm", template=template, mynewvar="xxx") |
| | 142 | }}} |
| | 143 | * The Stylesheet needs updating to act on these vars when found |
| | 144 | |
| | 145 | A nice further refinement would be to provide a UI to select a BBOX & optional filter to pull down the .osm file via [http://wiki.openstreetmap.org/wiki/XAPI 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) |
| | 148 | |
| | 149 | === Recurring Requests === |
| | 150 | e.g. Shelter needs 100 liters of water/week |
| | 151 | |
| | 152 | Want to be able to add Scheduling functionality to Requests. |
| | 153 | |
| | 154 | There is a wrapper for Web2Py's Scheduler class in {{{modules/s3/s3task.py}}} |
| | 155 | |
| | 156 | Can use UI ideas/code from Sync |
| | 157 | |
| | 158 | ==== Fix an Hard Ticket ==== |
| | 159 | http://eden.sahanafoundation.org/report/1 |
| | 160 | Pick a bug report from http://eden.sahanafoundation.org/report/1, 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. |
| | 161 | |
| | 162 | === Build library(ies) to integrate Emergency Data Exchange Language Distribution Element === |
| | 163 | Difficulty : '''HARD''' proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan] [[BR]] |
| | 164 | '''Specific : '''[http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf | EDXL-DE] is the final wrapper (envelope) of all [http://en.wikipedia.org/wiki/EDXL | 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]] |
| | 167 | Step 1 :: select one of the existing EDXL-based applications in Eden, I recommend the EDXL-RM [[BR]] |
| | 168 | Step 2 :: discuss each of the attributes/elements; then determine how EDXL-DE would be added to EDXL-RM as a pop-up GUI. [[BR]] |
| | 169 | Step 3 :: create some example XML files to get a feel for the inputs and outputs [[BR]] |
| | 170 | Step 4 :: write code to add to take the inputs EDXL-RM and EDXL-DE to package the data for delivery [[BR]] |
| | 171 | Step 5 :: test the code, fix bugs, and generalize the functions [[BR]] |
| | 172 | Step 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 http://www.oasis-open.org/standards#edxl [[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]] |
| | 177 | |
| | 178 | == Advanced == |
| | 179 | Have a look at a BluePrint to see what advanced code contributions are needed. |
| | 180 | |
