https://github.com/saulshanabrook/colgate-schedule
Add your course schedule from your portal to iCal or Google Calendar automatically
https://github.com/saulshanabrook/colgate-schedule
Last synced: 8 months ago
JSON representation
Add your course schedule from your portal to iCal or Google Calendar automatically
- Host: GitHub
- URL: https://github.com/saulshanabrook/colgate-schedule
- Owner: saulshanabrook
- Created: 2014-08-23T13:26:23.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2015-05-15T17:28:30.000Z (over 10 years ago)
- Last Synced: 2025-02-15T08:17:00.622Z (8 months ago)
- Language: Python
- Homepage:
- Size: 178 KB
- Stars: 1
- Watchers: 2
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Colgate Schedule
Add your course schedule from your portal to iCal or Google Calendar automatically
## Instructions
**UDPATE**: I have destroyed my heroku app that was hosting this code, at the request
of Colgate IT. The app encourages bad security procedures by teaching students to
enter their login info on a page that is not official. IT is working to open up
authentication on student info so that apps like this could be created in a
secure manor.
Add an iCalendar address that will have all your courses in it to
[Google Calendar](https://support.google.com/calendar/answer/37100?hl=en) or
[Apple Calendar](http://support.apple.com/kb/PH11523) or download the
`.ics` file by putting the calendar address in your browser, to import it to
another program.
The address you should use is
`https://colgate-schedule.herokuapp.com///`
## Possible Questions:
### How does it work?
It scrapes the schedule page, using your username and password, and looks
for the class times. Then it parses those times and creates a `.csv` file
with them.
You can see all of the code on [Github](https://github.com/saulshanabrook/colgate-schedule)
### But Isn't this horribly insecure?
Well yes, because You are sending your username and password for Colgate to
someone who is not
Colgate. That is a bad idea. I can say that I won't do anything malicious,
like look at the logs to see everyone's usernames and password, but it is
literally one keystroke away. One solution is to do this all on the client
side, which I should be doing. Maybe that will be the rewrite. I just
don't like Javascript as much as Python, but it makes much more sense.
While I am working on that, you could deploy your own version. It runs
for free on Heroku, just click this nice big button, and then you won't
have to worry about me snooping into your traffic.
[](https://heroku.com/deploy?template=https://github.com/saulshanabrook/colgate-schedule)
### Wait, it isn't working!!
It is pretty dumb. Also I have hard coded in the year and vacation time,
so unless I can figure out a good way to scrape that, it is stuck on
2014-15 for now.
If it breaks for one of your classes, let me know, just [leave an issue](https://github.com/saulshanabrook/colgate-schedule/issues/new)
with as much info as you can, obviously not your username and password.