1

Sakai and eduCommons OCWInteroperability – Progress Report

Joseph HardinZhen Quan

Jim EngCarl Collins

2

Look at OCW Site

3

Sakai Resources Area – unorganized vis a vis OCW

4

Overall Goals

•Make Sakai an Open Educational Resources engine; a generator of OERs as OpenCourseWare sites

•Make the process of OCW site generation economically feasible

•Make it simple for faculty to tag and export their class materials to an OCW site

•Couple Sakai and eduCommons (OCW site creation tool) to automate the process

5

Sakai

UMOCW

Web Siteor

other InstitutionalRepository

Publication PipelineDigital Course Materials:(1) IP Management (2) Tagging OCW Categories(3) Exporting from CTools(4) QA and Review

eduCommons tools

RawCourseContent

VettedOCW

Content

Teaching

Research

Putting an OCW Pipeline in the LMS -OCW Publishing from Sakai

Initial MIT OCW process has difficulty scaling.How can we support this process?

6

Current Problems

•Too expensive to create OCW sites

•Little or no automation

•No connection to CLE (eg, Sakai)

•Only large institutional commitment can get an OCW site off the ground

•Roadblock to growing the OCW community

7

Overview of ProcessBased on Hybrid Publishing Model

Integrated with MIT Teaching Process

Plan Build Teach/Manage Publish

Upstream foundational prep

• Recruit faculty• Plan TEACHING version of

course• Plan OCW version of course• Review existing content• Identify & resolve IP (except

permissions)• Track IP by object in system

Content development

• Collect/capture existing content

• Build content into LMS sections/templates

• Enter metadata• Create commissioned works• Process permission requests

& make IP edits

Live teaching and course administration

• Update/supplement materials

• Post announcements• Assign, track, grade

student work• Interact (faculty-student

and student-student)

Open publication

• Perform course QA• Obtain faculty approval• Export to OCW site

Support

Renewal, archiving, and preservation

• Update course content• Archive course content

Color legendBLACK Normal teaching processBLUE Required for open publishingORANGE Former OCW steps eliminated

HY

BR

ID I

NT

EG

RA

TE

D

PR

OC

ES

SA

RC

HIT

EC

TU

RE

O

VE

RV

IEW

• Spec course/map content • Reformat/clean up/ restructure/contextualize

• Enter content into CMS• Perform authoring QA

• Perform final edit• Perform production QA

• Respond to user feedback• Review/refine metadata

(MIT Library)• Edit course for errors

EL

IMIN

AT

ED

S

TE

PS

ExternalOCW

AudiencesMIT Faculty & Teaching Assistants

Individual Teaching Web Sites

MIT-Supported LMS

OCW External Web

Site

Dspace Archive

MIT-supported option

Assume 80% participation

Publish

- O

R -

Individual/local supported option

Assume 20% participation

• Robust authoring– Easy capture– Easy update

• Document managemt– Restricted teaching matls– Open teaching matls

• Import/export– Offline authoring– Self-publishing

• Multiple views• Course admin

Teach MITStudents

• Publishing tools– Embedded tracking code– Embedded license terms– IP tracking– Metadata tagging– Hi-design display templates– Preview capability– Downloadable ZIP files– Discussion group suppt– Archiving

• Workflow

Archive

Harvest for archi ving or publishing

8

Plan Build Teach/Manage Publish

Upstream foundational prep•Recruit faculty•Plan TEACHING version of course

•Plan OCW version of course•Review existing content•Identify & resolve IP (except permissions)

•Track IP by object in system

Content development

•Collect existing content•Build content into LMS sections or templates

•Enter metadata•Create commissioned works•Process permission requests & make IP edits

Live teaching and course administration

•Update and supplement materials•Post to email, wikis, blogs, announcements, discussions, forums, IM

•Assign, track, grade student work•Interact (faculty-student and student-student) through all channels above

Open publication

•Perform course Quality Assurance

•Obtain faculty approval

•Export to OCW site

BLACK Normal teaching process

BLUE Required for open publishing

