Make a student inside a already randomized room lockable for another randomized round

[mpagels]

I have a feature idea:

As an user
I need to "lock"studetnts inside an already randomized room
so that I can lock students, and they get not randomized again and stay in the room the next randomize round

Description (Text, Scribble, Wireframe, Design)

Let's say we have a group with 3 very advanced students, and you want every one of them in separate rooms, so that they can help the others students. Sometimes I have to randomize the students a lot to get a good mix of students. Maybe we can "lock" them, so they don't get randomized again and stay in the "locked" room.

The exported images should not show the lock, so the students don't know it was not a "real" randomize.

Acceptance criteria

• after the first random breakout room assignment, a lock is shown after every name
• when I click the lock, the name is "locked" to the room
• and would not be assigned randomly the next time I click the randomize button
• I can lock more than one student in one room
• I can lock more students in different rooms
• when I "unlock" them, they got back in the "randomize" pool and would be randomized again
• when I "export" the image for the students, the lock is invisible for them
• when the students visit the page, the lock is invisible for them

What do you think?

[jamarob]

Thanks Martin! This is a nice idea, but it violates some of the assumptions I made when I wrote the randomization logic. I am a little bit too tired to elaborate now but will get back to it tomorrow 😪

[jamarob]

Hi Martin, sorry for the late reply, I was super busy but I have put some thoughts into your suggestions.

When I wrote the app I wanted it to be very transparent - same seed for same students and rooms always generates the same distribution. Locking some students in certain rooms just adds another variable but it will be deterministic as well, so no problem there.

The page for sharing the groups (and the image as well) do not care how the distribution was done, it is simply passed in as a query parameter.

However, in some courses the groups are generated by the students and we can not prevent this very students from fudging with the groups without adding some kind login and user management.. but I guess that's more a matter of trust.

I can whip something up in a feature branch and then let's see how to go from there.

Any thought?