= Taiwan =
Sahana Taiwan are customising & deploying an instance of Sahana Eden.

Initially this is to complement their [http://sahana.tw Sahana Agasti deployment].

Forum about the SahanaTW deployment http://groups.google.com.tw/group/sahanatw

The proposal is for this to replace Agasti completely next year.

NCDR (National Science & Technology Center for Disaster Reduction) have a high tech EOC based around ESRI's ArcGIS.
However, they are unable to get the data to local governments easily due to licensing costs, so a combination of !GeoServer & Eden could help fill this niche.
They are also interested in Sahana being able to feed their EOC with crowd-sourced data such as from SMS & Twitter.

Coordination is being dfone using this group: http://groups.google.com.tw/group/sahanatwpy

There is a demo site up at: http://py.sahana.tw/eden

Enhancements that the Sahana Taiwan team are interested in:

== New Home Page ==
 * Provide a summarized page for info overview and status updating (frequency configurable)
 * Allow unauthenticated users to 'Report Incident' (Missing Person, Request Help or Incident) or 'Offer Help' (Volunteer or Pledge Resources)
 * provide top-level stats about # resources registered in system
 * Map overview
 * See attachment

== GIS / Mapping ==
Check http://bazaar.launchpad.net/~flavour/sahana-eden/trunk/files/head:/views/gis/ for updated codes in gis views

Configured to use openstreetmap.tw & Google layers

~~Want to be able to overlay data from Agasti onto the Eden Map:~~
~~* Shelters~~


There is an Agasti stylesheet under-development: {{{static/formats/agasti/import.xsl}}}
 * This could be used to import records on a scheduled basis


=== Location Selector ===
~~Use Taiwan's 4 levels of hierarchy~~ (In-Trunk - just needs localising)
Import L1 to L3 Administration Data:

 
 * ~~Show the dropdowns & populate the lower dropdown when then the one above is selected (detect dropdown change using jQuery & collect new results using AJAX)~~ (In-Trunk, still needs more tweaking)
  * {{{views/gis/location_autocomplete.js}}}
  * see if the different levels can be precached to a store to minimise user waiting?
 * Context-sensitive filtering of dropdown (or Autocomplete) to the appropriate level
{{{
db.gis_location.requires = IS_ONE_OF(db.gis_location, db.gis_location.id, filterby="level", filteropts="L4")
}}}
 * ~~Only allow Admins to edit the L0->L3 levels~~ (In-Trunk)
 * Fix #450 (Prevent an L2 being added as parent of L3, etc)
 * Local Geocoder service to allow users to enter street address
  * Add Geocoder to {{{modules/s3gis.py}}}
  * Provide a widget within locations picker to call this function
 * ~~[wiki:BluePrintGISSelectLocationFromMap Select from Map]~~ (In-Trunk)

== Messaging ==
 * A local SMS Gateway is working with the system.
 * This has been tested with [http://en.wikipedia.org/wiki/Big5 Big5 encoding].

== Incident Reporting ==
 * #508

== Authentication ==
 * Want to be able to have users login once to access resources on both systems.
  * OpenID support has been added to Web2Py/Eden
  * Rewrite Agasti to access Eden user table? auth_user
   * Better to hack the legacy Agasti rather then the end-goal Eden

== Authorization ==
 * TaiwanAuthorisation
   * Briefing 
     * Access control is able to create and edit
     * Read/write and read only should be separate for each role to each module.
     * For registry users, default access is limited since registry is open to public.
     * Each role is separate and independent. Each user is open to give multiple roles.
     * There are 3 types of confidentiality level for map. Each level is an independent module for role setting.
     * Special access control for “fulfill the request”

 * Want defined Roles to be active on both systems
  * Memberships should only be defined once
   * Rewrite Agasti to access Eden membership table? auth_membership
    * Better to hack the legacy Agasti rather then the end-goal Eden
 * Need support for the 'Shelter Administrator' and request fullfillment role 

== Localisation ==
Translation into Chinese is underway

== Person Registry ==

Six status types:
 1. missing
 2. deceased
 3. alive and placed
 4. injured and placed
 5. alive and not placed
 6. injured and in hospital
 7. injured and not placed
 8. other

For status type 3 and 4, the place location should be selected.
If there's hospital module in Agasti, status type 6 should associate with a chosen hospital. 

Note by Dominic:

  There are no "missing persons" in Eden, but just "persons", and neither "missing" nor "found" actually define a status of a person, but both are handled as "events" on a trail.

  The fact that someone is missing a person is gathered by a "missing report", which is basically a search request indicating that someone is seeking information about a person. The submission of a missing report is also recorded as a "missing" event, regardless of whether the person is currently missing or found.

  The fact that a person has been "found" is likewise an event report about the respective person covering the where, when and condition (temporary or permanent stay, known or unknown current/next location) of the "find", and this is as well independent of whether the person is missing or not.

  Both "missing" as well as "found" events are recorded by the same type of event report called "presence", which forms an observation trail over time.

  All "presence" records contain a location, time and description of the respective event, differentiated into:

  Presence condition:

        1) missing
        2) deceased
        3) seen at a location
        4) placed at a location

  Health status (not implemented yet, but planned):

        1) well-being
        2) injured
        3) ill
        4) unknown

  Procedure (free text up to now), e.g.:

        1) treatment in hospital
        2) accomodation in IDP camp
        3) evacuation from a region

  The missing "status" as you understand it is actually the answer to the following question:

  Is there any "found" event after the time the "missing" report has been submitted, and if yes, has the person who has submitted the "missing" report been notified about that?

  But "presence" can document/answer more questions beyond "missing", e.g.:

    a) procedure status
    b) placement in shelters (currently being implemented)
    c) checkpoints in evacuation
    d) tracking/tracing of staff and volunteers

  etc.

  "Presence" is, btw, not limited to persons, but as well used for

  - groups
  - organisations/offices
  - dead bodies
  - personal effects
  - vehicles and other property items

----
[wiki:Deployments] [wiki:TaiwanSettings]