-
Notifications
You must be signed in to change notification settings - Fork 1
Workflows
Christian Gass edited this page Feb 13, 2017
·
2 revisions
Some details about the technical flow of i/o between the user, browser, server, and database.
- Select a venue from a table or a map, on a dedicated "start" page.
- App takes you to the data entry form page, where it has loaded all data from the database for your selection into the form.
- You make changes, or don't, and hit submit.
- A verification modal pops-up with a summary of everything. You click
keep editing
to return to form, ordone!
to submit it. - On the backend, the
json
representation of the form as stored in the FishFryFormClass instance is passed to the Flask app, which assembles the call to the CARTO SQL API, and writes the data. - You are sent back to the page from step 1 with a
flash
that indicates the success of your submission. - Your submission will appear on the table and map, but with the
validated
field auto-checked and thus the row or point symbolized as such.
- On the start page, click a "create new" button.
- App takes you to the data entry form page, which is totally blank.
- You add information as you like.
- When you add the address and geocode, a point is placed on the map on the screen.
- When done, hit submit.
- A verification modal pops-up with a summary of everything. You click
keep editing
to return to form, ordone!
to submit it. - On the backend, the
json
representation of the form as stored in the FishFryFormClass instance is passed to the Flask app, which assembles the API call to CARTO and writes the data. - You are sent back to the page from step 1 with a
flash
that indicates success of your submission. - Your submission will appear on the table and map, but with the
validated
field auto-checked and thus the row or point symbolized as such.