A closer look at MIT’s hybrid model

9

OCW Tool + eduCommons

•Perform course Quality Assurance

•Obtain faculty approval•Export to OCW site

Publish

QA done within eduCommons by staff – local or central

Faculty receives an email with the URL of the QA’d OCW site,

decides whether or not to authorize publishing

If NO, faculty given available support – local or central –

supported through eduCommons workflow

If YES, OCW site is published through eduCommons

Open publication

This work is very much in progress, thanks to support from Hewlett

Foundation, and ongoing efforts from Utah State University and the University of

Michigan

10

So, let’s build an OCW Tool in Sakai

11

OCW Site Structure

1) Site Main Page

2) Department Page

3) Course Home Page

12

MIT OCW Site Page

13

“Department” Page

14

OCW Course Homepage

15

Utah State OCW Site – eduCommons generated

16

Utah State OCW Department Page

17

Course level page

18

The current main page for the OCW tool;from here one can:

create a course home pageselect materials from the sakai resources tool & set copyright

edit the list of MIT OCW categories (MOCs)preview our OCW choices

export to IMS-CP zip format

19

Closer look…

20

Creating the course home page

21

Selecting what resources to include for export,

tagging them with the appropriate MOC (Readings, Lecture Notes, etc.) and

assigning copyright

22

Here we can add metadata to the MOCs, remove them from the list, and eventually create user defined tags.

This allows the user to choose their own site navigation structures.

23

Previewing the choices we made in the previous sections

24

The final step within Sakai currently, exporting to IMS-CP zip file, which is then imported into the

eduCommons tool.

25

Working with your package in

26

Start by logging inthe site is publicly viewable

but you need to login to import

27

Select a department (created by admin staff ) from the left hand navigation;

need a department to import content into.

28

Select a course from the list, or create one using theadd item drop-down on the right hand

side of the administrative interface

29

Once at the course level, click contents and then import from the choices below the content list

30

Import the IMS-CP zip

31

Navigate to the imported files, click on one to see a detailed view

32

Review the file and its metadata.Identify if it should be shown in the left hand navigation.

Edit the associated html using the FCK editor.

33

Once files have been reviewed, copyright can be finally cleared and they can be moved through the QA process,

by using change state.

Once at PUB: the site is publicly viewable – we have the OCW site!

34

What does the Sakai OCW tool currently do?

• Selection of Course Home Page materials• Selection of Course Materials for export• Selection of content grouping based on MIT OCW categories (MOC) for: Sakai Resources Tool• Selection of Licenses for Course Materials• Review of Selected content• Export of selected materials into IMS-CP zip

Tasks handled by Sakai+ Import of IMS-CP zip

Import to eduCommons

• Review of imported content• Assigning of left hand navigation to imported content• Assigning of copyright toimported content• QA review of imported content• Hand off to instructor for final review• Publish site

Tasks handled by eduCommons “QA agent”

35

What is planned for the Sakai OCW tool andinteroperability with eduCommons

•Selection of Course Home Page materials•Selection of Course Materials for export and free tagging of content grouping titles for: Sakai Resources Tool Sakai Syllabus Tool Melete - Modules Tool•Selection of Licenses for Course Materials•Review of Selected content•Export of selected materials into IMS-CP zip

Tasks handled in Sakai

•Import of IMS-CP•Parsing of IMS-CP manifest•Assignment of content to left hand navigation and page template for course home page•Recognition and assignment of creative commons licenses to imported content

Tasks automated in eduCommons

Tasks handled by eduCommons QA agent

•QA review of imported content•Hand off to instructor for final review•Publish

36

Tech Demo - Where the the OCW tool is now

37

Questions, Comments

For more info:

http://sakaiproject.orghttp://cosl.usu.edu/projects/educommons/

Sakai/eduCommons/OCW Project

Zhen Qian zqian@umich.edu

John Dehlin johndehlin@gmail.com

Joseph Hardin hardin@umich.edu

Carl Collins carlrc@umich.edu

Questions, DiscussionStay Tuned