====== Faculty Web Listing Automatic Updating ======
===== Options =====
**A**. Migrate tables to OIT run Oracle space; Web listing will query live database each time it is viewed; True real-time data; Current Access interface will still exist except to refer to the Oracle data 

   * Pros
     - Read-only views increase security
     - Multi-users simultaneously with no problem
     - Increased web platform support 
     - Real time web interface
   * Cons
     - High cost (time to pay skilled employee) involved and time consuming
     - Substantial research time required
     - Setup and testing required
     - Loss of direct administrative control

 **B**. Keep current Access database; Generate weekly report from existing Access database and manually upload a html'ized report to the web

   * Pros
     - Less implementation time involved
     - Little research time required
     - Administrative control is maintained
   * Cons
     - Inconsistency with data between Access database and web listing
     - Laborious, four uploads per month, 48 per year
     - Employee must be assigned the ongoing duty
     - Manual process allow room for errors
     - Time consuming depending on format and layout of presentation

 **C**. Keep current Access database; Dynamically generate the report from existing Access database onto the web

   * Pros
     - Data redundancy is eliminated, integrity is maintained
     - No manual upload needed
     - Real time information provided to end users. Users get exactly what is available in the database
   * Cons
     - Database possibly exposed to threats 
     - Significant research time needed
     - May not be possible to implement
     - Access database may not support web platform

===== Decision =====
     - Inquire John Fritz about any past or present works on existing faculty databases
     - Create immediate update (if manually even) of web data
     - Implement Option A Oracle