1. Sakai & Next steps in Course Management David Millman dsm@columbia.edu April 2006

2. Millman -- 2006 April -- 2 Sakai Community source software development effort to design, build and deploy a new Collaboration and Learning Environment for higher education. –Started by U. Mich, Indiana U., MIT, Stanford –Mellon, Hewlett funded Columbia is a member of Sakai Educational Partners Program (SEPP) along with over 80 institutions and 12 commercial affiliates –CUIT and CCNMTL jointly funding partnership Web site: http://www.sakaiproject.org/http://www.sakaiproject.org/

3. Millman -- 2006 April -- 3 Why Sakai? Sakai is open, extensible platform that supports customization, development, rapid advancement Matches many existing CourseWorks features Has desired features not found in CourseWorks Community Development Model (with our peers) Leverages existing standards

4. Millman -- 2006 April -- 4 Current Status: Pilot Sakai Pilot Site - http://sakaipilot.cc.columbia.edu/http://sakaipilot.cc.columbia.edu/ Running on CUIT servers Ca 12 courses, 1,000 students Features not found in CourseWorks: –Improved file access, including WebDAV –Calendar, linked to assignments, announcements –Inline Assignments –Chat, Presence –RSS Feeds –Customizable interface –Cross-platform Web Editing Tool

5. Millman -- 2006 April -- 5 Active Development DateSpring, 2006Summer, 2006Fall, 2006Spring, 2007 Sakai Release2.1.22.2 Test Server2.1.2 Possible tool candidates: OSP 2.1 RWiki Blog Message Center 2.2 Possible tool candidates: Lancaster collab tools Others, TBD Production Server for Pilot 2.0.12.1.x 2.2.x

6. Millman -- 2006 April -- 6 Pilot Next Steps Monitor Sakai Progress - software, user feedback, governance, future funding model Upgrade Pilot for Fall 2006 - ePortfolio, Wiki, Blog, RSS, Editors, Message Center, Appearance (Skins) Determine top priorities –For use as CourseWorks platform –For non-course sites (research, admin, student) –As a development platform for new capabilities

7. Millman -- 2006 April -- 7 Library Integration: Today CLIOCourseworks course reserves workflow shared infrastructure (db)

8. Millman -- 2006 April -- 8 Library Integration: Options CLIOCourseworks next gen Institutional Repository Platform (e.g. DSpace) ?? ? ??

9. Millman -- 2006 April -- 9 Library Integration: Scaling CLIO Courseworks next gen Institutional Repository Platform A (e.g., articles) ? Institutional Repository Platform B (e.g., datasets) External repository C Custom course site D Syndicated search service E Personal citation-cart / annotation service F ?

10. Millman -- 2006 April -- 10 Library Integration: Scaling CLIO Courseworks next gen Institutional Repository Platform A (e.g., articles) ? Institutional Repository Platform B (e.g., datasets) External repository C Custom course site D Syndicated search service E Personal citation-cart / annotation service F ? Service

11. Millman -- 2006 April -- 11 Possible Architectures single sign-on (e.g., WIND, Shibboleth) OPAC viewRepository viewCourse mgmt view Study-group view shared infrastructure sakai platform external service

12. Millman -- 2006 April -- 12 Library/Repository Roles Library offers consistent metadata for all items used by the instructor Library should offer consistent service interfaces What are the right services? (e.g., Sakai twin peaks for search-type discovery)

13. Millman -- 2006 April -- 13 Sample “Service-Oriented” Architecture Repository Search Tag Subset “browser” CU Stacks Course Web Site Digital Journal

14. Millman -- 2006 April -- 14 Decisions Repository definition / collection scope Service definition Acquisition/publication definition Delivery to non-web-browsers (software agents, mobile devices) Services, not web sites?

15. Millman -- 2006 April -- 15 Personal Library vs. Research Library (Print) Individual selection criteria Personal shelving system understood only by individual Decision to lend material made by library owner No backup preservation Professional selectors in each field Standardized systems for cataloging and retrieval Lending policies and tracking system for distribution of content Duplicate copies in multiple libraries

16. Millman -- 2006 April -- 16 Individual Web-Environments vs. Scalable Digital Library Resources Develop individual digital teaching tool Broad range of approaches to citation and permissions Individual systems for tagging content Organize digital content for individual class Storage and access dependent on individual author Organize libraries of digital resources for reuse System to standardize citation and track IPR Consistent metadata enforced by workflow rules Automatic correlation of digital resources to general conceptual structures and standards Reliable access and archiving

17. Millman -- 2006 April -- 17 More Next Steps Journal of Jazz Studies (Fall ’06, Ford Foundation funding) Investigate service requirements through workflow “Spectrum of stability”

18. Millman -- 2006 April -- 18 Possible Spectrum Active collaboration Versioning Citable working- paper Publication Multiple users w/“collab space” functions File system metaphor / w/some metadata Institutional repository / metadata Preserved / archived / cataloged Scholarly research activity Library curation

19. Millman -- 2006 April -- 19 Research Questions How many discrete stages? What features are appropriate at each stage? What actions happen as content crosses stage boundaries? Can we create service requirements from these features?

20. Millman -- 2006 April -- 20 Immediate future Analysis, opportunity, leverage existing technologies & skills Incremental and iterative Research projects Socialization Policy

21. Millman -- 2006 April -- 21 Slides from Kim Cummings Rob Cartolano Kate Wittenberg

22. Millman -- 2006 April -- 22 Questions etc