You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there are quite a few variants of the "Next" button: one that gets the first student in the queue, one that gets the first passoff in the queue, and each of these buttons' online variants which selects only online students. There might be a cleaner way to do this, and it's worth looking into.
Although this is part #16, it doesn't necessarily have to be solved through automation. I will propose two solutions: one that has automation in mind - and one that doesn't.
Proposed Solutions
(Automation) - Reduce the amount of "Next" buttons to just one. If the TA is in-person, "Next" will select the first student in line. If today is a passoff day (see Passoff Day Notifications #18), "Next" will select the first passoff in line. If the TA is online-only (probably indicated with a separate button that toggles online/in-person), "Next" will select the first online student. If you want to get really fancy, in-person Next could check if there are online-only TAs online, and if there are, it will softly prefer in-person students.
(Non-Automated) - Reduce the amount of "Next" buttons to just one. When the button is pressed, some kind of menu will display the students currently in the queue, from which the TA can select a student to help. This is a much simpler solution than the first, but requires more effort from the TAs, though that effort is very low. The one concern I have is that it is unlikely that the menu produced by the button will be dynamic enough to support changes to the queue after the button is pressed, so if two TAs try to help the same student at roughly the same time, there's a chance to have some unexpected behavior.
Overview
Currently there are quite a few variants of the "Next" button: one that gets the first student in the queue, one that gets the first passoff in the queue, and each of these buttons' online variants which selects only online students. There might be a cleaner way to do this, and it's worth looking into.
Although this is part #16, it doesn't necessarily have to be solved through automation. I will propose two solutions: one that has automation in mind - and one that doesn't.
Proposed Solutions
(Automation) - Reduce the amount of "Next" buttons to just one. If the TA is in-person, "Next" will select the first student in line. If today is a passoff day (see Passoff Day Notifications #18), "Next" will select the first passoff in line. If the TA is online-only (probably indicated with a separate button that toggles online/in-person), "Next" will select the first online student. If you want to get really fancy, in-person Next could check if there are online-only TAs online, and if there are, it will softly prefer in-person students.
(Non-Automated) - Reduce the amount of "Next" buttons to just one. When the button is pressed, some kind of menu will display the students currently in the queue, from which the TA can select a student to help. This is a much simpler solution than the first, but requires more effort from the TAs, though that effort is very low. The one concern I have is that it is unlikely that the menu produced by the button will be dynamic enough to support changes to the queue after the button is pressed, so if two TAs try to help the same student at roughly the same time, there's a chance to have some unexpected behavior.