aarontitus
commented
11 years ago From v...@aarontitus.net on February 25, 2013 16:59:51
- What about this approach: Create a "Demo" Incident that always appears on the login screen at the bottom. Perhaps we could even make this Demo Incident not require a username, password, User's name, or phone number. Perhaps it could be public, to allow people to "try before you buy," so to speak.
1.a. Yes. The organization can add, remove, change, update, claim, unclaim, (etc.) any incident in the Demo Incident. 1.b. All changes would be reset on a 6-, 12-, or 24-hour rotating basis. 1.c. Ideally, we want to ELIMINATE the "None" incident type. My understanding is that proper modularization of the Assessment Form data points will allow elimination of the "none" type. If the "None" type must always exist, then can we simply hide it from the form?
- If an organization claims a site, the demo would work just like a live site. Icons would change color, etc. I guess in order to truly demonstrate how the system works, we'll need to create a few default dummy organizations just for the Demo Incident, which have claimed several work sites.
- If the Demo Incident is public, then the contacts page should be populated with dummy contacts. If the Demo Incident is non-public, then I guess by default, ALL contacts for ALL other incidents would be listed by default. I favor populating the Demo Incident with dummy contacts.
4.a. If the Demo Incident is public, then no sharing should occur. 4.b. Yes, organization, contacts, and work order information should only be shared within a current event.
- Agreed. I suggest a big red warning at the top of the page: This is a demo incident, and all changes you make will be erased within X hours.
- Yes. We'll create a functioning Assessment Form, and then have some fun pre-populating the map with bogus work orders across the country. Once done, we'll save that state and reset every X hours.
- I only one realistic (and coincidentally easy) possibility: Pre-populate ~1,000 work orders across the country, then zoom into their area based upon their geocoded IP address. Trying to Pre-populate ~100 work orders with all information except lat/long would be harder. It would require us to geocode the IP address and then randomize the lat/long within a certain distance from there. Problems would arise when someone in another area logs in. What will they see? Will the existing work order lat/lon all be rest?
- Will the Demo Incident be public? My vote is yes.
See attached functional (but ugly) login screen.
Original author: andy.n.g...@gmail.com (February 25, 2013 05:54:43)
We need an incident that organizations can sign up to when they are not involved in a current incident.
There are some questions involved.
1) Can such an organization add sites? What happens to those sites once they are added? We want to avoid organizations using the None incident during a current disaster.
2) What happens when an such an organization claims sites?
3) How do we allow access to contacts? Should contacts only be shared within a current event?
4) How do we allow access to organizational information? Should org info only be shared within a current event?
5) We have to make sure to let the user know at every turn, that this is a demo version, not a live incident version.
6) Do we prepopulate with sites?
7) How do we represent those prepopulated sites on a map? Do we try to load sites near an organizations home area? Or in one area for everyone?
8) What other issues must be described before we continue to construction?
Original issue: http://code.google.com/p/sandy-disaster-recovery/issues/detail?id=200