Blackboard at Cornell University
Clare van den Blink, Cornell Information Technologies
www.cit.cornell.edu
www.blackboard.cornell.edu
1
Why Blackboard at Cornell?

Adopted in 1997.

Early version
developed at Cornell.
CourseInfo(CourseSite Generator)
Blackboard Active Course Sites
3,500
3,000
Scalability.
 Allow faculty to
maintain their own
sites with formsbased interface.

2,500
2,000
1,500
1,000
500
1999
www.blackboard.cornell.edu
2000
2001
2002
2003
2004
2005
2006
2
1997 – Now: Criteria Changes

Academic:

How does the CMS support and enhance the teaching and
learning process at Cornell University?
www.blackboard.cornell.edu
3
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?
www.blackboard.cornell.edu
4
1997 – Now: Criteria Changes

Academic:


Administrative:



How does the CMS support and enhance the teaching and
learning process at Cornell University?
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?
www.blackboard.cornell.edu
5
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)
www.blackboard.cornell.edu
6
Supporting Blackboard
Management of content growth.
 Scalable user support practices.
 Automating processes-outside of
Blackboard's tools.


Interaction with Registrar’s office & Library.
www.blackboard.cornell.edu
7
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.

www.blackboard.cornell.edu
8
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.

www.blackboard.cornell.edu
9