Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider designs for feedback loops to maintain drain data #200

Open
jasonlally opened this issue Nov 24, 2016 · 0 comments
Open

Consider designs for feedback loops to maintain drain data #200

jasonlally opened this issue Nov 24, 2016 · 0 comments

Comments

@jasonlally
Copy link
Contributor

Opening this issue to capture/discuss alternatives for creating feedback loops to help maintain drain data.

From @alocalsewerhistorian via #198

I'd recommend having some flag to show any drains adopted that have been deleted or even leave adopted drains which might be deleted by the update operation. We'd be happy to take a feedback loop (if possible). One idea would be to have a "data steward" contact field in the app and a "data quality" feedback, both for users who find items which are missing or not located properly and for this kind of update. Maybe some email auto-notification loop on update including listing any adopted drains which are deleted by update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant