-
Notifications
You must be signed in to change notification settings - Fork 411
[FIX] LTI: Provide outcome status lists for LP collections #11641
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
Merged
+48
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Saaweel ,
I just stumbled across these changes and am not sure whether the overridden methods have been implemented as intended. From my understanding
_getInProgress,_getCompleted,_getFailedand_getNotAttempetedare expected to return lists of user IDs for the respective status based on the underlying learning progress data, rather than on the aggregated status values stored inut_lp_marks.
Let's assume that
\ilLPStatusWrapper::_refreshStatus()is invoked for the consuming object. This eventually calls\ilLPStatus::refreshStatus(), which in turn invokes the methods overridden here.
The returned user ID lists are then used to persist the corresponding learning progress status in
ut_lp_marks.
Kind regards,
Michael
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @mjansenDatabay ,
thanks for the feedback, and sorry for the late response. I had not seen your comment earlier because, for some reason, GitHub did not notify me about it.
I reviewed this again and agree that these methods should not derive their user lists from
ut_lp_marks, since they can also be used duringilLPStatusWrapper::_refreshStatus()to recalculate and persist that table.I prepared a follow-up PR that derives the LTI outcome status lists from the underlying outcome data instead:
#11667
The lists now use
lti_consumer_resultsandlti_consumer_grades, if available, and classify users through the existingdetermineStatus()logic. This keeps parent object / LP collection aggregation working without depending on the aggregated LP table.Kind regards,
Saúl