Sakai Project Sites: Who Uses Them & Why?

1. Sakai Project Sites: Who Uses Them & Why? Panelists: Stephanie Teasley & Emilee Rader, University of Michigan Wende Morgaine, Portland State University Jeff Narvid, University of California, Berkeley

2. Panel Participants • Stephanie Teasley & Emilee Rader School of InformationUsability, Support, and Evaluation (USE) Lab University of Michigan • Wende Morgaine & Nate AngellOffice of Academic Affairs & Web Communications Portland State University • Jeff NarvidTraining and Support Team University of California, Berkeley

3. Thoughts about Project Sites • “We’re doing a bake-off between Sakai & Moodle. But that might not be a good idea. Now I understand what we’d be missing if we go with Moodle [which doesn’t have project site capability].” • – small college IT administrator • “We were uncertain about project sites, so we just turn them on by request from faculty.” • – public university IT administrator

4. Goals/Purpose of This Session • Provide quick history of project site capability. • Present an overview of project site use at UM, Portland State, & Texas State. • Discuss various use cases to illuminate the potential of project sites. • Answer questions about project site support and training issues.

5. History of Project Sites • CourseTools use at UM led to the creation of WorkTools.

6. More History • UM’s CourseTools became “CTNG” where course site and project site capability was available in the same application (CHEF architecture). • Creation of Sakai preserved this dual use for CTools. • At UM, we faced migration issues to move users off WorkTools into CTools. • started May, 2005 until WTs server turned off in August 2005.

7. CTools Project Sites • As of May 21, 2006: • 7,223 Project Sites • 10,764 Course Sites • 69,125 Users

8. bSpace Project Sites

9. Project Sites Data Set • All project sites existing on Dec 31, ’05 • Analyzed event logs from Jan 1,’05 to Dec 31, ’05 • There were 1251 existing sites, inactive in 2005 • Identified 3169 “active sites” (sites with events on more than one day in 2005) Fall term Sp/Summer term Winter term Jan 06 Sept Jan 05 May WTs Migration

10. Event Log (!)

11. Weekly Average Project Site Events

12. Project Site Events by Week (2005)

13. Project Sites Used by Week (2005)

14. Final Data Set • Included only sites with more than one event on more than one day • Removed “extreme” sites to create picture of “typical use.” • Top 20% of sites with total events and total users counts. • Total “typical sites” in analysis n = 2253

15. Typical Sites: Descriptives

16. Typical Sites: Comparing Tool Use

17. Typical Sites: Comparative Tool Use

18. Typical Sites: Resource Use

19. Most Common Resources File Types (1) • Microsoft Word (67753) • PDF (39586) • Images (23998) • HTML (19577) • Unknown (15823) • Microsoft Excel (11682) • Microsoft PowerPoint (11322) • URL (11268)

20. Most Common Resources File Types (2) • Plain text (4307) • Zip or other archive (1775) • Audio (1635) • Video (1527) • Rich text (776) • Postscript (554) • Microsoft Visio (375)

21. Resource File Structure of Research Site

22. Resource File Structure of Admin Site

23. Project Sites: Who and Why

24. Top 50 Most Active Sites... • 17 admin (electronic reserves, faculty searches, hr initiative) • 20 learning (course resources, student course projects) • 7 research (research activities not associated with a particular course) • 6 extracurricular (fraternity, sorority, choral group, nonprofit run by students)

25. Examples of Interesting Cases • Faculty co-writing book “Right now I am using bSpace to store documents that I am working on with other people. One is a book project, and we have all of the working drafts of our book on line so the two co-authors and the permissions editor can access them. The others are smaller paper projects or executive education offerings.”

26. Examples of Interesting Cases • Staff use “I see resources as being a primary tool for us. We're a campus staff organization, with maybe 60-80 people on our mailing list. We'd like them to be able to go to a site, look for resource links to information, or find slide-shows of past presentations or meetings, templates with various functionality.”

27. Examples of Interesting Cases • Planning for future uses “After our first use of bSpace this summer, we anticipate creating additional project sites for teachers and students who are working together, and for staff to use in collaborating on grant proposals and other projects.”

28. Project Site Problems • Sakai development focused on LMS use (no separate tool set) • No version control (Wiki?) • No groups/sections • Public/private site listing

29. bSpace Project Site Survey • Q1: How do you currently use bSpace to support your project(s)? Tell us your story. • Q 2: How do the current bSpace tools, such as Announcements and Resources, coincide with how you would like to use a collaboration and learning environment? • Q3: How do you anticipate using bSpace in the future? • Q4: What, if any, additional bSpace training and support would you like from Educational Technology Services (ETS)? Check all that apply. • Q5: If you indicated in Question 4 above that you would like additional training and support from ETS, please elaborate on exactly what tutorials, workshop topics, etc. would be helpful to you. • Q6: Have you or would you recommend bSpace to a colleague?

30. Questions?

31. Contact Information • Stephanie Teasley – CTools, University of Michigansteasley@umich.edu • Emilee Rader – School of Information, University of Michigan ejrader@umich.edu • Wende Morgaine – Office of Academic Affairs, Portland State Universitywendemm@gmail.com • Nate Angell – Web Communications, Portland State Universityangell@pdx.edu • Jeff Narvid – bSpace, University of California, Berkeleyjeffn@media.berkeley.edu

32. Typical Sites: Resource Events

33. Typical Sites: Resources Events