User Feedback support

[soumendrak]

As users will use the system, it is necessary that we take feedback from them. The model should learn from this feedback.

Also, we need to check all the feedback may not be constructive, so review mechanism needs to be there as well to validate the user feedback.

There will be three kinds of primary feedbacks received from users:

1. Thumbs Up i.e. positive, the user is happy with the translated text
2. Thumbs Down i.e. negative, the user is unhappy with the translation
3. No feedback i.e. user will not give any feedback at all.

The review process should start from the top-most query text and topmost feedbacked text.
It's fine if the review process can not be automated on this release.

[akpanda]

Probably following can be elaborated a little more @soumendrak. Are we anticipating an UI for this user feedback 😺?

The review process should start from the top-most query text and topmost feedbacked text.
It's fine if the review process can not be automated on this release.

[soumendrak]

UI will be better. That also needs to be RBAC (Role-Based Access Control) enabled i.e. only admins should be able to see this report.
It is like a deep dive into how user's are using the system.

This the proposed requirement:

• When an admin login into the system, there will be a tab or hamburger menu item naming analytics maybe.

• There will be a section named Most queried texts with descending order of the query count.

• Query count should be displayed along with the query text.

• While the admin clicks on each individual query, s/he can check
  - the results (translated text) received by the user and
  - the user feedback on this i.e. how many thumbs up and down

• This result will be provided as feedback to the Core ML model, where are we doing good and where failing and users want us to pass.

• Similarly, another section will be there named Feedback received with descending order of feedback count.

• Feedback count should be displayed beside the queried text.

• The rest part remains the same.

In this activity, more work will be at the backend side and once the project is live this feature is a must need.
FYI: @subhadarship

[subhadarship]

Interesting! Some of these (e.g, receiving feedback) needs work, but logging the user's query and the server's response has already been done (#16 ).