FloodNotifications - Revision history

GearyEppley: /* Gage Details */

2020-09-21T21:47:49Z

Gage Details

GearyEppley at 21:46, 21 September 2020

2020-09-21T21:46:11Z

GearyEppley at 21:40, 21 September 2020

2020-09-21T21:40:04Z

GearyEppley: /* Subscription Page */

2020-08-19T21:38:46Z

Subscription Page

GearyEppley at 16:25, 19 August 2020

2020-08-19T16:25:41Z

GearyEppley at 21:31, 16 August 2020

2020-08-16T21:31:13Z

DaveSanderman at 16:25, 20 April 2020

2020-04-20T16:25:39Z

DaveSanderman: Created page with "== Flood Notifications == We intend to build a system which will allow users to sign up for notifications when a particular set of gages they're interested in has reach flood..."

2020-03-20T22:35:32Z

Created page with "== Flood Notifications == We intend to build a system which will allow users to sign up for notifications when a particular set of gages they're interested in has reach flood..."

New page

== Flood Notifications ==

We intend to build a system which will allow users to sign up for notifications when a particular set of gages they're interested in has reach flood stage, and again when the waters have receded.

=== Requirements ===

* A user will be able to give an email address which will receive timely notifications of flood status changes.

==== Possible Requirements ====

* Other notification channels besides email
** Text message?
** Phone calls?

==== Explicit Non-Requirements ====

