Proposed CS-OFIS Action Plan

Planning

• Examine current CS reports to determine what data is required to automate their preparation
• Examine non-CS reports to determine what generic data may be required later

Inquiry

• Determine which on-campus databases contain desired information (ask current OFIS team, faculty management)
• Determine which information is already in the current OFIS implementation and it's useability state

Analysis

• Obtain access to on-campus databases and assess state of data (is it useable? parseable? etc)
• Investigate current OFIS authentication practices
• Investigate need for faculty/graduate-student separation

Preparation

• Work with on-campus database administration to mend any data corruption/unuseability (i.e. multiple employee numbers, nexus IDs)

Implementation

• Create database structure suitable for the most general case usage (i.e. separate fields such as 'name' into 'last name', 'given name'), with minimum duplication of data (if possible, access campus databases directly)
• Create database user-interface for faculty use (inspection)
• Create report templates for CS reports (allow time period for other departments to prepare their templates, since data is likely to be at least partially faculty-wide)
• Implement data-retrieval and report-creation logic