title: Database design for weekly time tracking
body: <p>I am planning on creating a database to track user's time in/time out M-F.  Every week should begin on monday and run through sunday.</p>
  
  <p>I have a table filled with my entire user population, so I know which users I need to create entries for and where they belong to.  I have proposed so far, a table consisting of the following fields to track the entries (along with example data to fill the fields):</p>
  
  <pre><code>Field Name in table (Example of possible data)
  ---------------------
  Employee (John Smith) 'String
  Unit (Quality Assurance) 'String
  WeekOf (9/9/13) 'date
  
  InMonday (6:30) 'string, validate either a time in/out or N/A if holiday/vacation
  OutMonday (3:15) '^^
  HoursWorkedMonday (8.00) 'total hours worked
  VacationMonday (0.00) 'if N/A for time, should have hours here
  OvertimeMonday (0.00) 'any additional work hours should go here
  </code></pre>
  
  <p>For this instance, I would have to create In/Out for each day of the week (and perhaps track the date that each day is for). Is this extraneous or is there a seemingly better organization to tracking weekly time measurements?  Should I use one table with a unit indicator or multiple tables for each unit?</p>