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

[BACKLOG] Change GenEd override from section-level to course-level #462

Open
2 of 6 tasks
bombnp opened this issue Jan 13, 2023 · 0 comments
Open
2 of 6 tasks

[BACKLOG] Change GenEd override from section-level to course-level #462

bombnp opened this issue Jan 13, 2023 · 0 comments
Labels
cu-scraper Related to CU Scraper cugetreg-api Related to cugetreg-api cugetreg-web Related to cugetreg-web enhancement Improve existing features

Comments

@bombnp
Copy link
Member

bombnp commented Jan 13, 2023

Problem

Currently, our gened overrides are uniquely idenified with (courseNo, semester, academicYear, sectionNo). However, we recently discovered that we may not have to be specific and just specify with (courseNo) only, because the section doesn’t not affect one’s quality for graduation. This would significantly reduce the effort required to maintain CU Get Reg every semester.

This would achieve the following:

  1. No more preparing gened override csv files stating which course and sections are gened.
  2. We wouldn’t incorrectly show gened sections anymore since that could change at anytime and we can’t keep up.

Task Description

  1. Change override schema to contain course-level gened override (api/scraper)
  2. Remove genedtype fields in GraphQL types (codegen)
  3. Remove gened chips in section card (web)
  4. Other, as needed.

Additional Context

No response

Related Teams

  • Frontend
  • Backend
  • Data
  • Design
  • Infra
  • QA

Task Advisors

@bombnp

@bombnp bombnp added enhancement Improve existing features cugetreg-api Related to cugetreg-api cugetreg-web Related to cugetreg-web cu-scraper Related to CU Scraper labels Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cu-scraper Related to CU Scraper cugetreg-api Related to cugetreg-api cugetreg-web Related to cugetreg-web enhancement Improve existing features
Projects
Status: Todo
Development

No branches or pull requests

1 participant