Overview
The unidigital initiative wants to contribute some minor but important enhancements to the FeedbackXblock
Problems
When a course team want to use the feedbackxblock in multiple places of the course to capture fine grained ratings and feedback, there is no easy way to see the aggregated results.
There interface for configuring the feedbackXblock is not up to the best standard in terms of UI / UX
The component is currenly only supported in english
Use cases:
As an instructor, I want to easily add ways for learners to give ratings and feedback about the course experience, and have a place to see all the feedback colected across all the course.
As a learner I want to be able to rate the course content and provide feedback, ideally using an interface in my own language.
Proposed solution:
The Unidigital project (Spanish universities consortium) is interested and motivated to contribute the following improvements to the FeedbackXblock:
to present a new tab on the instructor dashboard with the aggregated ratings data and the comments received for each feedbackxblocks in the course
to change the settings interface to allow you to configure things like the title, the thank you message, and the visibility of the aggregated scores
to add a third set of images for the rating interface (it currently supports faces and numbers), namely stars icons.
to fix some glitches in interface for editing the settings of the xblock in studio
to add Spanish translations to the component
Other approaches considered:
we have also considered forking the Xblock and building a new version with these changes, but since they are minor improvements and aditions to the capability of the current component, it feels like a suboptimal approach not to contribute the changes to the official xblock.
Competitive research:
How do Canvas/Moodle/Coursera solve this problem?
TBD
Proposed plan for any relevant usability/UX testing
TBD
Plan for long-term ownership/maintainership
edunext is commited to build and contribute this work as part of the unidigital (spanish government) project. As part of that commitment, edunext would commit to maintain the feature for a minimum of 2 years and after that, either find a suitable maintainer to hand it over to, or to follow a the deprecation procedure in case the feature has any inconvenience or its maintenance is a burden that no one can carry.
Open questions for rollout/releases
TBD