search

City-of-Bloomington / inRoads

Digital service to publish road, sidewalk and parking status information including closings, lane reductions and reservations. Generates feeds for Waze Connected Cities program.
https://bloomington.in.gov/inroads
GNU Affero General Public License v3.0
9 stars 4 forks source link

Primary point of contact field #143

Closed charlesbrandt closed 6 years ago

charlesbrandt commented 6 years ago

Planning & Transportation has requested a new field for the primary point of contact. This should only be visible to logged in users. This would be for reference about who did the data entry. This is helpful when there are questions from other staff or the public.

inghamn commented 6 years ago

Should it be the person doing the data entry? Or should the data entry person choose who the contact person is? This is similar to Master Address; the data entry is not necessarily done by who's responsible for the event.

inghamn commented 6 years ago

In the meeting we said we wanted to capture the person doing the data entry as well as selecting a (possibly) different person as the point of contact. The point of contact is not often the person who's doing the entry in the web application.

inghamn commented 6 years ago

The person chooser requires #155

inghamn commented 6 years ago

Do we event want to be adding the point of contact as a "Person" in the system? Should it, instead, just be another plain text field that employees can type whatever they feel they need to about contact information?

charlesbrandt commented 6 years ago

I think it's fine if this is a plain text field.

inghamn commented 6 years ago

I'm all confused now. I think there's three things going on.

These three things can all be different people. Do we want to split out the publicly displayed contact info into a seperate field as well? Right now, employees mix that information into the event description.

An example: For a public works closing:

charlesbrandt commented 6 years ago

I think it's fine to keep publicly displayed contact information as part of the event description. If internal users want that as a separate field, I would rather add that later. So for now: