Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add concept of "attachments" to feedback threads #6610

Open
seanlip opened this issue Apr 15, 2019 · 4 comments
Open

Add concept of "attachments" to feedback threads #6610

seanlip opened this issue Apr 15, 2019 · 4 comments
Labels
enhancement Label to indicate an issue is a feature/improvement full-stack Impact: Low -- DO NOT WORK ON THIS YET Postponing for now, since it doesn't affect users much. Work: High It's not clear what the solution is; will need investigation.

Comments

@seanlip
Copy link
Member

seanlip commented Apr 15, 2019

The aim of this feature request is to add the concept of "attachments" to generalized feedback threads, so that users who submitted feedback can provide more information to creators on how to improve the lesson. A specific type of attachment is the learner's playthrough up to that point (for exploration feedback threads), but others might be possible.

Describe the solution you'd like

Users should be able to have the option of sending their playthrough along with feedback threads they create, so that the lesson creator can use it to improve the lesson.

@amey-kudari
Copy link
Contributor

amey-kudari commented Apr 17, 2019

Hi @seanlip!
I think we append the order of cards the user went through in the feedback text (as the last line/footer of the feeback thread message). What I mean is when the user starts an exploration, initialize a stack and when the user gets redirected to a new card, push the old card name to the stack. I feel this should give the author a decent idea of how the user reached a card that he has not understood.
Also I feel we can add the card name as the title and mention that its a student feedback in the title instead of abbreviated text (#6542).
And considering the user is stuck on a particular card, I think its better to add his interaction state to the feedback thread message.
( By interaction state I mean his conversation with the Oppia otter :) (feedbacks he has got for choosing the incorrect options if he has chosen any)
And this will not modify the experience of the user in any way. The feedback will be taken from the text box as usual, and the additional data will be appended on front-end before making a post request to add feedback thread.
Mock based on what I am trying to explain:
(card name student is stuck on: calculating ratios )
Screenshot from 2019-04-18 03-48-44
Screenshot from 2019-04-18 03-49-10

Thanks!

@seanlip
Copy link
Member Author

seanlip commented Apr 17, 2019

Hi @amey-kudari, I think this might work if we just cared about the individual card, but I think the idea here is more to see the full playthrough from the beginning of the lesson to this point. So I'm not sure it's feasible to include all that info in a regular comment, we'll probably need a separate view for it.

@amey-kudari
Copy link
Contributor

Hi @seanlip,
Can we include the entire conversation with the card name, I mean the answers of the user and the responses he got (feedback from the otter)?
I am not sure about displaying it, I was thinking we can make a "show path" option, And send the entire conversation through the text and decode it at the feedback tab but I am not sure how we can separate these feedback threads from other feedback threads.
Can we use the state-name in case to separate the threads by giving all student feedback threads a state-name of "![student-feedback]" Considering we already have the state name in the subject of the feedback.

Thanks!

@seanlip
Copy link
Member Author

seanlip commented Apr 18, 2019

No, the conversation is too long to include here. We already have some functionality for showing playthroughs in the stats tab (talk to @pranavsid98 for details) and reusing that seems like it would be better.

@kevintab95 kevintab95 added this to Awaiting Triage in Learner and Creator Experience via automation Feb 2, 2020
@iamprayush iamprayush moved this from Awaiting Triage to Full Stack in Learner and Creator Experience Feb 15, 2020
@aks681 aks681 moved this from Full Stack to Low Priority in Learner and Creator Experience Feb 22, 2020
@kevintab95 kevintab95 moved this from Low Priority to Learner Pages in Learner and Creator Experience Aug 16, 2020
@nithinrdy nithinrdy removed this from Lesson-Related Learner Pages (@aks681) in Learner and Creator Experience Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Label to indicate an issue is a feature/improvement full-stack Impact: Low -- DO NOT WORK ON THIS YET Postponing for now, since it doesn't affect users much. Work: High It's not clear what the solution is; will need investigation.
Projects
Status: Todo
Development

No branches or pull requests

3 participants