Last week was MoodleMoot UK & Ireland 2019. At the previous year’s MoodleMoot, our presentation on MoodleNet contained only ideas of what we would build. This year, we had an alpha version to put in front of people at a workshop.
The focus of the session was on past, present, and future, with participants having an opportunity to discuss what they like about the MoodleNet vision, and what they’d like to see included in the future roadmap.
The 1.5 hour session on Day 3 of the Moot was structured in the following way:
Welcome, intro and overview
Hands-on testing of MoodleNet
Discussion around key questions
Feedback and next steps
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. The emergent groups were around:
Online course design
Learning and teaching
During testing, participants were asked to register, complete a basic profile, and join a community to add resources and comments.
After testing, participants discussed a series of questions which are included with full details of the workshop on this wiki page. Over and above the things on our roadmap, the main things we learned (or found interesting) were:
Confusion between ‘communities’ and ‘collections’
Flagging duplicate content
Per-community hierarchical tags
Grouping of several communities
Reward and recognition for users
It was a very useful session, and the 1.5 hours went by very quickly. We’d like to thank participants, and your rare badge will be on its way soon!
MoodleNet is a new open social media platform for educators, focussed on professional development and open content. It is an integral part of the Moodle ecosystem and the wider landscape of Open Educational Resources (OERs). The purpose of this post is to explain how our approach to search will help with this.
Our research shows that educators discover resources in two key ways, which we’re bringing together with MoodleNet.
In order to be proactive and search for something specific, you have to know what you are looking for. That’s why it’s common for educators to also be reactive, discovering resources and other useful information as a result of their social and professional networks.
From its inception, we’ve designed MoodleNet as a place that works like the web. In other words, it harnesses the collective power of networks while at the same time allowing the intimacy of human relationships. However, search tends to be a transactional experience. How do we make it more ‘social’?
At this point, let’s re-introduce Seung, the 26 year-old Learning Technologist from Australia who we first met in a white paper from early 2018. She’s looking to help her colleagues use Moodle more effectively, and to connect with other Learning Technologists to discover promising practices.
Seung comes across many potentially-useful resources on her travels around the web, which she curates using services such as Pocket, Evernote, and the ‘favourite/like’ functionality on social networks such as Twitter and Facebook. When Seung uses MoodleNet, she joins relevant communities, follows interesting collections and people, and ‘likes’ resources that either she or her colleagues could use.
One of the problems Seung has is re-discovering resources that she’s previously found. Although she considers herself an advanced user of search engines such as Google and DuckDuckGo, Seung is sometimes frustrated that it can take a while to unearth a resource that she had meant to come back to later.
MoodleNet’s powerful search functionality will allow Seung to both find interesting communities, collections, and profiles, and quickly rediscover resources on MoodleNet that she has marked as potentially-useful. In addition, because MoodleNet is focused on open content, Seung can extend her search to OER repositories and the open web.
The same search functionality will be available through a Moodle Core plugin that allows any user, whether or not they have an account on MoodleNet, to search for resources they would like to pull into their Moodle course. This plugin will also automatically add metadata about the original source location, the MoodleNet collection of which it was part, as well as any licensing information.
We’ve already started conversations with Europeana and Creative Commons about allowing MoodleNet users to directly search the resources they both index. We would also like to explore relationships with other OER repositories who would welcome MoodleNet communities curating and using their openly-licensed resources.
In closing, we should mention that we have big plans for tags across MoodleNet, involving both taxonomic and folksonomic tagging, and provided by both users and machine learning. More details on that soon.
For now, the MoodleNet team would be interested in any questions or suggestions you have about this approach to search. What do you think? What else would you like to see?
On Tuesday, the European Parliament gave final approval to the Copyright Directive, a controversial piece of legislation affecting online services that either link to news articles or allow uploads.
During the process of this legislation coming into law, the MoodleNet team has been asked about the potential impact on what we are building. Developments are ongoing even now and the Directive has to passed into law by the European member states.
As a result, we have decided to keep a wiki page up-to-date about what the Copyright Directive may mean for MoodleNet. You can access this on the Moodle wiki.
A couple of days ago the team deployed MoodleNet v0.7 alpha, which includes the following new functionality, UI tweaks, and bug fixes.
User profile pages
New discussions view
Improved login page
Fixed ‘a few seconds ago’ bug
Various small bug fixes
Note that the timeline views aren’t exactly as we want them, so we’re tweaking them over the next week or so.
In addition, we’re working on our Data Protection Impact Assessment (DPIA) with Moodle’s Privacy Officer and external Data Protection Officer (DPO). That will be finalised before we launch the first beta next month.
We’re currently working on:
Federation — the ability to have separate instances of MoodleNet that can communicate with one another.
Moodle Core integration — add a resource from MoodleNet to a course in a Moodle course.
Refactoring and code clean-up — ensuring MoodleNet runs as quickly, efficiently, and bug-free as possible!
The next release, v0.9 alpha, is scheduled for week beginning 8th April 2019.
We’ve recently finished testing MoodleNet’s value proposition with two cohorts of users, in both English and Spanish. During each three-week testing period, we sent one survey per week. In this post, we’d like to share some of the insights we’ve gleaned.
It’s important to note the following:
We built the smallest possible version of MoodleNet in an attempt to answer the question, “Do educators want to join communities to curate collections of resources?”
During the testing process, we didn’t discuss future functionality in the user interface or in the emails we sent users. We did, however, discuss the roadmap in a tool called Changemap which we’re using to collect and discuss feedback and feature requests.
One of the key features of MoodleNet will be federation (i.e. the ability to have separate instances of MoodleNet that can communicate with one another). This will change the user experience and utility of MoodleNet in significant ways.
The survey data we’ve collected suggests that MoodleNet is indeed something that can sustainably empower communities of educators to share and learn from each other to improve the quality of education.
What follows are three things that we’ve learned from the testing process.
1. We’ve validated the value proposition
A couple of days after giving each cohort of testers access to MoodleNet, we asked them, “Do you see yourself using something like MoodleNet to curate collections of resources?”. The functionality, especially during that first week for the initial cohort was extremely basic, and the experience sometimes buggy.
Despite this, by the time the second cohort filled in their first survey, it was clear that almost two-thirds of testers agreed that, yes, MoodleNet would be something that they would use.
2. The best tagline for MoodleNet: ‘Share. Curate. Discuss’
During the testing period we learned that creating taglines that are translatable and impactful in different languages is no easy feat. In fact, many companies and brands simply use English taglines, such as Nike’s ‘Just Do It’. We’ve decided to go ahead and use ‘Share. Curate. Discuss’ for the moment as the tagline for MoodleNet (including on the Spanish version of MoodleNet).
3. Testers are clear on what they want to see next
Through free text boxes in surveys, and from the information coming in via Changemap, it’s clear that users want to be able to:
Search for specific keywords and topics of interest.
Easily find out when something has changed within a community they’ve joined, or a collection they’re following.
Sort lists of communities and collections by more than ‘most recent’ (e.g. by number of collections or discussion threads)
Tag communities, collections, and profiles, to make it easier to find related content.
Upload resources to MoodleNet instead of just adding via URL.
Indicate ‘resource type’ (e.g. ‘course’, ‘presentation’ or ‘plugin’)
Send resources they discover on MoodleNet to their Moodle Core instance
Add copyright information to resources and collections
Easily rediscover useful resources they’ve discovered in collections they’re not following
Access MoodleNet on their mobile devices
Happily, we’ve already got MoodleNet working on mobile devices, although we’re still having some issues with Safari on both iOS and MacOS. We’re also launching ‘timeline views’ for communities and collections this week which will allow users to see what’s changed since they’ve been away.
When developing software products, it’s easy to come up with a plan and start working on it without validating what you’re doing with users. We’ve still got a way to go before MoodleNet is exactly what community participants want from it, but we feel that in this initial testing period we’ve got a mandate to keep on iterating.
A big thank you to our two cohorts of testers, who have provided invaluable feedback. They still have access to MoodleNet beyond the testing period. We’ll be inviting more people to join at next month’s UK & Ireland MoodleMoot in Manchester, so why not join us there?
I’m MoodleNet Lead and, since the project’s inception, I’ve had lots of conversations with many different people. Once they’ve grasped that MoodleNet is a federated resource-centric social network for educators, some of them ask a variation of this question: Oh, I assume you’ll be using a star rating system to ensure quality content?
They are often surprised when I explain that no, that’s not the plan at all. I haven’t written down why I’m opposed to star rating systems for educational content, so what follows should hopefully serve as a reference I can point people towards next time the issue crops up!
However, this is not meant as my last word on the subject, but rather a conversation-starter. What do you think about the approach I outline below?
Wikipedia defines a rating system as “any kind of rating applied to a certain application domain”. Examples include:
Motion Picture Association of America (MPAA) film rating system
Rating system of the Royal Navy
A rating system therefore explains how relevant something is in a particular context.
Ratings in context
Let’s take the example of film ratings. Thanks to the MPAA film rating system, parents can decide whether to allow their child to watch a particular film. Standardised criteria (e.g. drugs / sex / violence) are applied to a film which is then given a rating such as G (General Audiences), PG (Parental Guidance), and R (Restricted). These ratings are reviewed on a regular basis, sometimes leading to the introduction of new categories (e.g. PG-13).
Despite the MPAA film rating system, many parents seek additional guidance in this area – for example, websites such as Common Sense Media which further contextualise the film.
In other words, the MPAA rating system isn’t enough. Parents also take into account what their child is like, what other parents do, and the recommendations of sites they trust such as Common Sense Media.
Three types of rating systems
As evident in the screenshot above, Common Sense Media includes many data points to help parents make a judgement as to whether they will allow their child to watch a film.
With MoodleNet, we want to help educators find high-quality, relevant resources for use in their particular context. Solving this problem is a subset of the perennial problem around the conservation of attention.
In other words, we want to provide the shortest path to the best resources. Using an adapted project management triangle, educators usually have to make do with two of the three of time, effort, and quality. That is to say they can minimise the time and cost of looking for resources, but this is likely to have a hit on the relevance of resources they discover (which is a proxy for quality).
Likewise, if educators want to minimise the time and maximise the quality of resources, that will cost them more. Finally, if they want to minimise the cost and maximise the quality, they will have to spend a lot more time finding resources.
The ‘holy grail’ would be a system that minimises time and cost at the same time as delivering quality education resources. With MoodleNet, we are attempting to do that in part by providing a system that is part searchable resource repository, and part discovery-based social network.
Simply providing a place for educators to search and discover resources is not enough, however. We need something more granular than a mashup of a search engine and status updates.
What kinds of rating systems are used on the web?
There are many kinds of rating systems used on the web, from informal approaches using emoji, through to formal approaches using very strict rubrics. What we need with MoodleNet is something that allows for some flexibility, an approach that assumes some context.
With that in mind, let’s consider three different kinds of rating systems:
Star rating systems
Best answer systems
1. Star rating systems
One of the indicators in the previous example of the Common Sense Media website is a five-star rating system. This is a commonly-used approach, with perhaps the best-known example being Amazon product reviews. Here is an example:
Should I buy this laptop? I have the opinion of 12 customers, with a rating of three-and-a-half stars out of five, but I’m not sure. Let’s look at the reviews. Here’s the top one, marked as ‘helpful’ by nine people:
So this reviewer left a one-star review after being sent a faulty unit by a third-party seller. That, of course, is a statement about the seller, not the product.
Averaging the rating of these two reviews obviously does not make sense, as they are not rating the same thing. The first reviewer is using the star rating system to complain, and the second reviewer seems to like the product, but we have no context. Is this their first ever laptop? What are they using it for?
Star rating systems are problematic as they are blunt instruments that attempt to boil down many different factors to a single, objective ‘rating’. They are also too easily gamed through methods such as ‘astroturfing’. This is when individuals or organisations with a vested interested organise for very positive or very negative reviews to be left about particular products, services, and resources.
Data mining expert Bing Liu (University of Illinois) estimated that one-third of all consumer reviews on the Internet are fake. According to The New York Times, this has made it hard to tell the difference between “popular sentiment” and “manufactured public opinion.”
As a result, implementing a star rating system in MoodleNet, a global network for educators, would be fraught with difficulties. It assumes an objective, explicit context when no such context exists.
2. Best answer approach
This approach allows a community of people with similar interests to ask questions, receive answers, and have both voted upon. This format is common to Stack Overflow and Reddit.
Some of these question and answer pages on Stack Overflow become quite lengthy, with nested comments. In addition, some responders disagree with one another. As a result, and to save other people time, the original poster of the question can indicate that a particular answer solved their problem. This is then highlighted.
The ‘best answer’ approach works very well for knotty problems that require clarification and/or some collaborative thinking-through of problems. The result is then be easily searched and parsed by someone coming later with the same problem. I can imagine this would work well within MoodleNet community discussion forums (as it already does on the moodle.org forums).
When dealing with educational resources, however, there is often no objective ‘best answer’. There are things that work in a particular context, and things that don’t. Given how different classrooms can be even within the same institution, this is not something that can be easily solved by a ‘best answer’ approach.
3. Like-based systems
Sometimes simple mechanisms can be very powerful. The ‘like’ button has conquered social networks, with the best-known example being Facebook’s implementation.
I don’t use Facebook products on principle, and haven’t done since 2011, so let’s look at other implementations.
Social networks are full of user-generated content. Take YouTube, for example, where 400 hours of video is uploaded every single minute. How can anyone possibly find anything of value with such a deluge of information?
In the above screenshot, you can see a search for one of my favourite topics, The Bolshevik Revolution. YouTube does a good job of surfacing ‘relevant’ content and I can also choose to sort my results by ‘rating’.
Here is the top video from the search result:
I don’t have time to watch every video that might be relevant, so I need a shortcut. YouTube gives me statistics about how many people have viewed this video and how many people subscribe to this user’s channel. I can also see when the video was published. All of this is useful information.
The metric I’m most interested in, however, and which seems to make the biggest impact in terms of YouTube’s algorithm, is the number of upvotes the video has received compared to the number of downvotes. In this example, the video has received 16,000 upvotes and 634 downvotes, meaning that over 95% of people who have expressed an opinion in this way have been positive.
If I want more information, I can dive into the comments section, but I can already see that this video is likely to be something that may be of use to me. I would add this to a shortlist of three to five videos on the topic that I’d watch to discover the one that’s best for my context.
Going one stage further, some social networks like Twitter simply offer the ability for users to ‘like’ something. A full explanation of the ‘retweet’ or ‘boost’ functionality of social networks is outside of the scope of this post, but that too serves as an indicator:
This tweet from the UN about a report their Global Education Monitoring report has been liked 72 times. We don’t know the context of the people who have ‘liked’ this, but we can see that it’s popular. So, if I were searching for something about migrant education, I’d be sure to check out this report.
Although both YouTube and Twitter do not make it clear, their algorithms take into account ‘likes’ and ‘upvotes’ within the context of who you are connected to. So, for example, if a video has a lot of upvotes on YouTube and you’re subscribed to that channel, you’re likely to be recommended that video. Similarly, on Twitter, if a tweet has a lot of likes and a lot of those likes come from people you’re following, then the tweet is likely to be recommended to you.
Interestingly, many Twitter users use the limited space in their bios to point out explicitly that their ‘likes’ are not endorsements, but used to bookmark things to which they’d like to return. In the past year, Twitter has begun to roll out bookmarks functionality, but it is a two-step process and not widely used.
So likes act as both votes and a form of bookmarking system. It’s a neat, elegant, and widely-used indicator.
What does this mean for MoodleNet?
So far, we have discovered that:
The ‘quality’ of a resource depends upon its (perceived) relevance
Relevant resources depend upon a user’s context
We cannot know everything about a user’s context
MoodleNet will implement a system of both taxonomic and folksonomic tagging. Taxonomic tags will include controlled tags relating to (i) language, (ii) broad subject area, and (iii) grade level(s). Folksonomic tags will be open for anyone to enter, and will autocomplete to help prevent typos. We are considering adding suggested tags via machine learning, too.
In addition to this, and based on what we’ve learned from the three rating systems above, MoodleNet users will soon be able to ‘like’ resources within collections.
By adding a ‘like’ button to resources within MoodleNet collections, we potentially solve a number of problems. This is particularly true if we indicate the number of times that resource has been liked by community members.
Context – every collection is within a community, increasing the amount of context we have for each ‘like’.
Bookmarking – ‘liking’ a resource within a collection will add it to a list of resources a user has liked across collections and communities.
Popularity contest – collections are limited to 10 resources so, if we also indicate when a resource was added, we can see whether or not it should be replaced.
As discussions can happen both at the community and collection level, users can discuss collections and use the number of likes as an indicator.
Sometimes the best solutions are the simplest ones, and the ones that people are used to using. In our context, that looks like a simple ‘like’ button next to resources in the context of a collection within a community.
We’re going to test out this approach, and see what kind of behaviours emerge as a result. The plan is to iterate based on the feedback we receive and, of course, continue to tweak the user interface of MoodleNet as it grows!
What are your thoughts on this? Have you seen something that works well that we could use as well / instead of the above?
This week, we are releasing MoodleNet v0.5 alpha, which includes one of our most-requested features: a mobile web view! We’ve also implemented a bunch of UI tweaks and bug fixes.
Note that, after testing using BrowserStack, pretty much every combination of mobile device and web browser works except Apple’s Safari and Microsoft’s Edge browsers. This is due to a combination of some issues around supporting web standards, unfortunately.
For the moment we suggest that the community use other, more standards-compliant browsers to access MoodleNet. Some excellent choices include Opera, Mozilla Firefox and Google Chrome.
We didn’t manage to sneak in an ‘activity’ view for this release, but we’re working on it this week. This will allow you to see everything that’s happened within a community recently (e.g. new user/resource/collection added, new discussion thread).
As MoodleNet progresses and the team get into more of a rhythm, we’ve started working in two-week sprints. For the next few weeks, up to the beta release at the UK & Ireland MoodleMoot, we have plenty to do!
Earlier this week we released MoodleNet v0.3 alpha in preparation for inviting a new cohort of testers. It includes the following new functionality, UI tweaks, and bug fixes:
‘Profile & settings’ to update name, description, and avatar
Guide to Markdown next to text input boxes
Tweaks to fonts and colours to improve accessibility
New approach to discussions, which now act more like threads
List of communities indicates number of collections contained by each
No longer have to refresh to see added community/collection
Can see all communities again (fixed pagination)
We’ve removed edit functionality from MoodleNet at the moment in preparation for moderation. In future, you’ll be able to edit and delete comments and resources you add, or those in a community you moderate.
Given the amount of time between now and the beta launch at the UK Moot, we’re going to focus on what we consider to be essential to the core value proposition of MoodleNet:
Federation — the ability to have separate instances of MoodleNet that can communicate with one another.
Mobile view — MoodleNet accessible and usable on mobile devices.
Moodle Core integration — add a resource from MoodleNet to a course in a Moodle course.
Thank you to our testers, who are doing a great job of asking questions, reporting bugs, suggesting functionality, and filling in surveys!
We’ve learned a lot from the first testing round of MoodleNet, which ends this week. Our focus has been on testing the value proposition, “Do educators want to join communities to curate collections of resources?” It’s early days, but it would appear that yes, they do!
The wealth of feedback we’ve received during the first testing period really has been invaluable. Our enthusiastic bunch of 100 testers have shown us what they prefer, through their use of MoodleNet, responses to surveys, and suggestions via Changemap. Happily, we’re not ‘wiping’ or ‘resetting’ the HQ instance, so we’re encouraging the 100 testers to use MoodleNet beyond this initial period.
As demonstrated in a previous update, over the last three weeks we’ve added a lot of functionality to MoodleNet, made many improvements to the user interface, and fixed a number of bugs. We’re looking forward to seeing how 150 additional testers respond to MoodleNet when they get started next week.
It’s now two months until our planned beta launch at the UK & Ireland MoodleMoot, so the team has some very important functionality to work on. Soon, MoodleNet will be:
Mobile — access MoodleNet on-the-go
Searchable — find communities, collections, and people across all of MoodleNet’s federated instances
Connected — import resources you discover on MoodleNet into courses in Moodle Core
Federated — join any instance of MoodleNet and interact with communities, collections, and other users across all instances
The MoodleNet team would like to thank the Moodle community for the encouragement and feedback we’ve received so far. We’re dedicated to creating an easy-to-use environment where educators can share, curate, and discuss!