Skip to content

Runestone Issue: assignment links don't force a student to be in the right course #1494

Description

@Tanaquil18

I don't use LTI and most of the time in my LMS I have an assignment where I link to where the problems can be found within the textbook. But occasionally I link to an assignment directly, like https://runestone.academy/assignment/student/doAssignment?assignment_id=288453

It appears that if one is not logged into Runestone at all and you click a link like that, then you are prompted to log in first. But if you are logged into Runestone but a different course is their active course, Runestone still lets them see the assignment and complete work there. But that work is not part of the course where the assignment is from and so they get a 0.

I've tried this both in pretext-based student page course and a course where I've unchecked that box - same behavior in both courses, except even harder to tell what's wrong in the non-PreTeXt based student page course.

For WeBWorK problems after activating and submitting an answer there is a small message that appears at the bottom of the problem that scores are not updated because submissions are closed, but I have had multiple students either not notice or not realize why this was happening to them when the assignment is clearly open and before the due date in the correct course. I don't know what message or warning occurs with other question types.

This is a pretty big problem when we are using Runestone with multiple courses in a single semester, and students are not prompted to change courses if we link directly to a Runestone assignment. If for some reason this is in fact the desired behavior, can we make the warnings much, much more prominent?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions