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

Automated seat count updating (database level) #23

Closed
Bad-Science opened this issue Jan 18, 2016 · 4 comments · Fixed by #47
Closed

Automated seat count updating (database level) #23

Bad-Science opened this issue Jan 18, 2016 · 4 comments · Fixed by #47
Assignees
Labels
class:design This issue is related to design priority:high This issue has a high priority service:core This issue involves the core service

Comments

@Bad-Science
Copy link
Member

A key part of the application's function is automatic and timely updates to seat count information. The information will be parsed from the xml file found here https://sis.rpi.edu/reg/rocs/YACS_201601.xml

A suggested approach is to poll this file every minute or so and store it in memory. On each subsequent poll, diff the new file with the one previously stored, and update sections corresponding to changed lines. (obviously) then update the locally stored copy. The records corresponding to the changes seat counts should then be updated in the database.

@Bad-Science Bad-Science added priority:high This issue has a high priority class:design This issue is related to design labels Jan 18, 2016
@Bad-Science Bad-Science modified the milestone: Minimum Viable Product Release Jan 20, 2016
@copperwater
Copy link
Member

It's unclear whether you want this to be done on the backend, frontend, or both. Also, we do not expect to use that XML file; the provided API will be a tab- or comma- delimited file (can't remember which) representing the same fields without using the XML tags and syntax.

@Bad-Science
Copy link
Member Author

My understand was that only the schools/departments/subjects files will be tab or comma delimited. Maybe I am mis-remembering.

@Bad-Science
Copy link
Member Author

But to answer the first question, this issue was for the backend (updating the records in the database). Should have been more clear will edit the issue. Updating the seats information on the front end automatically without reloading the page should also be done, but that is less vital and may not be needed for the first milestone. I will create a separate issue for this.

@Bad-Science Bad-Science changed the title Automated seat count updating Automated seat count updating (database level) Jan 22, 2016
@Bad-Science Bad-Science self-assigned this Feb 4, 2016
@copperwater copperwater added the service:core This issue involves the core service label Feb 4, 2016
@Bad-Science
Copy link
Member Author

e180daf resolves the initial issue but is unoptimized. closing this and created #46

Bad-Science added a commit that referenced this issue Sep 30, 2018
Bad-Science added a commit that referenced this issue Oct 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
class:design This issue is related to design priority:high This issue has a high priority service:core This issue involves the core service
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants