search

mozilla / aestimia

[Archived] Assessment tool
4 stars 10 forks source link

Allow mass deletion of submissions on a per-learner basis #37

Open toolness opened 11 years ago

toolness commented 11 years ago

I think COPPA requires us to be able to wipe all traces of a kid's existence from the internet.

This means Aestimia should probably have an endpoint that allows all submissions from a particular learner to be permanently deleted.

iamjessklein commented 11 years ago

just a minor point here, but is it possible to make it so that in addition to all submissions being deleted, all submissions could also be downloaded?

toolness commented 11 years ago

Er... well I should clarify, actually, that Aestimia doesn't believe it "owns" the evidence URLs that were given to it by the client (which in CSOL's case would be the CSOL website). So by "deletion of submissions" I really only mean the deletion of the submission metadata that Aestimia has the ability to delete--the reflection data, rubric, assessment, and so forth. So it might actually make more sense to create an API endpoint that the client can use to delete Aestemia's knowledge of a learner--but that client will be responsible for deleting all the data that Aestimia doesn't control, like the evidence URLs.

If by "downloaded" you also mean the evidence URLs, we'd have to talk about what format the download would take, and how it'd be structured... Would it be a static website in a ZIP file that the user could browse on their local filesystem? Or something else? Et cetera. Probably a separate bug should be filed for it.

cmcavoy commented 11 years ago

CSOL owns all the evidence, so all of this should probably be in CSOL.

On Wed, May 29, 2013 at 1:57 PM, Atul Varma notifications@github.comwrote:

Er... well I should clarify, actually, that Aestimia doesn't believe it "owns" the evidence URLs that were given to it by the client (which in CSOL's case would be the CSOL website). So by "deletion of submissions" I really only mean the deletion of the submission metadata that Aestimia has the ability to delete--the reflection data, rubric, assessment, and so forth. So it might actually make more sense to create an API endpoint that the client can use to delete Aestemia's knowledge of a learner--but that client will be responsible for deleting all the data that Aestimia doesn't control, like the evidence URLs.

If by "downloaded" you also mean the evidence URLs, we'd have to talk about what format the download would take, and how it'd be structured... Would it be a static website in a ZIP file that the user could browse on their local filesystem? Or something else? Et cetera. Probably a separate bug should be filed for it.

— Reply to this email directly or view it on GitHubhttps://github.com/mozilla/aestimia/issues/37#issuecomment-18638350 .

@chmcavoy http://twitter.com/chmcavoy http://lonelylion.com

iamjessklein commented 11 years ago

@toolness agreed. I think that most important thing (from an end user perspective) to keep is the evidence url's and possibly the badges. let's circle back to that.