Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Practical Interop For OPDF Developers - Nov 2009

1,141 views

Published on

short presentation for OPDF fund recipients that tries to explain why simply developing within an LMS and exporting is NOT sufficient to provide shareable resources, and some suggestions on better approaches

Published in: Education, Technology
  • Be the first to comment

Practical Interop For OPDF Developers - Nov 2009

  1. 1. Practical Interoperability for OPDF Recipients Scott Leslie, BCcampus November 12, 2009
  2. 2. Overview <ul><li>Why is this important </li></ul><ul><li>Where will your resources be shared </li></ul><ul><li>Some Scenarios </li></ul><ul><li>File format guidelines </li></ul>
  3. 3. Why is this important <ul><li>Part of the goal of OPDF is SHAREABLE content that can be EASILY reused </li></ul><ul><li>Without some forethought, it is easy to develop content that is difficult to reuse </li></ul><ul><li>We don’t want to distract from your initial need, simply avoid making costly choices </li></ul>
  4. 4. Goals of Practical Interoperability <ul><li>Create Flexible Learning Content as EASILY as possible so that it: </li></ul><ul><li>Works in the original environment it will be delivered in </li></ul><ul><li>Works in the other environments we can easily anticipate </li></ul><ul><li>Is shareable in a self-service manner that is easy for re-user to evaluate </li></ul>
  5. 5. Where will the resources be shared? <ul><li>All OPDF resources must be shared in SOL*R ( http://solr.bccampus.ca/ ) as a condition of funding </li></ul><ul><li>SOL*R can handle the following contribution types: </li></ul><ul><li>IMS Content Packages </li></ul><ul><li>Zip files of static web content </li></ul><ul><li>Binary Files </li></ul><ul><li>URLs </li></ul>
  6. 6. Where will shared resources be reused? <ul><li>Resources may be re-purposed ‘as is’, or sampled for select parts. </li></ul><ul><li>Resources may be used in LMS (in BC we have Moodle, WebCT/BB, Desire2Learn,…) </li></ul><ul><li>Resources may be used directly from SOL*R </li></ul><ul><li>Resources may be linked to directly if they reside elsewhere </li></ul>
  7. 7. The Challenge <ul><li>Many of the LMS in play do not EXPORT content in a form that is easily reusable </li></ul><ul><li>The standard for sharing learning content, IMS Content Packaging, does not well capture *an entire course* of content ( E.g. doesn’t capture discussions, assignments, assessments well) </li></ul><ul><li>Many of the ways of creating “learning standards-based” content *outside* of the LMS are cumbersome </li></ul>
  8. 8. The Ideal Shared OPDF-Funded Content Instructor / Instructional Developer Trying to Reuse Content
  9. 9. Scenarios <ul><li>Develop content *inside* delivery environments </li></ul><ul><li>Develop content outside of learning environments using Education-specific standards </li></ul><ul><li>Develop content outside of learning environments using general Web standards </li></ul><ul><li>Develop courses completely out in the open </li></ul><ul><li>??? </li></ul>
  10. 10. Scenario 1 – Moodle
  11. 11. Scenario 1 – WebCT/BB
  12. 12. Scenario 1 – D2L
  13. 13. Scenario 2 - Education-specific standards IMS Content Package HARD TO DO
  14. 14. Scenario 3 - Web-specific standards HTML / Flash / PDF EASIER TO DO
  15. 15. Scenario 4 – Develop out in the Open HTML / Flash / PDF
  16. 16. Which are the preferred scenarios? <ul><li>Ideally, develop content OUTSIDE of the LMS using WEB STANDARDS will provide for the most portable content </li></ul><ul><li>PROBLEM – Content developed outside the LMS often lacks the navigational structure (provided by the LMS) </li></ul><ul><li>SOLUTION – Create a basic “Index” page in HTML that provides this navigation OUTSIDE of the LMS </li></ul><ul><li>BUT...if you are going to assemble the content IN an LMS, we would love to have a FULL EXPORT of the course TOO, in the native export format. </li></ul><ul><li>Of course, content that is FULLY OPEN on the Web largely avoids this problem - people can simply link to it </li></ul><ul><li>(though ideally we would still like a copy of it to host locally) </li></ul>
  17. 17. Suggested File Formats Note on PDFs and Word Docs: PDFs aren’t a particularly web-friendly, data-friendly or re-use friendly format. Unless there is no other choice, efforts should be made to avoid PDF (and other proprietary document formats like Word .doc) in favour of native web pages and document transfer formats like RTF Asset Type Suggestion Images Ideally PNG (though GIF/JPEG still fine) Text and Web Pages HTML 4.01 (but ALL presentation in CSS) Video MPEG4 Rich Media Applications Flash Quizzes and Tests Ideally IMS QTI format, but separate text doc with questions/answer keys also helpful
  18. 18. Getting An Account/Logging In <ul><li>Need validated BCcampus Portal Account to access SOL*R </li></ul><ul><li>Go to </li></ul><ul><li>https://myprofile.bccampus.ca/myProfile.htm?_flowId=access-solr-flow </li></ul><ul><li>(or try http://u.nu/4uct3 for a shorter URL) </li></ul>
  19. 19. Contributing a Resource <ul><li>Your tracking number!!! </li></ul><ul><li>Which license? BC Commons or Creative Commons </li></ul>
  20. 20. License Generator <ul><li>Available at – http://solr.bccampus.ca/bcc/customer/BCcommons/publish/publish.html </li></ul><ul><li>Use EARLY in your project </li></ul><ul><li>Ideally simply embed it in a template </li></ul><ul><li>Displaying the license is for YOUR benefit </li></ul>
  21. 21. THANKS! <ul><li>Questions? Discussion? </li></ul><ul><li>Please don’t hesitate to contact me with additional questions </li></ul><ul><li>Scott Leslie </li></ul><ul><li>[email_address] </li></ul><ul><li>250-415-3490 </li></ul>

×