MoodleNet/mootieuk19-workshop

Jump to: navigation, search

<< Back to MoodleNet index


Overview

At the 2019 MoodleMoot UK & Ireland, Doug Belshaw gave a presentation and ran a workshop for attendees on MoodleNet's past, present and future. Participants had an opportunity to discuss what they like about the MoodleNet vision, and what they'd like to see included in the future roadmap.

mootieuk19-course-design.jpeg
mootieuk19-course-design-2.jpeg
mootieuk19-institutional.jpeg
mootieuk19-learning-and-teaching.jpeg
mootieuk19-technology.jpeg
mootieuk19-technology-2.jpeg
mootieuk19-UX.jpeg

Slides

Workshop

The 1.5 hour session on Day 3 of the Moot was structured in the following way:

  • Welcome, intro and overview
  • Affinity grouping
  • Hands-on testing of MoodleNet
  • Discussion around key questions
  • Feedback and next steps
  • CLOSE

During the Affinity grouping activity, and before participants had a chance to register for MoodleNet, they were asked what problems they envisaged MoodleNet solving for them. During testing, they were asked to do the following:

  1. Go to https://app.moodle.net
  2. Complete basic profile
  3. Join a community
  4. Add a comment in a community
  5. Add a resource to a collection
  6. Create a new collection
  7. Optional: create a new community

After testing, participants discussed the following questions:

  • What do you like about MoodleNet?
  • What questions do you have?
  • What concerns do you have?
  • How would you like the integration with Moodle Core to work?
  • What's the next thing we should add to MoodleNet? (think big!)

Course design group

Pre-testing discussion

  • Sharing good examples of course design
  • Central repository of key resources
  • Examples of good/diverse practice
  • Also sharing experiences of things that went well/didn't go well, pitfalls to avoid
  • Tagging/context aware
  • Ratings/reviews
  • Comments/running dialog beneath each resource

Post-test discussion

  • Likes:
    • Idea of communities
    • Quite visual presentation
    • Accidental discover of resources: "didn't know I wanted that"
    • Easy to see who is community
    • Interface
    • Usability
    • Harvests description of resource + thumbnail, etc.
    • Gravatar
  • Questions:
    • How communities ordered/can be ordered?
    • How can you connect with other users?
    • Why 10 limit?
    • How to get stuff into Moodle?
    • Upload activities?? (no file upload)
    • Integration with existing repositories - oai-pmh protocol?
    • Competes with similar projects - needs to build on them
  • Concerns:
    • Risk of duplicating communities accidentally
    • User impact if plugin UI in Moodle Core is bad
    • Assumes good behaviour + intentions from users
    • Overlapping/competing communities
    • No moderation of communities or resources (risky content)
    • No flagging of poor/risky content (fake news!)
    • Communities can be edited by others - risky
  • Wants & needs
    • Ranking / rating system
    • Comments
    • File uploads (e.g. images)
    • Flagging duplicate content?
    • View 'followed' by default (not 'all')
    • Share communities, invite users
    • Embed videos + preview
    • Upload resource - "did you know this resource is already linked...?"
    • Create a community - asks "did you know there is already communities with similar names...?"
    • Groups of communities
    • Tags for content + communities
    • Example use cases
    • More metadata fields for resources in general
    • Follow tags & feed
    • Uploading files - file/link checker
    • Save/like resources

This group gave the example of xtlearn.net as addressing similar challenge.

Institutional MoodleNet group

Pre-test discussion

  • Re-use content
    • Colleagues (in dept)
    • Students
    • External partners
    • Fellow professionals (e.g. 'physics teachers')
  • QA
    • Monitor quality
    • Improve quality
  • Change mindsets
    • Create sharing ethos (i.e. 'community')

Post-test discussion

  • Likes:
    • Easy interface with Moodle (we hope!)
    • Simple design/UX
  • Questions:
    • Could there be another level above community? (dept/institution)
    • Is there going to be (hierarchical) tagging?
    • Will communities be able to be closed/private?
  • Concern:
    • That will become an 'unstructured morass of stuff'

Learning and Teaching group

Pre-test discussion

  • Sharing good practice
  • Sharing good content (images/texts)
  • Incentivise sharing
    • Reward and recognition
  • Trust, evaluation, quality review
    • 'Paradata'. Review cycle - 'merlot'
  • 'Pedr'. Pedagogic research.
  • Community - not anonymised
    • Feedback; experience
    • Mixed media
    • Notification
    • Multi-lingual

Post-test discussion

  • Ownership of communities - not secure
  • Communities not moderated - duplication risk, security risk

Technology group

Pre-test discussion

  • Sharing resources
  • Bridging the gap between technology and pedagogy
  • 24/7/365 MoodleMoot online :)
  • Instructors more informed about student interests
  • Connecting local groups internationally

Post-test discussion

  • Requests:
    • Export/import directly to Moodle (courses)
    • Request/invite people
    • Pinterest pinning
  • Questions:
    • Would you have a community available across MoodleNet instances (e.g. collaboration between universities)
    • Could we 'pin' a Moodle 'thing' and the source server and then post an MBZ of the thing to MoodleNet? 'Out of brand' / asynchronously?
    • Discussion threads or channels?
  • Concerns:
    • Bug: all bold text should be linked (resource isn't). Could the link go to the collection, to see the context, with the resource should be focused on. (MDLNET-278)
    • Bug: in dark mode community user list presents with half shaded text which highlights at full black colour

UX group

Pre-test discussion

  • UX is the gateway - we ant sharing to happen, need to smooth all blockers and invite/encourage it.
  • Parallel? Moodle Plugins DB. Need quick to evaluate image and description.
    • Also download stats and reviews
  • Skills to create not necessarily skills to curate (hence communities)

Post-test discussion

  • Needs automated testing of the code so it is not glitchy
  • Short comments + rating of resources
  • Types of resource
  • Prompt to user/share/add to (?)
  • Share + suggest invite to community
  • How to integrate? Add to course? If logged in courses available?
  • Learning resources ratings (social proof)