1 / 26

Emerging Learning and Collaborative Tools for Building Campus Community

Emerging Learning and Collaborative Tools for Building Campus Community. Peter Siegel, Vice Provost and CIO Elizabeth Gibson, Director. APRU – CIO Conference March 22, 2007. Conclusions - Up Front. Collaborative Tools are becoming more and more critical to our communities.

danyl
Download Presentation

Emerging Learning and Collaborative Tools for Building Campus Community

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Emerging Learning and Collaborative Tools for Building Campus Community Peter Siegel, Vice Provost and CIO Elizabeth Gibson, Director APRU – CIO Conference March 22, 2007

  2. Conclusions - Up Front • Collaborative Tools are becoming more and more critical to our communities. • Community Source “Learning” Tools are great building blocks for collaboration. • Learning <=> research <=> community bldg • Tremendous Opportunities exist to leverage campus and international interest in community source collaboration tools • Universities, consortia, and vendors all have a role • Learning / Collaborative tools need to be integrated in fabric of IT services • including administrative, research, and other tools

  3. Community Source Software • Definition - Wikipedia • Why Community Source ? • The Case for Sakai • The role of commercial partners (in Sakai) • UCDavis’s Experience with Community Source

  4. Sakai: A Community Source LMS • The role of Sakai in building community • Three venues: • Within the ‘Classroom’ • Across the campus • Off Campus (nationally and internationally)

  5. Collaborations • In the Course / Classroom • Student – Student • Group Projects • Chat / discussion boards • Wiki • Student – Faculty / TA • Ease of access, e.g. Feedback • Discussion Boards, Shared opinions • Application sharing, feedback – just in time…

  6. Sakai Collaborations: Wikis

  7. Sakai Collaborations: Discussion Boards

  8. Sakai Collaborations: Chat

  9. Collaborations • Collaborations across campus • Project sites • Faculty, Student, Staff, mixed… • New “Information and Educational Technology” (IET) Collaborations: • Teaching Resource Center (TRC) • Library • Professional Schools: Medical / Veterinary

  10. Collaborations • State, National and International Collaborations needing Project Sites • University of California • Partnerships with other Universities and Commercial Partners • Research sites • Campus communities sharing information globally

  11. Sakai at UCDavis • Status • Production • Medical School (Year 1 students) • Veterinary Medicine (Year 1 students) • Early Adopters • General campus:Music • Training Programs: faculty • Active • Ramping up for Spring Quarter

  12. Sakai at UCDavis • What’s working • Faculty Support • Integration with information systems • Quality Assurance (QA) Testing • What’s (sort of) not working (yet…) • Quiz Tool and Gradebook tool • Working , but some issues

  13. Future Goals • What we want to add in the future to Sakai • Open Source Portfolio Tool • Goal Management Tool • “High stakes” Testing • Live meeting tool • Digital Repository access • Course Evaluation tool • Tools targeted to Graduate Student Management

  14. More Community Building… • Other Tools Helping Build Communities: • Online Collaboration and Communications Applications • Confluence • Digital Repositories • Associated Activities Helping Build Communities: • SITT, FMFP, • “More Thoughtful Teaching” series

  15. Community Source, Community Building, and Service-Oriented Architectures QUESTION: How do Community Source applications relate to everything else we do? In other words: • How do we leverage our community tools into our administrative and support services and strategies?

  16. Community Source, Community Building, and Service-Oriented Architectures Answer: • Use building blocks that can work in a modular Service-Oriented Architecture (SOA) environment, to maximize interoperability, allow specific tools to be plugged in and out over time, and to reduce duplication, architectural dependence, and user effort

  17. SOA - Definitions • Definitions: • There is no widely-agreed upon definition • Wikipedia • An architecture that allows a range of (academic, administrative, and other) resources to interact as independent services which can be accessed without knowledge of their underlying platform implementation • Reworking of a definition at Wikipedia • Behind SOA is: • A philosophical commitment to creating and supporting modular building blocks that does at the enterprise level what “plug and play” has done at the individual computer operating system level

  18. Service Oriented Architectures • Link Academic and Administrative Services • Services: Each self-contained but connected through a common architecture • Mix of community, home-grown, and vendortechnologies • Including collaboration and learning tools identified above • HR and Student (Course) systems • College or departmental “customizations” welcome

  19. Middleware is key • Develop identity management and “roles” software • Allows security and access control on the administrative side (whether Financials or Learning Tools) • Allows community-related roles to propogate to collaboration tools

  20. Middleware is key Examples: • Allow only members of the financial affairs office to access this account • Let all chemistry students access this wiki • Enable all Eng 102 students to read this on-line material

  21. Status at Davis • Developed Identity Management Proposal, ready to enter first formal assessment phase • Testing role-based middleware • Deploying Shibboleth authentication software (from Internet2) as a core service with other UC campuses

  22. Goals • Deploy learning tools on broad basis • Integrate related tools as seamlessly as possible • Elluminate/Breeze, Digital Image software • Library services • Integrate with campus Content Mgmt System / Portals as they are engineered • Integrate with campus admin tools relating to courses • Integrate with middleware tools for identity, roles, and secure access

  23. Conclusions • Collaborative Tools are becoming more and more critical to our communities. • Community Source “Learning” Tools are great building blocks for collaboration. • Learning <=> research <=> community bldg • Tremendous Opportunities exist to leverage campus and international interest in community source collaboration tools • Universities, consortia, and vendors all have a role • Learning / Collaborative tools need to be integrated in fabric of IT services • including administrative, research, and departmental tools

  24. Questions to consider • What is role of central units (IT, Lib, Teaching Center) in identifying and supporting teaching and collaborative tools? • Is IT integrated enough to provide effective integration of collaborative tools with middleware and administrative tools? • If not, what partnerships are necessary?

  25. Questions to consider • What is the role of faculty in determining priorities in learning / collaborative tools? • Are there multiple teaching missions with different student groups: • - On-campus, distance education • Are multi-institutional consortia and services important to your campus?

  26. DISCUSSION

More Related