FORWARD MOOC and OER Development Training Workshop
Training module developers, instructional designers, and platform staff to build FORWARD content: hands-on, in the project’s own Moodle and Dataverse environment
📅 Date: 26–28 October 2026 (10:00 – 13:00 CET)
Introduction
Context
FORWARD strengthens higher education and urban resilience in Palestine and Ukraine through six interconnected training modules, delivered as one integrated MOOC built from reusable Sprints, Micro-Learning Units, and Open Educational Resources (training modules development Plan Sec. 2.4). Work Package 4 (Training Curricula Development) is responsible for building this content; this workshop is where that responsibility becomes practical capacity, not just a written plan.
The workshop sits at a specific point in the WP4 pipeline. Stakeholders’ Workshop 2 (24 September 2026) surfaced and validated case-study evidence and module priorities directly from academic, institutional, and civil-society partners in both countries. This workshop, is a training how turn that evidence and those priorities into actual structured content, entered into Dataverse (general overview), built into Moodle Sprints, and prepared for the review and integration process leading to D4.1.
Two systems already exist to support this work, Dataverse (the case-study repository) and Moodle (the learning platform). But a deployed system and a team that knows how to use it correctly are different things. This workshop closes that gap, directly, through hands-on practice rather than instruction alone.
| Formal Training Target : a 3-day online workshop training 18 local IT and multimedia (graduate) students and staff, 9 from Palestine and 9 from Ukraine, delivered by trainers from IUG, Polimi, and OsloMet, on designing and developing OERs and MOOCs, focusing on both technical tools and creative approaches. |
Objectives
- Build a shared understanding of the FORWARD MOOC Sprint structure across all module developers, so content is consistent regardless of who builds it
- Equip participants to reuse and adapt Open Educational Resources legally, and to use AI responsibly in content development
- Enable participants to enter case-study evidence into Dataverse (general overview ??).
- Build hands-on capacity to construct and publish a working Sprint prototype directly in the live Moodle environment, combining technical tools with creative, design-led approaches to content
- Establish practical, free workflows for EN/AR/UA multilingual delivery, so language support is built in from the start rather than added later
- Strengthen the working link between Dataverse and Moodle, so content remains sustainable, citable, and reusable beyond the project
Training Outcomes
- By the end of the three days, participants will be able to:
- Explain FORWARD’s educational product hierarchy and correctly locate any resource within it
- Write a verifiable learning outcome and populate a MOOC Sprint Template
- Distinguish licensing from access classification when reusing or publishing an OER
- Entering a simple case data into Dataverse
- Build and publish a working Sprint prototype in Moodle, with a linked, citable OER correctly deposited in Dataverse
- Apply the free EN/AR/UA multilingual workflow, tagging, native-speaker review, and caption generation, to their own content
Who Should Attend
- Core trainees: Partner leads, module leads and content/training material authors
- Support staff/students: IT and multimedia staff/students; instructional designers; reviewers and translators; data stewards and repository staff.
Expected output: initial draft case record in Dataverse??, a working prototype FORWARD MOOC Sprint published in Moodle, and a linked, citable OER deposited in Dataverse, ready for review and integration into the FORWARD MOOC Platform.
Workshop Program
Day 1: 26 October 2026
The FORWARD MOOC Model
| Duration | Session | Focus / activities | Target groups | Presenter |
| 10 min | Opening (10:00) | Welcome; aims and flow of the three days | Core trainees | IUG |
| 15 min | Where we stand (10:10) | Evidence behind the MOOC: survey, Workshops 1 and 2, the anchor cases, what it means for sprints, agreed vs open | Core trainees | Oslomet |
| 40 min | How the MOOC is built (10:25) | Modules, sprint = case, case → gaps → units → practical, inside a sprint, minutes per sprint | Core trainees | POLIMI/ Oslomet |
| 20 min | What students do (11:05) | All sprints online; one practical in the whole MOOC (8 h, groups of 5, own context); cross-context pairs | Core trainees | Oslomet |
| 15 min | Break (11:25) | |||
| 20 min | Who does what (11:40) | Development, review, translation audit; roles and workflow; leads, minutes, partner summary, planning files | Core trainees | Oslomet |
| 20 min | Languages and access (12:00) | English master → AI translation → audit; captions, subtitles, right-to-left Arabic, low bandwidth | Core trainees | Oslomet |
| 30 min | Decide the open points (12:20) | Module leads, cross-context pairs, pilot sprints, practical tasks, surplus hours, Open Science split | Core trainees | Oslomet |
| 10 min | Wrap-up (12:50) | Decisions and owners; each group picks its case | Core trainees | IUG |
Day 2: 27 October 2026
From Case to Sprint and Pills
| Duration | Session | Focus / activities | Target groups | Presenter |
| 10 min | Opening and recap (10:00) | Day 1 decisions; today’s path from case to sprint design | All participants | IUG |
| 40 min | From case to storyboard (10:10) | Six steps: case, gaps, outcomes, units, quiz, practical; templates, outcomes, storyboard, workbook, data protection | All participants | IUG |
| 20 min | How a sprint becomes an H5P book (10:50) | Content bank upload, filling the chapters, activity settings, course structure in Moodle | All participants | IUG |
| 15 min | Break (11:10) | |||
| 30 min | Producing a pill (11:25) | Slide template, script in speaker notes, recording, video export, captions and subtitles | All participants | IUG |
| 20 min | AI tools and open licences (11:55) | Where AI helps and its rules; CC BY 4.0, attribution, licence vs access | All participants | IUG |
| 20 min | The repository: FORWARD Dataverse (12:15) | One record per sprint with OER and dataset parts; metadata, DOI, Moodle links | All participants | IUG |
| 10 min | Tasks for Day 3 (12:35) | Storyboard (overview and one unit), pill script, questions; about 4-minute presentation | All participants | IUG |
| 10 min | Wrap-up (12:50) | Each group checks it is ready for Day 3 | All participants | IUG |
Day 3: 28 October 2026
Build, Translate, Share
| Duration | Session | Focus / activities | Target groups | Presenter |
| 10 min | Opening and plan (10:00) | Build → translate → review → publish; outputs and support | All participants | IUG |
| 20 min | Groups present (10:10) | About 4 minutes per group: case, outcome, units, one pill, practical briefing | All participants | Group representatives |
| 90 min | Build in Moodle, hands-on (10:30) | Six build steps from upload to student preview | All participants | All five teams |
| 10 min | Break (11:30) | |||
| 20 min | Review and quality check (12:05) | The reviewers (POLIMI and NMBU) present who reviews what, the review process from submission to sign-off and freezing of the English master, and the quality checks applied to every sprint: learning design, content, online time, assessment and practical, pills, data and ethics, accessibility and licences, H5P in Moodle. Live review of one draft sprint. | All participants | POLIMI/NMBU |
| 30 min | Translate (11:40) | AI translation of transcript and chapter, audit, subtitle files, right-to-left check | All participants | All five teams + translation auditors |
| 30 min | Publish and link (12:25) | Dataverse record, CC BY 4.0, DOI, link to Moodle | All participants | All five teams |
| 10 min | Next steps and close (12:45) | Status of the draft sprints, pilot timeline, support, evaluation | All participants | IUG |
