Anonymize users on deletion

Open
#841 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
backend, databases

Research direction

Start by tracing deletion handling for the user, completion, completion_registered, user_course_settings, and verified_user records. Determine which email, name, and username fields must be anonymized, how certificates are synchronized with other systems, and which extra user_course_settings data must remain; done means these requirements are defined and consistently handled.

Written by the indexing model from the issue text.

Description

  • sync with other systems that may store info such as certificates
  • emails, names, usernames (?)
    • stored at least inside user, completion, completion_registered, user_course_settings, verified_user
  • don't zap all extra (non-anonymizable) data in user_course_settings that might have use in the future
Dominant language
TypeScript
Stars
6
Forks
7
Avg merge
25m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rage/mooc.fi

All issues in rage/mooc.fi

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.