May be this is a German perspective, but we think it will be relevant for others also.
During analysing badges feature we found some issues that should be solved. If we haven't found some existing features or settings.
- Most organization will start work with badges in test courses. The badges users get from this courses can't be deleted. This should be possible.
- If a students gets a quiz result and therefor a badge, but afterwords the teachers finds that the student cheated during the quiz, normally he would delete the quiz attempt and results. It should be possible to delete such badges by anybody inthe system. Its clear that there is no influence if the student exported the badge in between.
- There are lots or workers council contracts that personal data about performance data. Most of the time its not allowed to hold such data endless in databases. They have to be deleted fully if a students gets from the school/univesity, the employee leaves the company of time based after some years. Its a little bit similar to log data that have to be deleted after weeks or months.
We didn't found an option to really delete such data in the database fully.
Add system settings:
- delete user badge data if the account is deleted
- delete badges after x month, x years fully.
German Moodle Partner
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?
About item 2) : the Mozilla Open Badges project is working on adding a method of revocation for badges, even once a badge is out of the system, to cover issues like cheating etc.
But to do so requires that the original issuing system must be available for verification that it is the issuer (item 3).
To do that securely will require cross network and application communication standards (yet to be decided on or built) and a ping back mechanism from the badge or backpack to the original issuer. That's not a trivial problem.
Until all that happens, the best an application can do is add some features to better handle the badges at the local level - like marking a badge as "test" etc. - knowing that once the badge is downloaded by the user, it it an independent entity.