Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

The events are user specific and not in bulk form.

  • No API changes required inQuiry

  • New Kafka message consumers to be created to consume these 2 events (Gauraw Kumar - please fill in the details of Flink jobs).

  • In case of User Deletion,

    • The user name needs to be cleared out with a static default name (Deleted User). Refer

    • The User Name is stored in the below attributes,

      • creator

      • author

      • publisher

      • owner

    • The User Id (UUID) is stored in the below fields, 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

Discussion items

  • Retired questions and questionsSets can be left un-modified?

  • Bundles (ecar) also has these attributes. Needs update / republish (TBD with Kartheek)

  • Should we update the Author Name? As there is no UUID for author.

    • If needs to be updated, we need user name (first name, last name) in the message from Lern for us to cross check if it is the same user name.

    • Creator can be different from author and sometimes the author name is added automatically as creator name

Technical Design

<<TODO - Gauraw Kumar >>

  • Details of Flink jobs

  • Details of searching and updating Neo4J

  • Details of searching and updating ES