Lessons Learned

From openmichigan

Jump to: navigation, search


Lessons Learned


[edit] OER

  • We need faculty buy-in and license from the beginning of the process
  • prospective clearing (i.e. using open content from the start) is much more efficient and sustainable
  • open content created from the start by faculty may still have copyright, privacy, or endorsement concerns and require an audit before publication on Open.Michigan

[edit] dScribe

  • we can teach the basics of dScribe in an hour an hour and a half
  • it's difficult to get most students to put in time beyond the dScribe sessions
  • it's helpful to have bi-weekly sessions to create a culture around open and an understanding of why open matters
  • the roles-based approach to dScribe may work in crowd-sourcing tasks, but it requires great mediation via software
  • you can carry out the dScribe process with a simple spreadsheet, PowerPoint template, and a basic method for sharing files (e.g. email, shared file directories)
  • some courses and modules are too content intensive to be completed by volunteers
  • most courses will be published 3 - 9 months after the course ends
  • students can carry out the dScribe process without much interaction with the faculty member
  • few volunteers will take the time to add keywords to individual content objects
  • many volunteers do not feel confident in approaching faculty about why they should share their materials

[edit] software

  • it's difficult to design software for a process that's still changing
  • since the clearing process may be different at each institution, software should be modular

Print on Demand Book Services

Personal tools