Simon Coggins

I think these are all good suggestions, would you be able to create a separate feature or improvement bug for each one in the Moodle Tracker?

I don't think removing open badges support is necessary to make those changes. For example, with upgradable badges the badge within Moodle could replace the previous one, independent of if it has been uploaded to a backpack. The user would end up with two badges in their backpack if they are using it but that wouldn't impact the internal Moodle behaviour.

Since using the open badges format shouldn't impact on Moodle features, I'd prefer to keep that functionality, unless there is a very clear case where it is undesirable (rather than just not needed).

Although you might not expect your students set up a backpack or to export them, some of them might want to (even for trivial badges), for example if they are leaving the school/institution where they earned them. The whole point of the Mozilla system is that the user has control over the badges that they have earned, and having that control should, if anything, increase motivation further.

Simon

You are right that those core changes are currently needed, and I agree that it should be easier. Probably the most sensible approach is to make criteria a sub-plugin type. The criteria could then be shared via the plugins database.

Thanks for posting the improvement bug on this subject.

Simon

The original motivation behind not deleting badges was so that students who have already earned the badge don't lose them when they are deleted. While that makes sense in some cases, there are others (like the ones you describe) where it does make sense to delete the data.

One option would be to give the person deleting the option when they delete a badge. We could also add an option to remove individual records via the Awards tab.

If the user has already downloaded the badge we can't get it back, but if the record is deleted the badge would no longer be verifiable.

Would you be able to file a new feature bug in the tracker to track this issue?

Simon

Hi William,

At the moment we haven't created a badge criteria that is dependent on earning other badges. It's definitely something that we'd like to do though and it should be fairly straightforward as criteria are designed to be extended. You could definitely create a feature bug in the tracker for that one.

The second part (removing the earlier badges when the later ones are achieved) would be more work. I know Mozilla have some plans around badges that "fill up" as you progress so that might meet your needs. Currently that's scheduled to be implemented by Mozilla in version 1.5 (third quarter of this year):

https://github.com/mozilla/openbadges/wiki/Open-Badge-Infrastructure-Roadmap

The only info I can find on the open badges wiki is here:

https://github.com/mozilla/openbadges/wiki/Discussion:-Composite-and-Ranked-(or-Leveled)-badges./afa0e86bace1fe8e042eafb241f6743aea0ff08e

but it's an old discussion from their wiki that has since been deleted.

Hope that helps,

Simon

Hi William,

Sorry I'm not sure, I can't think of any significant changes to the filepicker in 2.4 or 2.5. Maybe you can find something in the API changes log:

http://docs.moodle.org/dev/Moodle_2.4_release_notes#For_developers:_API_changes

http://docs.moodle.org/dev/Moodle_2.5_release_notes#API_changes

Simon