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.

Sign up for GitHub

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

Jump to bottom

Remove SIS Scraping #638

Open
Apexal opened this issue Sep 11, 2020 · 2 comments
Open

Remove SIS Scraping #638

Apexal opened this issue Sep 11, 2020 · 2 comments
Assignees
@Apexal
Labels
Area: Back End An issue pertaining to the backend server (routes, api, etc.). Area: Database An issue pertaining to the database schemas or related. Area: Front End An issue pertaining to the frontend. Difficulty: Intermediate Priority: High A serious issue. Type: Enhancement

Comments

@Apexal
Copy link
Owner

Apexal commented Sep 11, 2020

All can be done if given CRNs. Users can just submit their profile info manually.
@Apexal Apexal added Priority: High A serious issue. Area: Back End An issue pertaining to the backend server (routes, api, etc.). Area: Front End An issue pertaining to the frontend. Area: Database An issue pertaining to the database schemas or related. Type: Enhancement Difficulty: Intermediate labels Sep 11, 2020
@Apexal
Copy link
Owner Author

Apexal commented Sep 14, 2020

Perhaps using Redis as a cache for courses fetched from https://github.com/Apexal/rpi-schedule-parser would work...

@Apexal
Copy link
Owner Author

Apexal commented Jan 25, 2021

Lo and behold... I finally solved this with ORCA, a public RPI course API. I must do this ASAP since scraping appears broken anyway...

@Apexal Apexal self-assigned this Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Apexal Apexal

Labels
Area: Back End An issue pertaining to the backend server (routes, api, etc.). Area: Database An issue pertaining to the database schemas or related. Area: Front End An issue pertaining to the frontend. Difficulty: Intermediate Priority: High A serious issue. Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Apexal