Changes between Version 3 and Version 4 of Projects/Quick


Ignore:
Timestamp:
11/02/13 11:58:25 (7 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Projects/Quick

    v3 v4  
    1515Easy tickets to get started on are listed here: http://eden.sahanafoundation.org/report/18
    1616
    17 === Common Operational Datasets [GCI] ===
    18 ''Added to GCI spreadsheet.''[[br]]
    19  * Purpose and schemas for common datasets (schemas are at end): http://oneresponse.info/resources/imtoolbox/publicdocuments/IASC%20Guidelines%20on%20Common%20Operational%20Datasets%20in%20Disaster%20Preparedness%20and%20Response%201%20Nov.%202010.pdf
    20  * Add model definitions for these schemas. This work was started but is not included in the current version of Eden. An example from an old version is here: [http://bazaar.launchpad.net/~flavour/sahana-eden/trunk/view/head:/models/08_assess.py#L1825 models/08_assess.py]
    21  * Think about how we could make use of them.
    22   * Display on the Map?
    23   * Have Reports which compare the baseline & situational assessments?
     17=== Common Operational Datasets ===
     18* Purpose and schemas for common datasets (schemas are at end): http://oneresponse.info/resources/imtoolbox/publicdocuments/IASC%20Guidelines%20on%20Common%20Operational%20Datasets%20in%20Disaster%20Preparedness%20and%20Response%201%20Nov.%202010.pdf
     19* Add model definitions for these schemas. This work was started but is not included in the current version of Eden. An example from an old version is here: [http://bazaar.launchpad.net/~flavour/sahana-eden/trunk/view/head:/models/08_assess.py#L1825 models/08_assess.py]
     20* Think about how we could make use of them.
     21 * Display on the Map?
     22 * Have Reports which compare the baseline & situational assessments?
    2423
    25 === GIS/Mapping [GCI, multiple tasks] ===
    26 ''Added to GCI spreadsheet''[[BR]]
     24=== GIS/Mapping [multiple tasks] ===
    2725These are various GIS/Mapping Tasks:
    28  * [=#AddOnHoverDelay]'''Add a delay to the onHover tooltip''' (highlightControl)
    29   * Something like [http://cherne.net/brian/resources/jquery.hoverIntent.html hoverIntent]
    30  * [=#PotlatchIntegration]'''Continue Integration of [http://wiki.openstreetmap.org/wiki/Potlatch_2/Deploying_Potlatch_2 Potlatch]'''
    31   * for editing the main OSM database
    32   * for editing a local OSM database
    33  * [=#FeaturePopupWindow]'''Make the display_feature() & display_features() popup a Window''' instead of opening in a DIV
    34   * This was working in FF before: http://eden.sahanafoundation.org/browser/views/sahana_scripts_min.html?rev=836#L39
    35  * [=#GeoExtMeasure]'''Replace the Measure !Length/Area tools with [http://trac.geoext.org/wiki/ux/Measure GeoExt.ux]'''
    36  * ~~[=#FullScreenMap]Option to go Full screen & back~~
    37   * ~~Full screen view (No Ext window) will be required for use on a small-screen, such as a Mobile device~~ (completed by aviraldg)
    38  * [=#LayerTree]'''[http://dev.geoext.org/trunk/geoext/examples/tree.html Layer Tree]'''
    39  * [=#LookupPresence]'''Create a pr/person/presence record upon login''' if HTML5 !GeoLocation available & has changed since last time
    40   * login_next
    41  * [=#MapPreview]'''Map Preview when !Lat/Lon set in pr/person/presence''' (auto or not)
     26* [=#AddOnHoverDelay]'''Add a delay to the onHover tooltip''' (highlightControl)
     27 * Something like [http://cherne.net/brian/resources/jquery.hoverIntent.html hoverIntent]
     28* [=#PotlatchIntegration]'''Continue Integration of [http://wiki.openstreetmap.org/wiki/Potlatch_2/Deploying_Potlatch_2 Potlatch]'''
     29 * for editing the main OSM database
     30 * for editing a local OSM database
     31* [=#FeaturePopupWindow]'''Make the display_feature() & display_features() popup a Window''' instead of opening in a DIV
     32 * This was working in FF before: http://eden.sahanafoundation.org/browser/views/sahana_scripts_min.html?rev=836#L39
     33* [=#GeoExtMeasure]'''Replace the Measure !Length/Area tools with [http://trac.geoext.org/wiki/ux/Measure GeoExt.ux]'''
     34* [=#LayerTree]'''[http://dev.geoext.org/trunk/geoext/examples/tree.html Layer Tree]'''
     35* [=#LookupPresence]'''Create a pr/person/presence record upon login''' if HTML5 !GeoLocation available & has changed since last time
     36 * login_next
     37* [=#MapPreview]'''Map Preview when !Lat/Lon set in pr/person/presence''' (auto or not)
    4238
    4339[wiki:DeveloperGuidelinesGIS Use the Mapping API to:]
    44  * [=#ColorCodedMaps]'''Color coded maps according to Geo-data''' (threats, needs, etc)
    45  * [=#VariableSizedMarkers]'''Place variable sized markers on the map in proportion to data''' (number of people in camp, number of families needing food)
     40* [=#ColorCodedMaps]'''Color coded maps according to Geo-data''' (threats, needs, etc)
     41* [=#VariableSizedMarkers]'''Place variable sized markers on the map in proportion to data''' (number of people in camp, number of families needing food)
    4642
    4743=== !Lat/Lon converter [GCI] ===
    48 ''Added to GCI spreadsheet''[[BR]]
    4944Portuguese Volunteer Firefighters ([Deployments/Portugal/Bombeiros Bombeiros]) use Eden.
    5045
     
    5752
    5853=== Scale Uploaded Images [GCI] ===
    59 ''Added to GCI spreadsheet''[[BR]]
    6054When images are uploaded we can limit the size, however larger pictures should be scaled instead. Example: personal profile picture.
    6155
    62  * [This part is done, see #1016] This should be implemented as a Validator {{{modules/s3/s3validators.py}}}).  The size limitation should be configurable in the model for that specific field, with a sensible default.
    63 
    64  * [GCI task, #1017] UI to to allow user to crop image (this would be a widget: {{{modules/s3/s3widgets.py}}})
    65   * Ideally 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?
    66   * Maybe: http://labs.corefive.com/Projects/FileManager/ (e.g. from http://code.google.com/p/django-ckeditor-filemanager/ )
    67 
    68 === Suggestion Box [GCI] ===
    69 ~~''Added to GCI spreadsheet''[[BR]]
    70 (Original suggestion from: http://groups.google.com/group/sahana-eden/browse_thread/thread/bbda1e98b73e1437)
    71 
    72 Here are some potential features for a "suggestion box", roughly in order of priority:[[BR]]
    73 ''For GCI, the first four bullets are the task.''~~
    74  * ~~Text data entry form -- just use standard Eden database fields like "timestamp", "authorstamp", and "comments", maybe with a subject field.~~
    75  * ~~Allow defining topics or keywords. Let user choose a topic for their suggestion. Add all module names as an initial list of topics. (Perhaps add a suggestion_topic table for this, and allow a suggestion to have multiple topics.)~~
    76  * ~~Simple search in the body of posts -- match words.~~
    77  * ~~Allow commenting on (replying to) suggestions -- show comment thread with original post. (Note threading now works with a normal comment field, so should not need to do much for this but see how it's handled for other comments.)~~ (completed by aviraldg)
    78  * Regexp search.
    79  * Some form of importance rating (e.g. voting up or down).
     56* [GCI task, #1017] UI to to allow user to crop image (this would be a widget: {{{modules/s3/s3widgets.py}}})
     57 * Ideally 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?
     58 * Maybe: http://labs.corefive.com/Projects/FileManager/ (e.g. from http://code.google.com/p/django-ckeditor-filemanager/ )
    8059
    8160=== Map elements between EDXL-SITREP and EDXL-RM ===
     
    9776
    9877=== Feature Enhancements ===
    99  * Fix UI issues, add features, provide user-requested enhancements.
    100   * You can pick from these [/report/21 feature requests].
     78* Fix UI issues, add features, provide user-requested enhancements.
     79 * You can pick from these [/report/21 feature requests].
    10180
    10281=== OSM Importer UI [GCI] ===
    103 ''Added to GCI spreadsheet.''[[BR]]
    10482
    10583==== Current Status ====
     
    1221004. We would like to be able to download features for a Polygon
    123101 * Provide a map window with a Polygon selector tool which then triggers a download of a suitably-filtered .osm file via the [http://wiki.openstreetmap.org/wiki/Overpass_API Overpass API]
     102
    124103=== Fix a Hard Ticket ===
    125104http://eden.sahanafoundation.org/report/1
    126105Pick 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.
    127 
    128 === Build library(ies) to integrate Emergency Data Exchange Language Distribution Element ===
    129 ''Not added to GCI spreadsheet -- outside time bounds. Can it be split or cut down?''[[BR]]
    130 Difficulty : '''HARD''' proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan] [[BR]]
    131 '''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]]
    132 '''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]]
    133 '''Attainable: ''' run through the steps [[BR]]
    134 Step 1 :: select one of the existing EDXL-based applications in Eden, I recommend the EDXL-RM [[BR]]
    135 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]]
    136 Step 3 :: create some example XML files to get a feel for the inputs and outputs [[BR]]
    137 Step 4 :: write code to add to take the inputs EDXL-RM and EDXL-DE to package the data for delivery [[BR]]
    138 Step 5 :: test the code, fix bugs, and generalize the functions [[BR]]
    139 Step 6 :: Apply to EDXL-HAVE and EDXL-SITREP to generalize the library [[BR]]
    140 '''Relevant  : ''' Applies to Sahana Interoperability policy. Present developments to investigate are: HAVE, RM, and SITREP http://www.oasis-open.org/standards#edxl [[BR]]
    141 '''Time-bound: ''' If steps 1 - 4 are completed that can be a full accomplishment; additional work is a bonus [[BR]]
    142 '''Evaluate  : ''' Produce XML files with the EDXL-DE element appended to the EDXL-RM, SITREP, or HAVE[[BR]]
    143 '''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