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

Mobile App - Add/View Field Reported Data #657

Open
NaveenP94 opened this issue Jun 15, 2016 · 2 comments
Open

Mobile App - Add/View Field Reported Data #657

NaveenP94 opened this issue Jun 15, 2016 · 2 comments

Comments

@NaveenP94
Copy link
Collaborator

NaveenP94 commented Jun 15, 2016

From the home profile screen when the user clicks the button to report data, they will be brought to this page that is a form to report data. This form serves the same purpose as the one found on https://crisischeckin-d.azurewebsites.net/ under "Report New Data"

From the home profile screen when the user clicks Disaster Field Data they will be brought to a different page that displays a table similar to https://crisischeckin-d.azurewebsites.net/Volunteer/ListResourceCheckinsbyDisaster however it will use the users most recent disaster checkin to filter what disaster DB this data is pulled from.
(as visual for this page is not included in the wireframe and left to the creativity of the dev to design)

Back End:
**NOTE since this DB hold resource data as well we would like the type to be standardized to "Delivered- item name_" for reporting canvasing and "Hazard- hazard type" . (see wireframe for more examples)

These pages will require read/write access to the field reported data DB and pull the users most recent checked in disaster from the users commitments table.

@AgileAwlReet
Copy link

I'll give this one a try

@tonysurma
Copy link
Member

Thx, FYI not noted here but fhilton was asking q's about this one so not sure if they are working on it as well

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

3 participants