add id column back to users table as change in requirements means that cage_code can no longer be a primary key - we will potentially be storing duplicates because multiple people from each company could sign up
created a rake task to run annotate then ran annotate since the id column is back in the users table now and I wanted the scheme information updated
removed the migration file that was used to make cage_code the primary key of the users table since I put the id column back in as primary key again.  This migration caused an update in spec/models/user_spec.rb because I had to remove the test for duplicate cage codes
updated test on uniqueness of email address as it was wrong