localdata / localdata-dashboard Goto Github PK

Breaking the templates out of index.html will help with organization and hopefully will ease the transition to the new design.

• User logins
• Map interactions (clicks on responses)
• Deletes
• Form saves
• Exports
• Survey creations

Anything else?

Generally it’s visually cluttered and undifferentiated.

Questions and responses should be differentiated (color or simple icon, etc.) Right now they look the same, which is confusing/overwhelming

Add hierarchy in addition to indenting (for example have an icon or visual feature. e.g. a darker shade for an element higher up the hierarchy. It could be a 4px border on the left side of the question field or a lightly shaded background in the text box )

MH: this might require a DB maintenance script as well to enforce question type

(which alerts for the survey users)

Instead of checking for new results, we should check and see if any tiles have expired.

We need a flow similar to password reset, for when we create an account and the user logs in for the first time.

The tests should confirm the following overall flow (and ideally some pieces of it separately):

• create an org
• create an account within that org
• generate a password reset token with a reasonable expiration (a few days)
• reset the password using that token
• log in using the new password

... if you're not on the secure site.
Users should never get that error. Instead, they should be redirected to the secure site, or otherwise logged in seamlessly and securely.

Happily, leaflet is awesome and L.tileLayer has loading and load events!

When someone logs in, we have create an org and a user account and generated a URL with which they can reset their password.

ParcelNumber PropAddressCombined Structure on site(Y/N) Improved (Y/N) Empty (Y/N) VOD(Y/N) Condition (5-point scale??) Fire Damage (Y/N) Illegal dumping (Y/N) Environmental Hazard (Y/N - confirm)

See implementation questions at LocalData/localdata-mobile-web#43

Looks like an issue with our switch to / from satellite.

Zip codes

IRE Census data

Do we? Would save rendering time, for sure. Individual features are too hard to pick out, anyways.

A proposal: let's not change the map background based on zoom level.

1. The change from street => satellite may be confusing for some users.
2. The change creates consistent problems with disappearing data, zoom levels, etc.
3. Most sites do satellite as an on/off layer toggle. We can do that easily.

@prashtx -- thoughts?

We have created an org and an account. Folks can't just sign up for accounts on their own.

Yes/no could be red/green

Scales should have colors

A big problem, but we can make some good guesses.

Per LocalData/localdata-api#58

But maybe we don't want to show all the options (eg put survey questions behind a login wall)

When you attempt to delete a response from the dashboard but you don't own the survey, you don't see that your request failed.

Make it clearer what the export formats are and what people can do with them.

• hide "saved" message
• Fix save / close buttons
• Make "Add a question" better.
• Re-add icons
• style buttons
• Add interactivity
• Add form removal button

We should use a combination of stats and filtering to make this fast.

We use an elId property on views in a spot or two instead of el, which Backbone understands. We also wrap the view's element in jQuery (var $el = $(this.el)), even though Backbone gives us a cached, wrapped element (this.$el). We should take a scan and clean up some of that stuff.

This response type is common, and having to write out yes and no every time is a pain

Locate it at the bottom of the page and make it stand out visually.