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.

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

Clarify How to Select Alternate/Etc Seating #34

Open
cycomachead opened this issue Dec 12, 2023 · 5 comments
Open

Clarify How to Select Alternate/Etc Seating #34

cycomachead opened this issue Dec 12, 2023 · 5 comments

Comments

@cycomachead
Copy link

We shouldn't have to specify 'alternateseating' as an attribute to for the student when assigning seats

@Reimirno
Copy link

Currently, for alternate seating, we would need to:

  1. Manually label certain seats of a room "alt" label.
  2. Make sure all students prefer "alt" label.
    Which is kind of not convenient.

I hope there is an algorithmic way to determine alternate seating directly.

@cycomachead
Copy link
Author

For 1, I think manually specifying the seat map layout makes sense.
For 2: Bulk edits and or a function which says "Assign with a default attribute" or something might work around this

@Reimirno
Copy link

Reimirno commented Feb 15, 2024

For 1, I think manually specifying the seat map layout makes sense. For 2: Bulk edits and or a function which says "Assign with a default attribute" or something might work around this

That we already have. See #47

Is that feature sufficient? If so I will close this issue.

@cycomachead
Copy link
Author

Hmm. I think but let me see

What I was imagining for ease would be:

  • student prefs are persisted with the specific data (right, left, wheelchair, etc)
  • data about a layout type is only applied when the assignment step

This would potentially make it easier to test out different layouts

@Reimirno
Copy link

Hmm. I think but let me see

What I was imagining for ease would be:

  • student prefs are persisted with the specific data (right, left, wheelchair, etc)
  • data about a layout type is only applied when the assignment step

This would potentially make it easier to test out different layouts

What about having a course-wide preferences/avoids? Instead of just student-level preference/avoids.
That course-wide preferences/avoids do not persist or link to specific student and needs to be entered before you click "assign". and those attributes are kinda just added to all students and work the same way as student-level preferences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants