neelbhat88 / imuadev

2 stars 0 forks source link

History table to store expectations #264

Closed neelbhat88 closed 10 years ago

neelbhat88 commented 10 years ago

Create a table to store every time a expectation is changed for a student. Store as much info on this table as necessary, even if it seems redundant with other tables - WE DO NOT WANT TO DO ANY JOINS ON HISTORY TABLES

neelbhat88 commented 10 years ago

This will help with our validation of Expectations. We can use this to see how long, on average, it takes to switch an expectation from not meeting back to meeting, etc.

Jakeah commented 10 years ago

I'm going to have a 'See History' button that will display the history in a list. @kylegracey I'll leave any styling nuances up to you (meaning it's going to look lackluster when I commit to master).

Jakeah commented 10 years ago

@kylegracey Actually, I'll throw it in there and have it all functioning, but leave it commented out until you can get to it.

kylegracey commented 10 years ago

Yea thanks. I want to treat this one with care, for sure. I’ll definitely be wanting to hook it up to a basic d3js line graph as well… <3

On Wed, Sep 3, 2014 at 4:57 PM, Jake Connors notifications@github.com wrote:

@kylegracey Actually, I'll throw it in there and have it all functioning, but leave it commented out until you can get to it.

Reply to this email directly or view it on GitHub: https://github.com/neelbhat88/imuadev/issues/264#issuecomment-54373914

neelbhat88 commented 10 years ago

Yeah I imagine we'll worry about the front end of history stuff later. For now, as long as we are tracking it we can expose those pages whenever. We can put in a new task to create a page to show history in one of the next sprints

Neel [Sent via mobile phone] On Sep 3, 2014 5:58 PM, "Kyle Gracey" notifications@github.com wrote:

Yea thanks. I want to treat this one with care, for sure. I’ll definitely be wanting to hook it up to a basic d3js line graph as well… <3

On Wed, Sep 3, 2014 at 4:57 PM, Jake Connors notifications@github.com wrote:

@kylegracey Actually, I'll throw it in there and have it all

functioning, but leave it commented out until you can get to it.

Reply to this email directly or view it on GitHub: https://github.com/neelbhat88/imuadev/issues/264#issuecomment-54373914

— Reply to this email directly or view it on GitHub https://github.com/neelbhat88/imuadev/issues/264#issuecomment-54380299.

kylegracey commented 10 years ago

Perfect

On Wed, Sep 3, 2014 at 6:56 PM, neelbhat88 notifications@github.com wrote:

Yeah I imagine we'll worry about the front end of history stuff later. For now, as long as we are tracking it we can expose those pages whenever. We can put in a new task to create a page to show history in one of the next sprints Neel [Sent via mobile phone] On Sep 3, 2014 5:58 PM, "Kyle Gracey" notifications@github.com wrote:

Yea thanks. I want to treat this one with care, for sure. I’ll definitely be wanting to hook it up to a basic d3js line graph as well… <3

On Wed, Sep 3, 2014 at 4:57 PM, Jake Connors notifications@github.com wrote:

@kylegracey Actually, I'll throw it in there and have it all

functioning, but leave it commented out until you can get to it.

Reply to this email directly or view it on GitHub: https://github.com/neelbhat88/imuadev/issues/264#issuecomment-54373914

— Reply to this email directly or view it on GitHub https://github.com/neelbhat88/imuadev/issues/264#issuecomment-54380299.


Reply to this email directly or view it on GitHub: https://github.com/neelbhat88/imuadev/issues/264#issuecomment-54386330