Added the basic MarketItemSummaries model to the app. Indexs may be necessary depending on load and the exact implementation of MIS updates and generation.
Having computer problems, running commit to backup code.
Rolled back a require line in spec_helper.rb that was based off old information about factorygirl. Commented the :market_order factory, and detailed how the factory accepts parameters.
Added bids boolean to market_item_summaries. This will allow for easily splitting out summaries based on type: buy or sell.
Began implementing market_item_summary factory only to realize that the factory may not be necessary. It has been left in a semi-complete, non-buggy state.
killing rvmrc with fire
fixing the gem reference
Merge remote-tracking branch 'upstream/marketSummaries' into fixing_broken_spec
Merge remote-tracking branch 'upstream/marketSummaries' into fixing_broken_spec
attempting to fix some of the failing tests

Recomendations
  Read the following
    https://github.com/styleguide/ruby
    http://betterspecs.org/
  Avoids
    $vars, especialy in specs
    let! if your not referencing the thing your creating
    find_by_foo is going away
  AREL and scopes are your friends
  where is good

  we should re-work some of your logic on this, your overkilling some things
  your cache times checkes arent really testing much, you may want to skip
  vcr for the moment because you dont care about the call for the chach, delorian
  or another time travel tool will help.
moving back to ruby 2.0
fixing a typo
Commiting before pulling in darkbushido's code.
Merge branch 'bug/fixing_cache_timers_specs' of github.com:darkbushido/market_monitor into bushidoMarketSummaries
Fixed error causing the accessMask not to be properly retrieved from the API's response.
Removed the before each block as it was useless and was not standardized with the other two specs. This should also fix the reference to timer.id.
Added user has many market_item_summaries relationship to the market_item_summaries and user models.
Built out the prepdb method for MISBuilder, this method deletes all users, apis and marketorders in the database then creates two new users, four new apis and 50 orders for each API. This gives each user 100 orders, 50 are corp and 50 are character. This should provide a useable testing bed for market_item_summaries.

Designed and built out the build function using the new queries I've learned in the last 72 hours. Much more intelligent .where queries are used, combined with hashes and API loops. The logic is much cleaner then the original design.
Changed the MarketOrder market_summary_id column's name to market_item_summary_id to match the proper name of the MarketItemSummaries model.
Renamed and updated the model file for MarketItemSummaries to match with conventions and the new table name.