DScribe Process Refinement Session: 12/04/2009

DScribe Process Refinement Session: 12/04/2009

Collaborative note-taking
We'll be using our ether pad from last session http://etherpad.com/jfTKsmTZbh

Action Items from Last Session

 * 1) Write out service scenarios: DScribe Scenarios
 * 2) Revisit tasks/skills/roles table: see bottom of DScribe Scenarios
 * 3) Identify tools for supporting

goal of meeting

 * to have a complete new version of dScribe for fall 2010. Today we would like to identify several projects to target for next semester. Next semester: Will do a small pilot of refined process with identified projects next semester. may recruit new people as necessary, i.e. not just rely in dScribe alums or OER star faculty. could also put small effort in developing new tools for next semester, but this would be the huge OERca2 development.

tasks involved in OER production

 * advocacy/promoting
 * identify potential OER
 * training and OER creation
 * gather material
 * obtain permission
 * extract and tag
 * find replacement content (open content)
 * edit
 * review and feedback
 * spot check, audit
 * convert (e.g. file formats)
 * instructional design/architecture (e.g., Lada’s course)
 * faculty approval
 * promote
 * publish (could provide broad access to /stage-education)
 * update, maintain (refresh, new files, etc.), retire (the entire process repeats itself)
 * research on porcess, policy. learning outcomes
 * add learning objectives to materials
 * content evaluation - course specific, site-wide

possible projects - dScribe

 * 1) find GROCS project and make it open
 * 2) find and stduent project and make it open
 * 3) find few alumni and make them dScribes with certification
 * 4) train interested staff in copyright and OER prod (admin asst, student serv, instruct. design, Scott B) - priority
 * 5) train interested staff in evangelism (cheerleader, auditor)
 * 6) try to clear course/module w/ dScribe-lite process (very simplified - no unlicensed 3rd party content)
 * 7) apply student to backlogged materials
 * 8) audit 4 departments to see how difficult it is to make open (use CTools data to find)
 * 9) audit 4 courses in diff dept for difficulty
 * 10) find 5 projects we can help make open
 * 11) investigate students, faculty, staff to collect syllab
 * 12) start a dScribe student group, be the catalysts (free culture, radical learning) - priority
 * 13) make existing student notes project open
 * 14) host student open notes contest

possible projects - dScribe or open.michigan staff

 * 1) approach LSA course guide and add CC license
 * 2) start speaker series on openness
 * 3) make next year's OA week a BIG deal
 * 4) host 2nd open everything

possible projects - open.michigan staff only

 * 1) provide resources/help to new open textbook project at SPO
 * 2) provide faculty workshop on open ed (include OER component, could be hands-on where people come with materials, could be strategies for making course open such as wiki)
 * 3) host student lecture remix project
 * 4) work with library to archive OER
 * 5) archive course information from MCommunity (wolverine acces, CTools) (Laura Patterson)

goal for fall 2010
"vibrant set of nodes is an open network of open activities at U-M" (too broad?)

dScribe definition, tensions

 * underlying principle: - do not want to dilute dScribe brand
 * open michigan vs. dScribe
 * open culture vs content
 * U-M community needs vs. how dScribe product presented outside the university (e.g. health OER project w/ Hewlett)
 * not recreating slogan (we already have this on T-Shirts, stickers) but coming up with one sentence explanation
 * tagline open > share> learn. evolve
 * existing business card: "dScribes are students who transform learning materials into OER. Each semester, dScribes assist faculty, researchers, and classmates in the process of opening access to educational resources for use by instructors."


 * dScribes - building the open culture
 * dScribes are people who make things opens. things could be people, content, education
 * dScribes need to faciltate openness
 * dScribes already exist we just don't call them that and they don't identify by that name
 * students should not be drones, "staff should be drones"
 * what's the least common denominator?

random important notes

 * N.B. Std Practice says U-M owns syllabus, faculty owns other content
 * even a student or professor starts an open project and doesn't finish it, we shouldn't consider that it's not a success. changing mindset and awareness of open is MORE than a small win and means they are more likely to create their own open content in the future or teach other people how to do so.

follow-up actions before next meeting

 * separate out dScribe only projects (done)
 * schedule next meeting for Wednesday Dec 9 from 1 - 3 pm (done)
 * before next meeting: vote on dScribe only projects for project - criteria is 1) what will have greatest impact to put us in a position for fall 2010, 2) low-hanging fruit (easiest content to clear, level of interest of content creators)