OER Life Cycle: From Authoring to Publishing / July 2009 / OER Hands-On Production Except where otherwise noted, this work is available under a Creative.

OER Life Cycle: From Authoring to Publishing

/ July 2009

/ OER Hands-On Production

Except where otherwise noted, this work is available under a Creative Commons Attribution 3.0 License. Copyright © 2009 The Regents of the University of Michigan

Kathleen Ludewig

Adapted from earlier presentations by Pieter Kleymeer and Garin Fons

The OER life cycle.

Authoring

Clearing

Editing

Archiving

Publishing

post production clearing...

Authoring

Clearing

Editing

Archiving

With post-production clearing, the system gets clogged up and becomes less efficient

Publishing

Pre-production clearing - stages

Authoring + Clearing

use content created locally (from KNUST)

choose 3rd party content from open sources that give explicit open licenses (or content that is in the public domain)

document all 3rd party content with pertinent source information

Editing

display a clear notice of how others may use your work (e.g. CC license)

edit the resource to include 3rd party licenses and source citations

Pre-production clearing - stages.

6

Checklist for published resources

All published resources must have:1.A Creative Commons license2.The name of the Copyright Holder3.The name of author(s) 4.Institutional Branding5.General contact person6.Acknowledgements of those who contributed (funders, collaborators)7.Proper citation for third-party objects8.Necessary disclaimers (see next slide)

7

Disclaimers

There are 4 Disclaimers that a material may have. The first one is required for all. The rest are only included if relevant. They are contained in the OER HTML templates.

1. Medical images and general liability2. Medical patients 3. Third-party content4. Student actors

Questions for discussion

:: Considering access and connectivity constraints, what file formats, file sizes, etc. are best?

:: Is there a quality assurance process after an OER module is finished to ensure that a material is reviewed for policy issues (e.g. dScribe)? Is the module also peer-reviewed for content?

:: Once an OER module is finished and reviewed, where is it stored? Who uploads it to the server? What is the process for updating materials?