= Occupy Sandy =
[[TOC]]

Occupy community hare currently leveraging their community mobilisation skills on supporting the victims of Hurricane Sandy through a project called [http://interoccupy.net/occupysandy/ OccupySandy].
* Sahana instances:
 * Production: http://sandyrelief.sahanafoundation.org
 * Test: http://sandyrelieftest.sahanafoundation.org
  * Can be used to test data imports and other training with dummy data
  * Can be used to test new code
  * Database refreshed from Production to test database migration during upgrades
 * Please only register if you are actively working on the project
* Code: Trunk with !SandyRelief template: https://github.com/flavour/eden/tree/master/private/templates/SandyRelief
* [http://eden.sahanafoundation.org/report/37 Open Tickets]
 * http://eden.sahanafoundation.org/report/37
* User Guidelines
 * [http://eden.sahanafoundation.org/raw-attachment/wiki/Deployments/Sandy/Occupy/Comms_Volunteer_Sahana_User_Onesheet.pdf One Page Guide] for new Comms staff
 * [UserGuidelines/Tutorial/RequestAndInventory User Guide for Requests & Inventory]
 * The list of gDocs which are being replaced: https://sites.google.com/site/occupysandydocs/
== Developers: Getting started ==
1. [http://eden.sahanafoundation.org/wiki/InstallationGuidelines Set up Sahana on your local machine]
2. Once you're done, set your models/000_config.py to use the SandyRelief template to see Erica's beautiful theme & have the other relevant settings. Also uncomment the settings.base.prepopulate = ["IFRC_Train"] line to get data.
3. Go through the tutorial in the online book: http://eden.sahanafoundation.org/wiki/Book
4. & join the community: http://eden.sahanafoundation.org/wiki#Contact
5. I also suggest that you join the #SandyRelief channel on Freenode IRC as that is where the users of the system will be, so yo
6. The current bug backlog is above
7. Direct questions to the email lists:
  * Desired Functionality: sahana@lists.occupy.net
  * Code: sahana-eden@googlegroups.com
8. admin@example.com, password testing


== Requirements ==
These should be written as User Stories: BluePrint/Guidelines

Raw:
* gDoc: https://docs.google.com/document/d/1ZUiAiEozox5dZbgf3W_JK3CZMx0xfNNjg67bGb24-1M/edit
* Hackpad: https://hackpad.com/uWF14mmRQqy#Sahana-Sandy

=== Requests ===
Hub Dispatchers want to log Requests into the system
* Supplies (1st priority)
* Volunteers
* Assets (needs enabling/testing)

Should we start simple, by just enabling the 'Other' type of Request so that all of the detail is in a free-text form?
- no need to fiddle with the item catalog
=== Inventory ===
Only a single process will be done:
* Daily Stock Take focussing on top 20-25 items & probably down to case level.
This will use the Stock Adjustment process, to which photos may be optionally added.
A dropdown can be used for the Item Selector.

Historical reports can also be produced from these (probably reqwuiring a little work down the line)

==== Old Ideas ====
Simplify intake form?
 * Hide CTN
 * Hide Price per Pack
 * Hide Status

Should we use simplified process for adding Stock? (i.e. direct access without going through stock adjustment. This is the current setting in HelpNY template)
* Also add ability to Send Shipment without having Stock yet added to Warehouse & record negative stock
 * This still allows accountability, so separate switch: inv.send_item_without_stock = True
 * /eden/inv/send/1/track_item currently has Item as a Dropdown from Warehouse Stock

Improve Item Selector
* Autocomplete+Add (nursix)
 * http://www.aliaspooryorik.com/blog/index.cfm/e/posts.details/post/adding-data-to-jquery-ui-autocomplete-342

Stock Reports should be visible to Public
* Transparency
* Make it clear what is NOT needed
=== Volunteers ===
==== Registration process ====
Current Registration form (which feeds CiviCRM):
* http://interoccupy.net/occupysandy/volunteer/

Implementation Notes:
* BluePrint/UserManagement

==== Sign-up to 'Tasks' (Skills Requests) ====
Port from Give2LA branch?
* https://code.launchpad.net/~flavour/sahana-eden/la

==== 'Sync' (!Import/Export) volunteers between Sahana & CiviCRM ====
nursix looking at with Jamie & Joseph from Occupy
* http://projects.occupy.net/projects/owsoutreach
* CiviCRM Imports: http://book.civicrm.org/developer/current/techniques/imports/
* Sahana REST API: wiki:S3XRC/RESTfulAPI
* [wiki:BluePrint/CiviCRMSynchronisation CiviCRM Data Synchronization]

==== Allocations of Volunteers to Tasks ====
Shoudl we buildon the Rostering tool?
* UserGuidelines/Rostering

=== Mapping ===
Hubs, Distribution Centers, Medical Clinics & Residential Buildings are all Types of org_facility.

This allows a common /map view & popup definitions.

* Types w diff Icons DONE
* Color-coding by whether they have an open / urgent request?
* !OnHover tooltip to show description DONE
* Click to show Requests (custom popup representation) DONE

* Embeddable map in other websites (iframe with flexible size) DONE

* Sync data with Google Fusion Tables?
 * At least write back to Fusion as this feeds Google Crisis Response
 * http://support.google.com/fusiontables/answer/2571232/?hl=en&

=== Recurring Requests ===
Fran DONE (mostly)

e.g. 3 people needed to serve hot food at lunch and dinner at this location - repeats daily
* Simple UI to the Scheduler - like is done for Sync currently

=== Smartphone access to forms ===
Need to define exactly which forms & decide whether to write custom /m pages for these forms or else develop a Mobile Theme (autodetected vuia WURFL?)

* BluePrint/Mobile/Portal

=== SMS Communications ===
We have access to the OccupySMS gateway (!MobileCommons) for both Inbound & Outbound SMS
* Inbound uses shortcode 69866 and is shared, so not all keywords are available for us.
* http://occupysms.org
* https://docs.google.com/document/d/1cGiQN9MRlYEXdjDHs1F60yuqCj9OpC4Y2xAawEQmb2w/edit
* http://www.mobilecommons.com/mobile-commons-api/
* Code:
 * Original/launch: https://github.com/cjohnson7/Sandy-Response
 * Improvements: https://github.com/disantlor/OccupySMS-Web