Start with location information

[inghamn]

The request process should probably start with asking for the location information.

We are receiving a percentage of tickets these days where users are putting the location and contact information into the details field. Then, later on, on the location screen, they just skip over that; because they feel they've already provided that information in the details field.

The problem with this is that the details field is publically available information. We do not want people putting their address and phone numbers into that field. We want them to put them into the appropriate fields, so we can hide that information when we publish the ticket reports.

[inghamn]

33

[adabutch]

Via Linda today:

add default as 401 morton

"Near Buffa Louies & Starbucks"

---

POST Service Request Required Arguments:

via api

A full location parameter must be submitted. location parameter - One of lat & long or address_string or address_id

---

So, by intended design, if they don't know the exact spot, let them optionally fill anything they want in address_string to satisfy the API location parameter.

[adabutch]

Rather interesting note,

https://github.com/City-of-Bloomington/open311-nodejs/releases/tag/1.1.0

Notice the page reorder, Lucy, among others pushed for the location & personal info last.

[adabutch]

Page Order via v2:

Cat / Sec. Cat / Location / Info / Questions + submit

---

Check entires in ~6mo. for before vs after descriptions.