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

create report history table #11

Open
omegabytes opened this issue Feb 26, 2019 · 4 comments
Open

create report history table #11

omegabytes opened this issue Feb 26, 2019 · 4 comments

Comments

@omegabytes
Copy link

omegabytes commented Feb 26, 2019

create a table that displays a history of a user's reports, similar to sf311's:
image

This should display the following information:

  • submission status (pending, completed, failed)
  • date of report
  • image
  • location

In the event of a failed submission, the user can select a reload icon to quickly resubmit. Example:
image

@gumbypp
Copy link
Member

gumbypp commented Mar 26, 2019

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.

@omegabytes
Copy link
Author

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.

@gumbypp
Copy link
Member

gumbypp commented Mar 27, 2019

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.

@SherlockHomie
Copy link

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

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

No branches or pull requests

3 participants