codeforamerica/cityvoice

A place-based call-in system for gathering and sharing community feedback

cityvoice's Issues

Turn off polygon-scrollover on landing page map

Add demo order info to backend

Will be a string in property_info_set

Update modal on landing page

Change map markers to reflect demo status

e.g. one color (orange?) could be used for those properties with an affirmed demo and another (current blue?) could be used for all others

Fix lat-longs to use parcel data centroids

Courtesy of @ttmp

landing page: modal blocks the ability to manipulate the map

If you close the modal the problem disappears. Also if you start manipulating the map before the whole page loads you can continue to edit it with the modal open.

We might fix by changing how the js loads.

Add demo order info to views

The attribute will be called demo_order, for example

@subject.property_info_set.demo_order 

a string, with potential values of:

"Expired", "Affirmed", blank

Typeahead broken in Firefox v19

...but works in latest versions (22, 23)

Has something to do with the document.location.origin property being undefined in that version of FF.

(Low-priority bug)

@mholubowski is checking it out

Deploy functional staging instance (w/ password protection)

Add about page

Same phone # can submit info for multiple properties

Currently the session doesn't take into account if you're giving feedback on a different property code; change that so that 1 phone number can provide feedback on multiple properties.

Set up hard connection to Socrata endpoint

To download and refresh data; may want to use a modified version of windy or the (alpha) SODA API wrapper

Integrate addresses into search bar (typeahead)

Proposed Approach:

1. Rake task that pulls down data from Socrata, and creates a JSON file of just the addresses and tax IDs
2. Upload (maybe part of Rake task?) the JSON file to S3
3. Make search bar pre-fetch the JSON from S3

Potential issues:

• Need to test how long the load of the JSON file takes on a deploy (may want to make appearance of bar conditional upon the data having been loaded)

Other ideas:

• Load into DB, use API endpoint for typeahead

Property page status info should be more colorful

Currently the two key pieces of information are status and demolition order. Perhaps the icons for these could be in color, ideally reflecting the level of urgency (V&A more urgent than occupied; Demo order affirmed more urgent than no demo order).

Add Icons for Poll and Voice Responses

Create Contact page

Create branch with "no comments" and deploy for testing alternate workflow

Add shapefile to map for Monroe Park Neighborhood

(or whichever neighborhood we want to test)

Fix home button link

Make all of landing map moveable

Right now, the "click to move" functionality doesn't work on areas of the map horizontal to the explanatory overlay.

Potentially related to #12

Moving back a page in browser breaks the app (Chrome)

This is true for the landing page and subjects pages

Fix Carroll/Columbia issue in Monroe Park

Add example text in search bar "search addresses..."

Set up Google Analytics

Property data "legend" page to explain icons & data

It'd be good to provide a page that explains the different categories of data (ie, where "Moderate Repairs Needed" is on the spectrum), and maybe provide some more contextual data (eg, this is in the top 30% of values)

Maybe this is a modal that opens if you click on something in the the property data area of the page? ("explain" or "learn about this" or whatever)

What you think @rduecyg @ttmp ?

Add icons for property statuses

Neighborhood association on the property page link should spawn to a new tab or window

Add password protection for staging deploy

Add content and style map pop-ups

Change some question texts

Per @rduecyg: Can we change the question_text wording to: "How important is improving public safety in your neighborhood? (1-5 scale)" "How important is improving property values in your neighborhood? (1-5 scale)"

fix landing page footer links

Add RailsAdmin for basic backend management

Hover-over explanation of Demolition Order

Make property-level view have marker at real lat/long

Add ability to upvote a voice message

Add visual poll tags to each audio file

Make map show just a point if the "subject" is a property

For the property view, we want to modify the map to basically map the name attribute (the name will be the address).

So, for example, in the view, it will go something like this:

@subject.name
# => "1234 LaSalle Avenue"
# Below is a fake Leaflet call to express the logic
LeafletMap.place_marker_at_address(@subject.name)

Set up domain for Monroe Park trial

On Subjects view hide Opinions and Voice Messages if none exist for the property

Change Text Responses

Submission B:
Thanks! We recorded your response “Demolish” for property 1234 Lincoln Way West. You can also text comments to this number. Learn more: 1000in1000.com/1234

Comment:
Thanks for your comments! Your feedback will be reviewed by city staff. Please tell your neighbors about this program. Visit 1000in1000.com/1234.

Transfer ownership to CFA Heroku and turn on 1 web dyno

To avoid spin-up time

Put map zoom on right side of map

Move map zoom control on landing page

Load neighborhood data into database for views

Requires both:

1. Joining neighborhoods onto the properties
2. Creating neighborhood entries as part of data-load

Opinion tag for voice messages

Attach a visual tag to voice messages indicating how that person voted. (e.g. repair or remove in V&A deploy)

Aaron Perri brought this up for the IWTW deploy and I'm sure once Code Enforcement starts playing with the feedback will want this bit of information as well.

Implement secondary font (Rokkit google fonts)

Implement property codes

Will be 5-digit codes, with the "duplicate indexing" occurring in the last digit.

1234 Main St => "12340"
1234 Lasalle St => "12341"

For 3-digit street numbers, here's a question:

987 Main
"98700" or "09870"

play button doesn't show in deployed website

audio player play button shows on local version of site but not on heroku deployment

Set up A/B testing for call-in method

Create records in the database to distinguish feedback based on how people got the property code, namely:

• Sign
• Neighborhood association list
• Flyer
• Web site

Filter/validate input

Ideally done at point of input, with "invalid" response, but could be hacked for now to simply exclude presentation of bad input in view.