Extend the data management capabilites of omCollab

[Sean.McClowry]

1. Document the data model for omCollab into a relational model; this can be reverse engineered from phpmyadmin
   

2. Define a logical design approach for extending the data model to store history that is optimized for end-user reporting. For example:
   

• History tables
  
• General report data models, optimized for large volume queries
  
• Documented recommendations on how to extend this approach
  

3. Build a common data access framework for accessing data that manages connections for creates, reads, updates and deletes as well as opening and closing of connections
   

4. Migrate existing connections to this new data access framework
   

5. Implement a new reporting and analytics tool across the platform that meets the requirements defined here
   using an existing open source tool

6. Move existing home page portlets to this new reporting tool
   

7. Work with developers implementing new porlets to use this framework on 168 and 157
   

8. Create and implement upgrade scripts to move any existing reporting or data functionality to this new approach