1. Blackboard at Cornell University Clare van den Blink, Cornell Information Technologies www.cit.cornell.edu www.blackboard.cornell.edu1

2. Why Blackboard at Cornell? Adopted in 1997. Early version developed at Cornell. CourseInfo(CourseSite Generator) Scalability. Allow faculty to maintain their own sites with forms- based interface. 2www.blackboard.cornell.edu

3. 1997 – Now: Criteria Changes Academic: How does the CMS support and enhance the teaching and learning process at Cornell University? 3www.blackboard.cornell.edu

4. 1997 – Now: Criteria Changes Academic: How does the CMS support and enhance the teaching and learning process at Cornell University? Administrative: How well does the CMS perform course management tasks and course administration? How easily can faculty and students be supported? 4www.blackboard.cornell.edu

5. 1997 – Now: Criteria Changes Academic: How does the CMS support and enhance the teaching and learning process at Cornell University? Administrative: How well does the CMS perform course management tasks and course administration? How easily can faculty and students be supported? Infrastructure: What are the IT and support requirements? Are they consistent with CU’s IT architecture and support models? 5www.blackboard.cornell.edu

6. Blackboard Use Currently, about 5,500 courses & 30,000 active users. Most frequently used features are: Course Information and/or Course Documents Announcements and Send Email. Assignments and Gradebook. Provides critical features for large course management. Other features: Tests and quizzes Collaboration (including chat and virtual classroom) 6www.blackboard.cornell.edu

7. Supporting Blackboard Management of content growth. Scalable user support practices. Automating processes-outside of Blackboard's tools. Interaction with Registrar’s office & Library. 7www.blackboard.cornell.edu

8. Issues to Consider What are the critical features in a CMS? Typically, most features are not fully utilized. Features to use & not use? Not all features are enabled at Cornell due to local practices & policies. Some features still need to be developed locally, i.e. authentication & automation. 8www.blackboard.cornell.edu

9. Issues to Consider Support cycle for courses and content. Governance and policies. In 1997, no policies in place - have evolved over time. Product Upgrade Cycles Impact on support and user experience. New features may mean new processes & policy review, i.e. SafeAssign in Blackboard. 9www.blackboard.cornell.edu