1. Course Management Project Update Marc Brierley

2. Course Management WG Who are we? Stanford - Marc Brierley (PM and interaction designer), Daisy Flemming (developer) U of Arizona - Duffy Gillman (PM and developer) UC Berkeley - Oliver Heyer (PM), Josh Holzman (lead developer), Daphne Ogle & Judy Stern (interaction designers)

3. Who are we (also)? Stanford - Lydia Li (developer) Oracle/IMS - Linda Feng Also... –Mark Norton –Ray Davis

4. Glossary SIS - Student information system (e.g. Oracle’s Campus Solutions, Banner, homegrown, etc.) Section - grouping of students enrolled with the registrar, delivered via SIS - lecture, discussion, lab, etc.

5. Why? Needed to support more complex course structures –For integration –Reflected within tools

6. Course Structure Patterns Examples

8. Progress (!) 2.2 –team formation –project definition –user research –requirements gathering –1st round API and service design completed –1st round Hibernate Impl complete

9. Progress 2.3 –UI framework agreed upon (Pinto+) –1st round UI design documents completed 2.3 implementation –Stanford implementing API locally –UCB assembling data sources based on draft schema

10. Next phase: Sub-projects With the Course Management API & Service being implemented and UI framework settled, the CM WG has decided to break down the project into CM-related tool design and development. Goal: Make tools “CM-aware”; able to take advantage of more robust SIS (student info system) data

11. 2.4 Roadmap UC-Berkeley –Section Info –Gradebook –Roster (The Roster tool will be a collaboration with IU.)

12. 2.4 Roadmap Stanford & U of Arizona –Site Info/Worksite set-up - changes to the new course site wizard –Course Browser Tool - admin tool (Duffy Gillman) –Course Homepage Tool new tool

13. Section Info Represent and manage course hierarchies/section memberships Enhanced filtering capabilities Instructor option to toggle between self and SIS-managed sections

16. Gradebook Configurable course grade export Student enrollment and grading status (e.g., Pass/Not Pass). Optionally exposed in UI? (These are the CM-related requirements)

17. Roster Represent course/site hierarchies Filtering capability on Sections/Groups Roster export Display additional member data, e.g., enrollment status

18. Site Info/Worksite set-up (course sites) Show sections in their proper hierarchies for easy selection while: –Creating a new course site –Editing a course site’s sections (rosters)

19. Course Browser Tool (admin tool) Admins/Support staff need to look up Section/Roster IDs in order to edit sites in Sites

20. Course Homepage Tool (new tool) Provide a landing page more suitable for courses Pre-populate with SIS data (e.g. section/meeting info) Allow instructors to include other course information

26. Q & A http://issues.sakaiproject.org/confluence/di splay/CM/Homehttp://issues.sakaiproject.org/confluence/di splay/CM/Home cm-wg@collab.sakaiproject.org