Overview
The user deletion requirement in inQuiry has been originated from the below requirement.
...
FE Design Lern - /wiki/spaces/SUN/pages/3359146039
What is changing?
The user can request for deletion of their account in Sunbird, this means two primary actions to happen.
User's Personal Identifiable Information (PII) needs to be removed
The assets (like questions, questionSets, content etc) that was created by this user needs to be transferred to an identified user.
Scope for inQuiry
Inquiry in its question bank stores the users name and id as part of question and questionSet meta data.
...
Neo4J
Cassandra (In case of hierarchy)
Elastic Search
Redis (For Live Objects)
Cloud (ECAR Bundle)
Changes in inQuiry
The below two events will be flowing into inquiry as messages which originated from the Lern system.
...
No API changes required
A flink job has to be created to consume these 2 events.
In case of User Deletion,
The user name needs to be cleared out with a static default name (Deleted User). Refer
The User Name could be stored in the below attributes as per sunbird inQuiry schema,
creator
author
publisher
owner
The User Id (UUID) is stored in the below fields as per sunbird inQuiry schema, this will be left as is.
createdBy
lastPublishedBy
lastUpdatedBy
lastSubmittedBy
| Info |
|---|
createdFor is an attribute that stores the organisation name. It is confirmed that the users in the scope of inQuiry, i.e; creator or reviewer, will always have an organisation. |
Impacts if any
No impacts detected,
As the searches are based on UUID and that is retained
In the consumption flow only the author name is displayed
Technical Design
...
A flink job will will be written to consume both message (user deletion and ownership transfer)
This flink job will only deal with two object type Question & QuestionSets.
Assets (appIcon, images/audio/video used as options/solutions) used under Question/QuestionSets will not be processed by this flink job.
Those assets should be processed by Knowlg Flink job as inQuiry uses only artifactUrl metadata of those assets. So no dependency from inQuiry functionality.
...
Will be updated in Phase-2