SGID Data feedback system (Chalkdust)

[steveoh]

We currently have a dojo widget (super old) that runs in websites that we created (address editing) that makes an api request with user feedback and metadata about the map that they are viewing. This generates an email to the data group folks with the contents of the user feedback and a link to the chalkdust map viewer of where the user was on the map when they submitted the issue. They can also select a point to make it more accurate. People submit things like this road should be 600 north etc.

I've been actively migrating this system to the cloud and thinking that we could really expand on this feedback idea and create a system to capture and respond to feedback to engage our users and improve our data.

The general idea would be to improve and expand the chalkdust system that we have right now. Adding a database to the system would be great to allow us to have a queue of items to work on and their status. The database could even be github issues. This would allow us to use assignments, commenting, and closing of the issue which we could respond to the events generated and notify the person who submitted the issue etc.

The chalkdust viewer could list these issues on the map and we could navigate and act on them. This would end up being kind of the private ugrc view to the whole system.

To engage with our users we would need to create a bunch of public facing clients similar to the web api and the geocoding tools. I propose to create an api that people can send requests at, a pro/desktop add-in, as well as some website components, and something for the gis.utah.gov website to submit feedback that all use the api. All of these client submissions would feed into our chalkdust database and then get triaged yada yada.

Thoughts?

[nathankota]

Interesting idea! It's timely too, given the discussion in yesterday's Data Team meeting about bad Duchesne County (and various other counties') roads and address data. Although this feedback system would not fix the communication and data repair challenges that exist with counties, it would certainly be helpful to further quantify and communicate issues about their, and other, data sets that a wider audience (besides UGRC) is experiencing. The philosophical question of whether or not the data is ours if/when we rely on other stewards to maintain, fix, and provide it back to us still remains but, as you said, this tool could be great for engaging our users/clients/constituents, and fixing data that we truly "own". Just my initial, early a.m., coffee laden comments.

[gregbunce]

kudos! I think this is solid 2 thumbs up idea. This would drastically advance our efforts in data collaboration and feedback.

i think this is a key aspect:

I propose to create an api that people can send requests at, a pro/desktop add-in, as well as some website components, and something for the gis.utah.gov website to submit feedback that all use the api. All of these client submissions would feed into our chalkdust database and then get triaged yada yada.