{"id":17695,"date":"2022-07-19T01:12:34","date_gmt":"2022-07-19T05:12:34","guid":{"rendered":"https:\/\/pacificopencourses.col.org\/edt4ol\/?page_id=17695"},"modified":"2022-07-19T01:12:34","modified_gmt":"2022-07-19T05:12:34","slug":"oer-reuse-and-remix","status":"publish","type":"page","link":"https:\/\/pacificopencourses.col.org\/edt4ol\/acceptance-portfolio\/oer-reuse-and-remix\/","title":{"rendered":"OER reuse and remix"},"content":{"rendered":"
\n
\n
\n
\n
\n
\n
\n
\"Open<\/a><\/div>\n


<\/p>\n

In this course, we will use wiki technology for collaborative authoring of OER. Here, we provide a brief explanation highlighting the benefits of this approach. Our approach is distinctively open and encourages open design and peer collaboration models to maximise reuse and remix.\n<\/p>\n

Learning Management Systems (LMSs) like Blackboard<\/a>, Canvas<\/a>, Desire2Learn<\/a>, Moodle<\/a> and Sakai<\/a> are widely used by institutions of higher education as their preferred technologies for e-learning. Some institutions use blogs and other website technologies for publishing and hosting online learning materials.\n<\/p>\n

While many of these software tools support inter-operability specifications and standards for importing<\/i> content into their respective systems, including, for example, the IMS Learning Tools Interoperability<\/a> (LTI), IMS Common Cartridge<\/a> and SCORM<\/a>, exporting<\/i> content from these learning management systems for reuse across different delivery technologies is not universally supported. Moreover, these LMS tools were not primarily designed for collaborative authoring and reuse on scale.\n<\/p>\n

Practical challenges<\/span><\/h2>\n

In the OER world, implementing a peer collaboration model for OER design and development for reuse across multiple delivery platforms poses a number of practical challenges:\n<\/p>\n

    \n
  1. How do we provide a ‘single source’ of content which can be easily integrated into a wide range of delivery technologies?<\/i>\n<\/li>\n
  2. How do we manage version control in an open collaborative development environment?<\/i>\n<\/li>\n
  3. How do we design for scalability for large numbers of prospective learners?<\/i>\n<\/li>\n<\/ol>\n

    The wiki OER authoring solution<\/span><\/h2>\n
    \"OERu-logo-acronym.png\"<\/a><\/div>\n

    In a global collaboration like the OERu<\/a>, it is unlikely that all partners would agree to use the same Learning Management System. In addition, if we were to use a Learning Management System for collaborative authoring, if one teacher, for example, were to make a change to the course materials, it would not be easy for the other members of the team to monitor and manage the detail of these changes. Similarly, remixing the sequence of the content or substituting assessments for different international contexts would not be easy to implement within a shared Learning Management System. Scalability for large student cohorts is also a major challenge. For instance, if a facilitator were to host a webinar and request a course cohort of thousands of learners to click simultaneously on a particular discussion forum post, the server infrastructure may not be able to deal with the amount of online traffic. One possible solution is to distribute the computing resources required for interactions across the internet, and this is the technology approach adopted for this online course development ecosystem.<\/p>\n

    \"Bangalore<\/a><\/div>\n

    Revision control<\/a> software used by software developers, for example, GitLab<\/a> or GitHub<\/a>, would provide the functionality needed for version control. However, many educators do not have the technical skills to use revision control software.\n<\/p>\n

    In this course we use wiki technology because:\n<\/p>\n