Difference between revisions of "Software Task List"
| (2 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
==== Main Site ==== | ==== Main Site ==== | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
TASK: Front page rework | TASK: Front page rework | ||
| Line 30: | Line 15: | ||
* Current system is noisy when there's a flood | * Current system is noisy when there's a flood | ||
* Suppress messages when a river is hovering around notification stage level | * Suppress messages when a river is hovering around notification stage level | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
TASK: build a queue/pipeline system for processing new data (new readings, new forecasts, etc) | TASK: build a queue/pipeline system for processing new data (new readings, new forecasts, etc) | ||
| Line 48: | Line 28: | ||
TASK: build a test/staging database and environment | TASK: build a test/staging database and environment | ||
| + | |||
| + | TASK: Figure out site error reporting (e.g. database is down, site is down, etc) | ||
| + | * #site-errors in Slack? | ||
==== Admin Tools ==== | ==== Admin Tools ==== | ||
| Line 60: | Line 43: | ||
TASK: Per-gage notification lists for flood levels, offline status, etc | TASK: Per-gage notification lists for flood levels, offline status, etc | ||
* primarily for Gage Stewards | * primarily for Gage Stewards | ||
| + | |||
| + | TASK: Make sure "log book" entries are created for all admin actions | ||
==== Data ==== | ==== Data ==== | ||
Latest revision as of 02:06, 22 March 2023
Contents
Software Task List
Next Tasks in Priority Order
Grab Bag
This is an unordered, unprioritized, incomplete list of pending tasks.
Main Site
TASK: Front page rework
- Spec
TASK: Rework flood notifications to allow summary/batching of emails/SMS
- Current system is noisy when there's a flood
- Suppress messages when a river is hovering around notification stage level
TASK: build a queue/pipeline system for processing new data (new readings, new forecasts, etc)
- example reading steps: Preprocess (e.g. remove Senix non-reading posts), Filter invalid/offline data, Mark possible crests, Notifications
- example forecast steps: Preprocess, Build downstream predictions, Notifications
TASK: allow more complex chart views (maybe this is Admin-only?)
- battery level
- "missing" readings
- better zoom/navigation
Infrastructure
TASK: build a test/staging database and environment
TASK: Figure out site error reporting (e.g. database is down, site is down, etc)
- #site-errors in Slack?
Admin Tools
TASK: Rework how Device creation happens
- don't require user to input ID
- if we get a reading from an unknown device, create the device object
TASK: USGS Admin
- currently, adding new USGS gages requires direct database access
TASK: Per-gage notification lists for flood levels, offline status, etc
- primarily for Gage Stewards
TASK: Make sure "log book" entries are created for all admin actions
Data
TASK: recalculate data for 124th West to take into account resurvey.
TASK: recalculate data for Tolt Hill to take into account resurvey.
Wiki
TASK: Wiki permissions changes: Allow edits only from users with verified email addresses.
TASK: Document wiki administration, installation, etc.
TASK: Ensure all passwords/secrets are in password manager.
