search

WaterReporter / www.waterreporter.org

http://www.waterreporter.org
0 stars 1 forks source link

Single Report: Link/Callout to the assigned WaterKeeper #20

Closed joshuapowell closed 9 years ago

joshuapowell commented 9 years ago

When a user submits a Report via the mobile app, performs a lookup in the system to see if the Report falls under any defined Organization's jurisdiction. If so, an email is sent to the user with that information and the Organization is notified as well.

That information should be saved in the new API and if it is, then we should display that relationship here as well.

joshuapowell commented 9 years ago

Currently no WaterKeeper is being implicitly assigned ... we need to fix this in the API so that we can pull the appropriate "assignee" information;

See Issue #21

joshuapowell commented 9 years ago

Via @brendandm

So. Quick point about the new Water Reporter material. Essentially the idea is to use the existing geo-notification setup as a springboard for natural user groupings that lead to increased activity within the network. However, rather than having organizations with mash-up geographies, we’d use HUC12 watersheds as the core building block and allow people to assemble those into larger collections as needed. No Frankenstein boundaries for folks like David and Brent. They pick and choose what makes sense to them, but the basic spatial unit is standardized. On the user side, we capture what is now an ephemeral datum - the geometry in which they submitted a report - and store that as a relation. Each user then has a watershed collection that expands accordingly when/if they submit reports within other HUCs. That opens up possibilities for automatically filtering their feed (e.g. firehose or ‘only my watersheds’), allowing people to see who and what is happening around them, etc. On the admin side, it’s dead simple to alter or add an organization geometry since it’s just a collection of watersheds, not a single polygon. So we don’t need to perform queries on everything, just the affected HUC and then ping every admin whose watershed collection includes that HUC. Easier to automate that on the front-end someday because nobody has to draw weird polygons. It’s Water Reporter, right there in the name. Choose some watersheds and have at it.

brendan [1:56 PM] *Query on HUC collection, then pull in related admins. Poor sentence back there.

joshuapowell commented 9 years ago

This will not be implemented. The use of the WaterKeeper has changed.