* We will not support sending notifications to non-registered users (i.e. you can't just give us an email address, you have to create an account with a password)

=== Open Questions ===

* How frequently will notifications go out?

=== Building Blocks ===

This will depend on implementing LoginAndSecurity. Also, future-flood notifications will depend on FloodForecasting.

@@ Line 85: / Line 85: @@
 !Conditions
 |-
-|Green
+|Normal
 |Below XX.X ft
 |-
-|Yellow
+|Near Flooding
 |At and above XX.X ft
 (0.5 ft below road saddle)
 |-
-|Red
+|Flooding
 |At and above YY.Y ft
 (road saddle level)
@@ Line 118: / Line 118: @@
 Body:
-  Gage: <link>[ID] [Name]</link>
+  Gage: <nowiki><link></nowiki>[ID] [Name]<nowiki></link></nowiki>
   Last reading at 12:00 pm, 9/12/2020

@@ Line 115: / Line 115: @@
 =====Email Notification=====
 Subject:
-  [status] [ID] [Name] - Gage Status Changed
+  [status]: [ID] [Name] - Gage Status Changed
 Body:
@@ Line 133: / Line 133: @@
   Snoqualmie Valley Preservation Alliance (SVPA)
 Tolt Avenue, Carnation, WA 98014

← Older revision		Revision as of 21:40, 21 September 2020
Line 112:		Line 112:

	*should have way to unsubscribe from email and SMS (STOP)		*should have way to unsubscribe from email and SMS (STOP)
		+
		+	=====Email Notification=====
		+	Subject:
		+	[status] [ID] [Name] - Gage Status Changed
		+
		+	Body:
		+	Gage: <link>[ID] [Name]</link>
		+
		+	Last reading at 12:00 pm, 9/12/2020
		+	Status: [status]
		+	XX.XX ft / YY.YY ft over\|below road level (OR "at road level")
		+
		+	Trend:
		+	Rising\|Falling at XX.X ft/hr
		+	Projected to be at road level at 12:00 pm
		+
		+	--
		+	Floodzilla Gage Network - <link>https://floodzilla.svpa.us</link>
		+	We sent this email to [email]: <link>unsubscribe</link>
		+	Snoqualmie Valley Preservation Alliance (SVPA)
		+	4621 Tolt Avenue, Carnation, WA 98014

@@ Line 61: / Line 61: @@
 A background task will run at some appropriate frequency to monitor the state of all notifiable events.
-== Phase 1 - Fall 2020 ==
+==Phase 1 - Fall 2020==
-=== Features ===
+===Features===
-* Email & SMS support (SMS can be phase 1.5)
+*Email & SMS support (SMS can be phase 1.5)
-* Subscribe to all status changes for a gage (can't pick and choose for phase 1)
+*Subscribe to all status changes for a gage (can't pick and choose for phase 1)
-=== Events ===
+===Events===
-* The events for phase I are all status changes: green to yellow, yellow to red, red to green, green to red, green to offline, etc..
+*The events for phase I are all status changes: green to yellow, yellow to red, red to green, green to red, green to offline, etc..
-* We will include 'offline' as a notification worthy status change
+*We will include 'offline' as a notification worthy status change
-* For gages with associated roads, the red status should align to the road going under and the yellow status should be 6" or so below, just before water is on the road surface.
+*For gages with associated roads, the red status should align to the road going under and the yellow status should be 6" or so below, just before water is on the road surface.
-=== UX ===
+===UX===
-==== Gage Details ====
+====Gage Details====
-* Add a card titled 'Status Levels'
+*Add a card titled 'Status Levels'
 {| class="wikitable"
@@ Line 99: / Line 99: @@
 |}
-* If user is not logged in when they click 'subscribe' pop-up to create / login form
+*If user is not logged in when they click 'subscribe' pop-up to create / login form
-==== Subscription Page ====
+====Subscription Page====
-==== Notifications ====
+*Check box to receive alerts via email and sms (grayed out if email/sms not verified)
-* should have way to unsubscribe from email and SMS (STOP)
+*add / change phone number

@@ Line 99: / Line 99: @@
 |}
-====== Subscription Page ======
+* If user is not logged in when they click 'subscribe' pop-up to create / login form
-<br />

@@ Line 1: / Line 1: @@
-== Flood Notifications ==
+==Flood Notifications==
 We intend to build a system which will allow users to sign up for notifications when a particular set of gages they're interested in has reach flood stage, and again when the waters have receded.
-=== Requirements ===
+===Requirements===
-* A user will be able to give an email address which will receive timely notifications of flood status changes.
+*A user will be able to give an email address or phone number which will receive timely notifications of flood status changes.
-* Various kinds of events can be separately subscribed to per gage:
+*Various kinds of events can be separately subscribed to per gage:
-** Flood status begins (define a notification water level threshold per gage?)
+**Flood status begins (define a notification water level threshold per gage?)
-** Road underwater
+**Road underwater
-** Road clear
+**Road clear
-* When it becomes possible to predict flood events, each predictable event should have a separate notification
+*When it becomes possible to predict flood events, each predictable event should have a separate notification
-==== Possible Requirements ====
+====Possible Requirements====
-* Other notification channels besides email
+*Other notification channels besides email
-** Text message?
+**Text message - Yes
-** Phone calls?
+**Phone calls - Maybe future
-* Other notification events that are not per-gage
+*Other notification events that are not per-gage
-** Region-wide "flood event starting"?
+**Region-wide "flood event starting" (At some point we should incorporate the NWRFC forecast alerting that OG Floodzilla does and migrate users into this new site)
-==== Explicit Non-Requirements ====
+====Explicit Non-Requirements====
-* We will not support sending notifications to non-registered users (i.e. you can't just give us an email address, you have to create an account with a password)
+*We will not support sending notifications to non-registered users (i.e. you can't just give us an email address, you have to create an account with a password)
-=== Open Questions ===
+===Open Questions===
-* How frequently will notifications go out?
+*How frequently will notifications go out?
-* Do we need to have per-user or per-gage memory of last time a notification happened for a particular gage to avoid spam? (example: water level reaches road, goes below road level, goes above, all within a short period of time)
+*Do we need to have per-user or per-gage memory of last time a notification happened for a particular gage to avoid spam? (example: water level reaches road, goes below road level, goes above, all within a short period of time)
-* Do we need to track history of notifications we sent? If so, how and where?
+*Do we need to track history of notifications we sent? If so, how and where?
-== Building Blocks ==
+==Building Blocks==
 This will depend on implementing LoginAndSecurity.  Also, future-flood notifications will depend on FloodForecasting.
-=== Email Notifications ===
+===Email Notifications===
 Doing email notifications will depend on (at least) having these features:
-==== Email address verification ====
+====Email address verification====
 Add a workflow for verifying email addresses:
-==== Subscription management ====
+*Remember verification status (flag already exists in database; need to verify it works and clear all existing statuses)
 Each individual event that can be subscribed to will need a subscribe/unsubscribe UI.
@@ Line 56: / Line 57: @@
 There will also need to be a simple "Unsubscribe me from all notifications" page that the email notifications can link to.
-==== Background processing ====
+====Background processing====
 A background task will run at some appropriate frequency to monitor the state of all notifiable events.