Skip to content
This repository has been archived by the owner on May 25, 2021. It is now read-only.

Add support to store and show section status in place of seat numbers #398

Open
2 of 5 tasks
Bad-Science opened this issue Jan 31, 2019 · 0 comments
Open
2 of 5 tasks
Assignees
Labels
class:feature This issue describes a new feature priority:high This issue has a high priority service:adapter This issue involves an adapter service service:core This issue involves the core service service:web This issue involves the web service size:epic This issue is an epic status:inprogress This issue is actively being addressed university:nyu Specific to NYU university:rpi Specific to RPI
Milestone

Comments

@Bad-Science
Copy link
Member

Bad-Science commented Jan 31, 2019

It seems as though we will be unable to acquire exact seat numbers for NYU, at least initially. Instead of providing seat numbers, NYU's system displays a status text instead.

The possible statuses of a section are:

`Open`
`Closed`
`Wait List (<N>)` (although all I have seen is `Wait List (0)`
`Cancelled`

YACS should be able to ingest a status as well as seat numbers, but not require either to function. If seat numbers are not available, they should not be displayed, and if a status is not available, one should not be displayed.

This actually works out well, because we have received feedback from students at RPI in the past that showing only the number of seats total and the number of seats available often leaves some confusion as to whether a section is closed. So we should add a status to the RPI data adapter based on the number of seats. Because the status can be derived in the case of RPI, this will technically be redundant, but it is a small amount of data and will improve clarity and generalization.

This issue can be marked completed when the following subtasks are completed:

This issue was migrated from YACS-RCOS/university#8

@Bad-Science Bad-Science added priority:high This issue has a high priority service:web This issue involves the web service service:core This issue involves the core service class:feature This issue describes a new feature size:epic This issue is an epic service:adapter This issue involves an adapter service status:readyfordev university:rpi Specific to RPI university:nyu Specific to NYU labels Jan 31, 2019
@Bad-Science Bad-Science added this to the Release 0.13 milestone Feb 2, 2019
@fakedestinyck fakedestinyck self-assigned this Mar 8, 2019
@fakedestinyck fakedestinyck added status:inprogress This issue is actively being addressed and removed status:readyfordev labels Mar 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
class:feature This issue describes a new feature priority:high This issue has a high priority service:adapter This issue involves an adapter service service:core This issue involves the core service service:web This issue involves the web service size:epic This issue is an epic status:inprogress This issue is actively being addressed university:nyu Specific to NYU university:rpi Specific to RPI
Projects
None yet
Development

No branches or pull requests

2 participants