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.

Sign up for GitHub

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

Jump to bottom

[Feature Request]: Measure lesson progress correctly (Learner Dashboard Redesign) #21486

Open
amyyeung17 opened this issue Dec 19, 2024 · 2 comments
Open

[Feature Request]: Measure lesson progress correctly (Learner Dashboard Redesign) #21486

amyyeung17 opened this issue Dec 19, 2024 · 2 comments
Labels
enhancement Label to indicate an issue is a feature/improvement Impact: Medium Will improve quality-of-life for at least 30% of users. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.

Comments

@amyyeung17
Copy link
Contributor

amyyeung17 commented Dec 19, 2024 •
edited
Loading

Is your feature request related to a problem? Please describe.

This is part of #18384. Currently, there is no way to determine intermediate progress of explorations, collections, and nodes within the classroom lessons. Thus, when starting any of them will always return 0/start in the UI even if more has been done. Skill progress may also be affect, although I'm not positive.

Additional note: If a student starts a story in a classroom with several canonical story summaries, all of the summaries are considered in-progress even if the student has not tried the others.

Describe the solution (or solutions) you'd like

  • Verify skill progress in progress tab is being reported correctly
    • Check how the old dashboard measures progress and see if that fits what we need.
  • Verify canonical story summaries are being appropriately added to in-progress sections
  • Find a way to record and track actual progress within explorations, collections, and story nodes
    • StoryNodes have checkpoints which we might able to use
  • Adjust the UI as necessary. Impacted areas include all the tabs.
    • All lesson cards that show progress, affects button text and number
    • Goal list should display start/resume button depending on progress.

Describe alternatives you've considered and rejected

N/A

Additional context

N/A
@amyyeung17 amyyeung17 added triage needed enhancement Label to indicate an issue is a feature/improvement labels Dec 19, 2024
@amyyeung17 amyyeung17 changed the title [Feature Request]: Measuring progress (Learner Dashboard Redesign) [Feature Request]: Measure lesson progress correctly (Learner Dashboard Redesign) Dec 19, 2024
@amyyeung17 amyyeung17 mentioned this issue Dec 19, 2024
Open
@HardikGoyal2003
Copy link
Member

Hi @amyyeung17, thanks for filing the issue. Could you please link to the specific lines of code where contributors should begin? Additionally, if possible, could you include a video demo showing the issues that arise when this requested feature is missing?

@amyyeung17
Copy link
Contributor Author

amyyeung17 commented Dec 22, 2024 •
edited
Loading

Hi @HardikGoyal2003. Unfortunately, this is a rather complex issue and affects the backend too. Correct me if I'm wrong, but it seems like there's no way to measure the progress of LessonExplorationSummary, CollectionSummary, and StoryNode. If so, contributors will need to modify the models.

There aren't any features missing. This just affects the user interface from showing the correct values. For example, the first in-progress lesson card displays 0% and Start button even though having already started it. It'll continue to show 0% until the user completes the entire StoryNode.

user-data.mov

I'm happy to fix the user interface once these things are implemented since I'm most familiar with it. I updated the post with some suggestions on where to start. I can explain more in-depth to whoever takes up the issue.

@seanlip seanlip added Impact: Medium Will improve quality-of-life for at least 30% of users. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. labels Dec 29, 2024
@amyyeung17 amyyeung17 mentioned this issue Dec 29, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Label to indicate an issue is a feature/improvement Impact: Medium Will improve quality-of-life for at least 30% of users. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.
Projects
LaCE Quality Team
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@seanlip @amyyeung17 @HardikGoyal2003