snayrouz / bike-share Goto Github PK

we can do this tomorrow morning. I've noticed a few things in the csv tables that could hurt us down the road if we aren't careful. Would love to hear everyone's thoughts tomorrow.

Great job team!

https://gist.github.com/mimilettd/6e1a0def9d4fee9e4e7adb12f45ec9bc

I'm simply adding this card now because if you come across a cool site or photo or anything you'd want to use for styling, save it and we can brainstorm together when we get there.

Display following information:

Total count of stations
Average bikes available per station (based on docks).
Most bikes available at a station (based on docks).
Station(s) where the most bikes are available (based on docks).
Fewest bikes available at a station (based on docks).
Station(s) where the fewest bikes are available (based on docks).
Most recently installed station.
Oldest station.

Get all tags in line (html pun). Special attention to show and dashboard views.

1 feature test for dashboard
model tests for AR methods

This we can discuss as a group tomorrow once we've all read through the spec a few times. That way if we ever work individually, we have a standard procedure in place

Ability to have an admin enter a start station and end station ID. We'll have to put a boolean in our methods in the Trip model

We have a few failing tests, need to go back and take a look.

display information on one or more of your dashboards

First card woohoo!! I was just reading through the spec and it seems like we'll have view folders for stations, trips and conditions(weather). Each folder will contain an edit, index, new, show, dashboard specific erb file.

create drop down and add validations

Looks like 'foreach' is the way we want to go. I'm still struggling with csv things so I'd love to be a part of these changes when you make them

Deploy application to heroku

We have the layout from the classroom practice we did today but just wanted to remind everyone so there aren't any troubles later on

Should read station_id: start_station_id

https://www.kaggle.com/benhamner/sf-bay-area-bike-share

Just reading through the data and the spec, I want to discuss the possibility of making more than 3 models but on having 3 views. Meaning the possibility of having a 'City' model given that a city 'has many' stations. We can also discuss associations off the bat that are clear and possibly finding associations to help manipulate the data better.