-
Notifications
You must be signed in to change notification settings - Fork 0
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
create report history table #11
Comments
Instead of this, what about having a tab with the real-time twitter feed from https://twitter.com/EverySF311Bike and highlighting (and possibly also a way to filter by) the user's submitted reports? That will give them real-time feedback of their contribution as well as seeing recent contributions from others. |
It could work if we want to go with a view-only option. The longterm purpose of this table is to allow users to re-submit failed reports to 311, as well as add categories after-the-fact (to be submitted to our backend, not a resubmission to mobile311.) Easier said than done, of course. If you want to go with the Twitter feed option, let's open a new issue for it instead of replacing this one with it. |
I created a new issue for the twitter option (#17). I'm actually not entirely in favour of resubmitting failed reports because (a) real-time submission seems pretty reliable and (b) there's no way to back-date the submission so a report that was captured on Tuesday, but submitted on Wednesday will appear to 311 that it was reported on Wednesday. I think that adding categories after-the-fact should be handled by lanebreach/lanebreach-api#18. |
I think this is a valid concern, but we already know that choosing photos from the gallery to submit will have the wrong time stamp anyway so something to consider if do re-submits on failures |
create a table that displays a history of a user's reports, similar to sf311's:
This should display the following information:
In the event of a failed submission, the user can select a reload icon to quickly resubmit. Example:
The text was updated successfully, but these errors were encountered: