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

Implement mechanism to handle update to topics with saved progress [Blocked on #169] #3492

Open
MaskedCarrot opened this issue Jul 17, 2021 · 3 comments
Open

Implement mechanism to handle update to topics with saved progress [Blocked on #169] #3492

MaskedCarrot opened this issue Jul 17, 2021 · 3 comments
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@MaskedCarrot
Copy link
Contributor

MaskedCarrot commented Jul 17, 2021 •
edited
Loading

On updating a topic and/or a lesson, the student progress will not be saved because of the pedagogical constraints involved in the lesson updates which render it difficult to identify how to extrapolate the previous lesson’s progress into the updated lesson. Therefore, the saved version will be deleted and replaced by the updated version of the lesson and the user will have to start over from the beginning. (for more context see Oppia Android Checkpointing PRD.)

A topic/and or lesson with saved progress can be either

  • Deleted
  • Updated

If the topic/and or lesson with saved progress is deleted, there should be no change in the saved progress and the users should be able to resume the lesson using the saved progress when the lesson is re-downloaded.

If the topic/and or lesson with saved progress is updated, the structure of the exploration may change, so in this case, the progress should be not be used to resume the checkpoint and the user should start the lesson from the beginning.
@MaskedCarrot MaskedCarrot added Where: Infrastructure Priority: Essential This work item must be completed for its milestone. Type: Task A single task of work corresponding to a greater milestone. Generally corresponds to a single PR. labels Jul 17, 2021
@MaskedCarrot MaskedCarrot added this to the GSoC 2021.5: Milestone 2 milestone Jul 17, 2021
@MaskedCarrot MaskedCarrot self-assigned this Jul 17, 2021
@MaskedCarrot MaskedCarrot removed their assignment Aug 14, 2021
@MaskedCarrot
Copy link
Contributor Author

Un-assigning myself from this issue, because this issue is no longer a part of the project "implement light-weight checkpointing" As topic downloads is not yet complete, so this issue is currently blocked on #169, #396

@MaskedCarrot MaskedCarrot removed this from the GSoC 2021.5: Milestone 2 milestone Aug 14, 2021
@MaskedCarrot MaskedCarrot changed the title Implement mechanism to handle update to topics with saved progress Implement mechanism to handle update to topics with saved progress [Blocked on #169, #396] Aug 14, 2021
@seanlip
Copy link
Member

seanlip commented Aug 14, 2021

@MaskedCarrot Please could you update the description of this issue to be clearer about what needs to be done and what the objectives/approach are (as much information as you know)? Thanks.

@MaskedCarrot MaskedCarrot changed the title Implement mechanism to handle update to topics with saved progress [Blocked on #169, #396] Implement mechanism to handle update to topics with saved progress [Blocked on #169] Aug 15, 2021
@MaskedCarrot
Copy link
Contributor Author

@seanlip I have updated the issue description to more clearly explain what has to be done.

@Broppia Broppia added issue_type_infrastructure Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 14, 2022
@BenHenning BenHenning added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Z-ibt Temporary label for Ben to keep track of issues he's triaged. issue_user_learner and removed Impact: Low Low perceived user impact (e.g. edge cases). labels Sep 15, 2022
@seanlip seanlip added bug End user-perceivable behaviors which are not desirable. and removed issue_type_infrastructure labels Mar 28, 2023
@adhiamboperes adhiamboperes added Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. and removed Priority: Essential This work item must be completed for its milestone. Type: Task A single task of work corresponding to a greater milestone. Generally corresponds to a single PR. labels Jul 31, 2023
@adhiamboperes adhiamboperes added enhancement End user-perceivable enhancements. and removed bug End user-perceivable behaviors which are not desirable. labels Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Projects
[Team] Core Learner and Mastery flows & UI Frontend - Android
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
5 participants
@seanlip @BenHenning @MaskedCarrot @adhiamboperes @Broppia