(small but mighty idea) Support Disaster Response

What problem are you trying to solve / opportunity you're addressing?

AfG needs to be prepared to handle man-made and natural disasters (i.e. the
next 9.11 or katrina).
It's also a core priority with regard to our WH/CNCS partnership.

Describe the rough idea:

As discussed in our 8.19 planning mtg, we should look to (better) support
and respond to disasters via:

1. Tagging (disaster, etc.)
2. create a customized widget/gadget to support the distro to the masses.

** I believe 9.11,9/11, September 11 tag support was filed/handled
separately.  let me know if you'd like me to file that item as well.

Does this require anything beyond writing code?  if so, what?  where would
you get this?

1. UX treatment and ultimately communication out to our partners.

In the 18 month timeframe, how much impact could this have (number of
people impacted)?  have you considered all the steps involved (e.g.
approvals, user sign-ups, etc.) and whether they would slow us or limit
scale?

1. This should dramatically improve traffic during times of crisis and
limit the intense fire drills the team could endure coming form the WH in
the face of a disaster.

Can this be implemented in 3 months or less?  if not, why should we
prioritize this over big ideas that can be?

1. Yes, as I understand it from ENG/UX.

How does this impact users?

1. Improved search results and experience.

How does this impact organizers?

1. Improved search results and experience.

How does this leverage partners?

1. Improved search results and experience.

Does this bring up new legal/policy problems?

n/a (as far as I know).

Original issue reported on code.google.com by snesbitt@gmail.com on 20 Aug 2009 at 6:01

thegooglecodearchive / allforgood

(small but mighty idea) Support Disaster Response #527