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

ExamSchedule/1149ExamSchedule.csv has extra blank columns #62

Open
nathanv opened this issue Oct 16, 2014 · 4 comments
Open

ExamSchedule/1149ExamSchedule.csv has extra blank columns #62

nathanv opened this issue Oct 16, 2014 · 4 comments
Assignees

Comments

@nathanv
Copy link
Contributor

nathanv commented Oct 16, 2014

There is a known issue with extra columns in the csv. Some notes:

  • This issue ONLY affects the CSV and not the API.
  • Since we wanted to get the data out as fast as possible and since the API works as per usual, we are releasing the data with this known issue.
  • In the future, we endeavour to properly normalize the data in conjunction with the partners at the registrar.

edit 13:06 16-10-2014: for clarity

@nathanv
Copy link
Contributor Author

nathanv commented Oct 16, 2014

File in question is here: https://api.uwaterloo.ca/v2/terms/1149/examschedule.json

@nathanv nathanv self-assigned this Oct 16, 2014
@nathanv nathanv added the bug label Oct 16, 2014
@nathanv
Copy link
Contributor Author

nathanv commented Oct 16, 2014

@lkmorlan
Copy link
Contributor

This raises a question about the nature of these source data files. I think they should either be the unprocessed files strait from the upstream source or fully-processed and normalized files which use ISO dates and times, no redundant data (like day of the week), etc. Right now, they are somewhere in the middle, having had some processing, but not all of it.

@nathanv
Copy link
Contributor Author

nathanv commented Oct 16, 2014

Point of clarification: please not that this issue ONLY affects the CSV and not the API.

@lkmorlan totally agree. Thanks for opening the new bugs #63, #64, #65, #66, #66.

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

No branches or pull requests

2 participants