Metrics/stats viewable in application

[caseywatts]

How many people helped per day/month/year/etc. How many people a specific person helped. How much was each item used? How many times did a particular user check out items? frequency of problems reported on a per item basis

[ncmaas]

Some relevant information: http://4loc.wordpress.com/2008/12/25/date-arithmetric/

Are we thinking of making this pretty (like graphs, etc) or simply text based things? If we're going to try to implement graphs, I think this would be a sweet gem to use, and it seems to be well supported: https://www.ruby-toolbox.com/projects/googlecharts

[caseywatts]

This is also relevant: https://www.ruby-toolbox.com/categories/visualizing_data It might be super-easy to make graphs!

But just getting processed raw data is a much higher priority than graphing it for now.

[caseywatts]

Also: Shifts has a data analysis model "stats" that we could learn a lot from

[caseywatts]

Alsoalso: here's a super-useful set of js data-visualization tools we could use beyond ruby-toolbox's list (I think the ruby-toolbox ones will be great, but just as reference) http://selection.datavisualization.ch/

[noreaster]

studying shifts for guidance on how to get the raw data. The way I'm looking at it right now is that each report consists of a set of reservations (defined by a date range, a user/dept, a category/equipment model/object, or some combo). This set of reservations has data on it:

• the # or set of reserved/checked out/overdue/etc. reservations
• the amount of fees paid
• the users creating reservations
• the times when reservations are made/checked in/checked out

[noreaster]

So I've got counts for each of the various scopes(reserved, checked_out, etc.) and I'm outputting them to a simple table, with a count for all models, categories, and equipment_models

[noreaster]

merged into development, flexible report maker (only controller side, need to make a form for generating the flexible reports), sub reports, links

Need layout and formatting work

[noreaster]

should this be refactored to move the report creation into a model? Because reports should not be saved into the DB is the reason I created a model less controller

[noreaster]

also if we're creating a report generator, maybe I should shift for_model and for_model set into the generator as a canned reports

[adambray]

I'm not yet convinced we need a model for reports, but let's discuss this today in more depth.

[noreaster]

I haven't started working on putting a model into the reports, but I just wasn't sure how fat the controller should be.

[noreaster]

So the issue I was having with it not eager loading the users correctly is because the default scope ignores deleted users, but calling it individually has the default scope of allowing deleted users, which gives 2 different queries, thus breaking includes

[noreaster]

finished reservations list, cleaned up layout a bit, want to do a little bit of work on durations, but essentially done

[noreaster]

maybe another look at the layout

[mnquintana]

Layout done-ish - good enough for 3.0, but will probably be revised for 3.1.